From: Neil Jerram <neil@ossau.uklinux.net>
Cc: rm@fabula.de, tomas@fabula.de, guile-devel@gnu.org
Subject: Re: Smart variables, dumb variables
Date: 17 Aug 2002 12:59:41 +0100 [thread overview]
Message-ID: <m3d6shwv9u.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: 87n0rnq4am.fsf@zagadka.ping.de
>>>>> "Marius" == Marius Vollmer <mvo@zagadka.ping.de> writes:
Marius> rm@fabula.de writes:
>> > Should it print #<primitive-generic +> from the start?
>>
>> Since it actually _is_ a generic from the start, yes, i think it should.
Marius> Ok, agreed. Objections?
Sounds OK. Eventually, though, I presume what we _really_ want is for
_all_ Guile procedures to be generic. Once we achieve this, it will
no longer signify anything to say #<primitive-generic> rather than
#<primitive-procedure>, because there won't be any non-generic
procedures left.
>> Of course, what i'm really after is a test like 'generic? foo' so that
>> i can write a macro that does what i think guile should do. Make 'foo'
>> a generic iff it's not one allready.
Marius> You can't really do that I think. You can't change a procedure into a
Marius> generic function. What you can do is change the value of a variable
Marius> to point to a new function, which is generic. But maybe that is what
Marius> you want.
Sure? I think that subrs at least are made generic by filling in a
preexisting slot in the subr structure; variable binding doesn't need
to change.
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-17 11:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 20:06 Smart variables, dumb variables Marius Vollmer
2002-08-14 8:07 ` tomas
2002-08-14 19:35 ` Marius Vollmer
2002-08-14 20:28 ` tomas
2002-08-14 20:48 ` Marius Vollmer
2002-08-14 21:06 ` rm
2002-08-14 21:09 ` Marius Vollmer
2002-08-15 8:06 ` rm
2002-08-15 8:01 ` Lynn Winebarger
2002-08-15 9:51 ` rm
2002-08-15 14:44 ` Rob Browning
2002-08-15 16:34 ` Marius Vollmer
2002-08-15 17:27 ` rm
2002-08-15 19:43 ` Marius Vollmer
2002-08-15 20:02 ` rm
2002-08-15 20:02 ` Marius Vollmer
2002-08-15 20:25 ` rm
2002-08-17 11:59 ` Neil Jerram [this message]
2002-08-19 23:29 ` Marius Vollmer
2002-08-20 12:01 ` rm
2002-08-26 22:06 ` Marius Vollmer
2002-08-15 10:52 ` tomas
2002-08-15 16:36 ` Marius Vollmer
2002-08-14 21:31 ` Rob Browning
2002-08-14 21:45 ` Marius Vollmer
2002-08-15 2:43 ` Rob Browning
2002-08-15 6:29 ` Marius Vollmer
2002-08-15 14:38 ` Rob Browning
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=m3d6shwv9u.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=rm@fabula.de \
--cc=tomas@fabula.de \
/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).