This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH] setup.exe: Stop NetIO_HTTP from treating entirestreamas a header


On Wed, 2001-11-28 at 11:16, Gary R Van Sickle wrote:
> > On Wed, 2001-11-28 at 10:09, Christopher Faylor wrote:
> > > References?  A simple google search for 'NULL C++ deprecated' didn't
> > > unearth this information.
> >
> > Deprecated may have been too strong a word. Anyway, references:
> >
> > The C++ annotations - http://www.icce.rug.nl/documents/cpp.shtml
> > Specifically...
> > http://www.icce.rug.nl/documents/cplusplus/cplusplus02.html#an78
> 
> This must predate the ratification of the standard:
> 
> "2.5.3: NULL-pointers vs. 0-pointers
> [snip]  Indeed, according to the descriptions of the pointer-returning
> operator new 0 rather than NULL is returned when memory allocation fails."
> 
> When new fails, it doesn't return anything, but rather throws an exception
> now.  (Well, unless you use the (std::nothrow) syntax which I've never seen
> used and in fact just found out about).  Oops, now it's my turn to document!
> ;-):  Chuck Allison here: http://www.freshsources.com/newcpp.html

Thank you for the reference. Setup currently builds with exceptions
disabled, which is a bit of a handicap. I was going to raise this soon
anyway :}.
 
> Anywhoo, tell you guys what:  I'll roll all four permutations and whoever
> checks it in can pick which patch or patches they want ;-).

Code comfortable for you. I won't reject patches using NULL, or not
using ==/!= 0. 

Rob


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]