Hi Ian,
[re-adding the list; please keep the list CC'd on all guile-related
topics]
On Fri 28 Jan 2011 22:37, Ian Hulin writes:
> Are you going to fix the double extension bug for defaulted/cached
> output names? I.e. compiling c++.scm will produce an output filename of
> c++.scm.go in the cach
On Fri, 28 Jan 2011 17:26:07 +0100
Andy Wingo wrote:
> On Wed 08 Dec 2010 12:45, Marek Kubica
> writes:
>
> > Is there a way to add the current directory to the search path? I
> > think this should be default, just like in Python, otherwise
> > creating modules is a really big hassle.
>
> As A
Marek Kubica writes:
> What about "the same directory that the file is in"? The point is, when
> writing scripts that become larger than one file, splitting them into
> modules becomes immensely painful because the modules cannot find each
> other.
I agree that this is a bit awkward. My current
Neil Jerram writes:
> Marek Kubica writes:
>
>> What about "the same directory that the file is in"? The point is, when
>> writing scripts that become larger than one file, splitting them into
>> modules becomes immensely painful because the modules cannot find each
>> other.
>
> I agree that th
Hi Marek,
On Sat 29 Jan 2011 13:13, Marek Kubica writes:
> On Fri, 28 Jan 2011 17:26:07 +0100
> Andy Wingo wrote:
>
>> We don't add the current directory to the search path because it is a
>> security issue, for the same reason that "." is not in $PATH.
>
> What about "the same directory that t
On Sat 29 Jan 2011 13:13, Marek Kubica writes:
> What about "the same directory that the file is in"? The point is, when
> writing scripts that become larger than one file, splitting them into
> modules becomes immensely painful because the modules cannot find each
> other.
I would also mention
On Sat, 29 Jan 2011 18:07:04 +0100
Andy Wingo wrote:
> I would also mention the approach from the skeleton package, which you
> can fetch from http://wingolog.org/git/skeleton.git. `autoreconf
> -vif', `./configure', and `make'. It has a toplevel `env' script,
> similar to other environment scr
On Sat, 29 Jan 2011 18:04:14 +0100
Andy Wingo wrote:
> For what purpose? If you are using modules, they are already in one
> global namespace, the various roots of which are in the %load-path
> and/or %load-compiled-path. (resolve-module '(foo bar)) should work
> regardless of what file calls i
Andy Wingo writes:
> Hi Marek,
>
> On Sat 29 Jan 2011 13:13, Marek Kubica writes:
>
>> What about "the same directory that the file is in"? The point is, when
>> writing scripts that become larger than one file, splitting them into
>> modules becomes immensely painful because the modules cannot
