Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <79218202D4B9D4118A290002A508E13B79C39B@PNZEXCHANGE>
From: Ross Smith <rosss@pharos.co.nz>
To: "'Emil Briggs'" <emil@baymountain.com>, Ross Smith <rosss@pharos.co.nz>
Cc: cygwin@cygwin.com
Subject: RE: limit for # of items created with "new" ?
Date: Wed, 25 Sep 2002 16:36:33 +1200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

> From: Emil Briggs [mailto:emil@baymountain.com]
> 
> On Tuesday 24 September 2002 10:28 pm, Ross Smith wrote:
> > From: Hans Horn [mailto:hannes@2horns.com]
> >
> > > // an element of a linked list
> > > typedef struct node {
> > >   node (int _v, node* _n) : v(_v), next(_n) {}
> > >   int   v;
> > >   node* next;
> > > };
> >
> > I'm surprised that compiled; the typedef shouldn't be there.
> >
> > > int main (int argc, char** argv) {
> > >   // allocate descriptions of points
> > >   char** points = new char*[NUM_POINTS]; assert(points);
> >
> > The assert is superfluous; new is guaranteed never to return null.
> >
> 
> Except when you are out of memory.

No. It throws a std::bad_alloc exception.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/