From: Kevin Ryde <user42@zip.com.au>
To: guile-devel@gnu.org
Subject: Re: struct-copy func
Date: Tue, 21 Aug 2007 09:27:55 +1000 [thread overview]
Message-ID: <87hcmtvlac.fsf@zip.com.au> (raw)
In-Reply-To: <87643aiox2.fsf@laas.fr> ("Ludovic Courtès"'s message of "Mon, 20 Aug 2007 10:35:37 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> `struct-copy' must check fields permission
I didn't want to do that.
> `s' fields must be updated
Ah yes, I forgot that.
> `o' fields cannot be copied I think.
I had in mind just bitwise copying them. But I guess that slightly
defeats the purpose of such fields, and could conceivably be a bit evil.
I might rethink it as just a record-copy, since plain records have none
of those questions. But that'd need at least `record?' down in C code
for a type check, so it might have to wait until most of the record
stuff is in C.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-20 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 0:46 struct-copy func Kevin Ryde
2007-08-20 8:35 ` Ludovic Courtès
2007-08-20 23:27 ` Kevin Ryde [this message]
2007-08-21 7:49 ` Ludovic Courtès
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=87hcmtvlac.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).