unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: rm@fabula.de
Cc: rm@fabula.de, tomas@fabula.de, guile-devel@gnu.org
Subject: Re: Smart variables, dumb variables
Date: Thu, 15 Aug 2002 22:25:21 +0200	[thread overview]
Message-ID: <20020815202521.GB9588@www> (raw)
In-Reply-To: <87n0rnq4am.fsf@zagadka.ping.de>

On Thu, Aug 15, 2002 at 10:02:09PM +0200, Marius Vollmer wrote:
> 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.
> 
> Ok, agreed.  Objections?
> 
> > 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.
> 
> You can't really do that I think.  You can't change a procedure into a
> generic function.  What you can do is change the value of a variable
> to point to a new function, which is generic.  But maybe that is what
> you want.

Excuse my slopy language - i was thinking more of the net result.
So i guess my macro would have to save the original value (the one
pointing to the procedure) and then, after a define-generic, issue
a define method that rebinds the value to a generic method with 
a parameter signature of '<object>'. Kind of clumsy.

> There is no 'generic?' but you can maybe define it like so

I couldn't find one (which i found astonishing as well).

>   (define (generic? obj)
>     (or (is-a? obj <generic>)
>         (is-a? obj <primitive-generic>)))

Yes, i guess that would do the trick.

  Ralf

 :
> 
> -- 
> GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-08-15 20:25 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 [this message]
2002-08-17 11:59                         ` Neil Jerram
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=20020815202521.GB9588@www \
    --to=rm@fabula.de \
    --cc=guile-devel@gnu.org \
    --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).