-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I am wondering, what is the advantage of having both the definition of
the module and the invocation depending
on the module path?
One would think that the path in invocation [i mean `(use-modules (a
path to module))' macro invocation],
w
> On 8 Jan 2015, at 01:18, Chris Vine wrote:
>
> On Wed, 7 Jan 2015 23:15:07 +0100
> Hans Aberg wrote:
>>
>>> On 7 Jan 2015, at 21:24, Ludovic Courtès wrote:
>>>
>>> If Scheme code calls C++ code that throws an exception, then the
>>> stack will be unwound by libstdc++ and Guile’s ‘dynamic-w
> On 8 Jan 2015, at 02:00, Matt Wette wrote:
>
>
> On Jan 7, 2015, at 6:45 AM, Hans Aberg wrote:
>
>>
>>> On 7 Jan 2015, at 14:52, Matt Wette wrote:
>>>
>>> Python is written in C yet Qt has been integrated in to produce PyQt. I
>>> wonder how that is done. I will take a look.
>>
>> I
When a program contains:
(use-modules (foo bar))
Guile searches for a file named foo/bar.scm (or foo/bar) in its search
path. The search path is defined by the user, using the GUILE_LOAD_PATH
environment variable etc. (info "(guile) Load Paths").
So the source file of that module, foo/bar.scm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-01-08 10:17, l...@gnu.org wrote:
When a program contains:
(use-modules (foo bar))
Guile searches for a file named foo/bar.scm (or foo/bar) in its search
path. The search path is defined by the user, using the
GUILE_LOAD_PATH
environ
Alpha Omega writes:
> I am just curious about the decision to embed path info in the module
> file itself.
The '(foo bar baz)' is not path info, it's the name of the module. :-)
The filesystem path mimics the components of the module name.
Taylan
I find this surprising too. IMO, it's not useful to declare the file a
module at all.
Similarly having to "export" or "re-export" procedures and variables is not
helpful. Having everything exported by default makes development easier,
even if it can lead to name clash, imports can be renamed. Inde
Amirouche Boubekki writes:
> I find this surprising too. IMO, it's not useful to declare the file a
> module at all.
You can have single-name-component modules '(foo)' in corresponding
files foo.scm if you want stand-alone files/modules.
> Similarly having to "export" or "re-export" procedures
On Jan 7, 2015, at 5:00 PM, Matt Wette wrote:
> PyQt does not recompile Python in C++ so there must be some way to do it w/o
> recompiling python (=> guile).
I looked into PyQt a bit. Only recent versions of Qt have exceptions. The
bulk of the code is exception free.
Also, PyQt uses a to
