From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: [goops] adding a number class with generic methods
Date: Sun, 07 May 2006 12:45:42 +0100 [thread overview]
Message-ID: <87odyanjmh.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <66e540fe0605070237r12b1ee34i22dfb7b63a2b1dd8@mail.gmail.com> (Mikael Djurfeldt's message of "Sun, 7 May 2006 11:37:59 +0200")
"Mikael Djurfeldt" <mdjurfeldt@gmail.com> writes:
> On 5/7/06, Neil Jerram <neil@ossau.uklinux.net> wrote:
>> I agree that this explains why the export is not necessary (and hence
>> why it works without it). But I don't yet understand why adding the
>> export messes things up.
>
> In the current module system, the effect of mentioning a variable in
> an export statement is to set up a new, undefined, variable with that
> name. This variable is added to the module and to the export list of
> the model. The former has the effect of shadowing the old variable =.
I see. Thanks for explaining this.
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-05-07 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 19:13 [goops] adding a number class with generic methods Marco Maggi
2006-05-04 19:26 ` Mikael Djurfeldt
2006-05-06 23:07 ` Neil Jerram
2006-05-07 9:37 ` Mikael Djurfeldt
2006-05-07 11:45 ` Neil Jerram [this message]
2006-05-09 7:56 ` Ludovic Courtès
2006-05-09 8:30 ` Mikael Djurfeldt
2006-05-09 9:43 ` GOOPS and Code Complexity Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2006-05-03 5:36 [goops] adding a number class with generic methods Marco Maggi
2006-05-04 7:47 ` Neil Jerram
2006-05-02 20:16 Marco Maggi
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=87odyanjmh.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.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).