unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: stack overflow equal? values
Date: Fri, 19 Jan 2007 10:19:45 +0100	[thread overview]
Message-ID: <87ac0fbcge.fsf@laas.fr> (raw)
In-Reply-To: <8764b4aree.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 19 Jan 2007 09:42:17 +1100")

Hi,

Kevin Ryde <user42@zip.com.au> writes:

> Yep, looks good.

Applied to both branches (I also converted the change logs in 1.8 to
UTF-8 :-)).

> After I posted I wondered if the values struct is an actual "s" or if
> there's some strange extra I couldn't spot.  Testing eq avoids
> worrying about that.

Yes.  The `s' field is actually part of the REQUIRED_VTABLE_FIELDS that
gets automatically added in `make-vtable-vtable'.

> Dunno why values are a struct and not a smob cell.

Maybe because structs looked cool at that time.  ;-)

>> but their semantics are a
>> little fuzzy to me.  In particular, I don't understand why the size of
>> the tail array can be specified in both `make-vtable-vtable' and
>> `make-struct': What does that mean?  Which one should really be taken
>> into account?
>
> Dunno :).

Then maybe we should "do something" about it in 1.9, and fix remaining
bugs.

> The records level is friendlier I guess.  For a long time I couldn't
> understand what "vtable" meant, I still don't think I quite do.  Maybe
> the docs should be tweaked, to help show what structs are typically
> meant to be.

Yes.  Actually, I used mostly exclusively either SRFI-9 records or GOOPS
classes.  Then there's also Guile's built-in records as you said.

Structs are nice in that they can be easily accessed both from C and
Scheme, so they can probably be used in lieu of SMOBs in some cases.

Still, that leaves us with 3 (or 4) record/struct APIs, and we may also
want to implement R6RS records at some point...

Thanks,
Ludovic.


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


      reply	other threads:[~2007-01-19  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 16:57 stack overflow equal? values Marco Maggi
2007-01-17 23:32 ` Kevin Ryde
2007-01-18 12:57   ` Ludovic Courtès
2007-01-18 22:42     ` Kevin Ryde
2007-01-19  9:19       ` Ludovic Courtès [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=87ac0fbcge.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=bug-guile@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).