From: Joe Buck <jbuck@synopsys.com>
To: Olivier.Galibert@mines.u-nancy.fr (Olivier Galibert)
Cc: jbuck@synopsys.com, egcs@cygnus.com
Subject: Re: linux libio status
Date: Wed, 15 Oct 1997 20:16:00 -0000 [thread overview]
Message-ID: <199710151843.LAA23738@atrus.synopsys.com> (raw)
In-Reply-To: <19971015194434.57156@renaissance.loria.fr>
> > Conclusion: we should deprecate the use of NULL in C++ code. If we
> > must define NULL for C++ code, it must be 0. Nothing else.
>
>
> You say "make sure that current code works but randomly crashes when the
> users upgrade to new 64bits architectures". I don't call that being
> fair to the user.
Stop putting words in my mouth. Since my C++ code has to run with
multiple compilers, I never use NULL and, on those rare occasions where
I must use a variadic function, I pass a null pointer of the right type.
What's unfair to the user is to tell the user he/she can use NULL in
any position where a pointer is required in C++ code. The problem is
that there is no definition that will work correctly and portably with
variadic functions. (But then, variadic functions are a bad idea, as
their arguments can't be type-checked at compile time except by special
means, like the gcc printf hack. Furthermore, they are rare except for
the printf family, and gcc has a special check for those).
> If your vision of "deprecating NULL" is "let users having their code working
> right now but crashing randomly when they eventually have the money to buy
> a 64bits processor" then yes, define NULL as 0.
So Stroustrup doesn't know what he's talking about? So every C++ author
in the book doesn't know either? For variadic functions that want a
pointer, 0L is just as broken as 0; on certain memory models for 16-bit
PC code, you will corrupt your stack (a near pointer, only 16 bits, is
expected and you push a four-byte quantity).
There's no substitute for programming correctly.
next prev parent reply other threads:[~1997-10-15 20:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-14 23:23 Joe Buck
1997-10-15 0:06 ` Richard Henderson
1997-10-15 0:52 ` Olivier Galibert
1997-10-15 8:25 ` [ECGS] " chip
1997-10-15 11:12 ` Peter Seebach
1997-10-15 20:16 ` Joe Buck
1997-10-15 11:12 ` Joe Buck
1997-10-15 12:10 ` Olivier Galibert
1997-10-15 16:51 ` [ECGS] " chip
1997-10-15 20:16 ` Joe Buck [this message]
1997-10-15 20:16 ` Olivier Galibert
1997-10-16 12:53 ` Pal Engstad
[not found] ` <199710151419.JAA20162.cygnus.egcs@monolith.solon.com>
1997-10-15 16:51 ` Jason Merrill
1997-10-15 20:16 ` Peter Seebach
1997-10-15 22:29 ` Jason Merrill
1997-10-16 8:31 ` Peter Seebach
1997-10-16 15:19 ` Jason Merrill
1997-10-16 12:53 ` Peter Seebach
1997-10-16 15:19 ` Paul Koning
[not found] <199710150623.XAA06491.cygnus.egcs@atrus.synopsys.com>
1997-10-15 2:10 ` Jason Merrill
1997-10-15 9:15 ` Joe Buck
1997-10-15 11:12 ` Per Bothner
1997-10-15 14:33 ` Joe Buck
1997-10-15 16:51 ` Per Bothner
[not found] ` <199710152351.QAA02138.cygnus.egcs@cygnus.com>
1997-10-16 1:51 ` Jason Merrill
1997-10-16 12:58 ` Alexandre Oliva
1997-10-16 12:58 ` Joe Buck
1997-10-17 12:53 ` Jason Merrill
1997-10-15 16:51 ` Peter Seebach
1997-10-15 14:33 ` Richard Henderson
1997-10-15 12:10 Greg Galloway
1997-10-16 12:53 ` H.J. Lu
1997-10-15 12:10 Greg Galloway
1997-10-15 20:16 ` Joe Buck
1997-10-16 12:58 ` H.J. Lu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199710151843.LAA23738@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=Olivier.Galibert@mines.u-nancy.fr \
--cc=egcs@cygnus.com \
/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).