From: Chusslove Illich <caslav.ilic@gmx.net>
Cc: guile-user@gnu.org
Subject: Re: Avoiding name clashes between different scripts
Date: Fri, 1 Apr 2005 16:57:16 +0200 [thread overview]
Message-ID: <200504011657.22836.caslav.ilic@gmx.net> (raw)
In-Reply-To: <E1DHLYM-000867-00@surf.glug.org>
[-- Attachment #1.1: Type: text/plain, Size: 430 bytes --]
> [: Thien-Thi Nguyen :]
> probably you should avoid top-level defines and use "executable
> modules" [...] a module gives you a namespace into and out of which
> you can import and export bindings.
Oh... I should have read the manual more carefully. Not only that this
perfectly solves what I wanted, but also simplifies some other things that
I had in mind. Thanks :)
--
Chusslove Illich (Часлав Илић)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2005-04-01 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 10:55 Avoiding name clashes between different scripts Chusslove Illich
2005-04-01 12:47 ` Thien-Thi Nguyen
2005-04-01 14:57 ` Chusslove Illich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200504011657.22836.caslav.ilic@gmx.net \
--to=caslav.ilic@gmx.net \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).