From: "Dale P. Smith" <dsmith@cleveland.lug.net>
Cc: guile-devel@gnu.org
Subject: Re: Everyone working on the C side might want to read this article...
Date: Thu, 17 Apr 2003 16:33:29 -0400 [thread overview]
Message-ID: <20030417163329.2756da8b.dsmith@cleveland.lug.net> (raw)
In-Reply-To: <873ckgevxl.fsf@raven.i.defaultvalue.org>
On Thu, 17 Apr 2003 15:00:22 -0500
Rob Browning <rlb@defaultvalue.org> wrote:
>
> The following article explains gcc changes that may be behind at least
> some of our recent set of bugs:
>
> http://www.ddj.com/documents/s=880/ddj0010d/0010d.htm
>
> You may not need to read it if you're already familiar with what the C
> standard says about type aliasing, or already know that (for example)
> according to the standard this code is illegal and the results are
> undefined:
[ code examples ]
> Thanks to Marius for tracking the pointer down. I'm not yet sure what
> this means for our code.
Some time ago, some effort was put into guile to use unions and structs
as the type for SCM to provide much more robust type checking from the
compiler. Unfortunately, that code is almost worthless except for
debugging because of the way structs are returned, iirc.
Does this situation change at all with gcc >= 3 and the new c99 standard?
-Dale
--
Dale P. Smith
Senior Systems Consultant, | Treasurer,
Altus Technologies Corporation | Cleveland Linux Users Group
dsmith at altustech dot com | http://cleveland.lug.net
440-746-9000 x239 |
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-04-17 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 20:00 Everyone working on the C side might want to read this article Rob Browning
2003-04-17 20:25 ` Bruce Korb
2003-04-17 20:33 ` Dale P. Smith [this message]
2003-04-28 20:48 ` Rob Browning
2003-04-28 21:02 ` Bruce Korb
2003-04-28 22:30 ` 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=20030417163329.2756da8b.dsmith@cleveland.lug.net \
--to=dsmith@cleveland.lug.net \
--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).