From: Joe Buck <jbuck@synopsys.com>
To: mschaefer@dsai.com (Mark Schaefer)
Cc: egcs@cygnus.com
Subject: Re: Before you release 1.0.3 -- please!
Date: Thu, 30 Apr 1998 20:03:00 -0000 [thread overview]
Message-ID: <199805010303.UAA12389@atrus.synopsys.com> (raw)
In-Reply-To: <98Apr28.171852mdt.26882@colorado.dsai.com>
> Before you send the next release out the door, could someone figure
> out what you're going to do about the NULL problem. Basically, it's a
> damned if I do, damned if I don't problem.
The workaround is to use 0 in your code for function pointers or
member function pointers. I doubt if this is going to be fixed before
1.0.3, since the only purpose of 1.0.3 is to fix so-called showstopper
bugs, not bugs with simple workarounds.
> int main(int, char**)
> {
> UiCallbackHandler a;
> a.addCallback (1,1,NULL,1);
> }
s/NULL/0/
prev parent reply other threads:[~1998-04-30 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-28 21:59 Mark Schaefer
1998-04-30 20:03 ` Joe Buck [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199805010303.UAA12389@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=mschaefer@dsai.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).