Path: news.mv.net!news.shore.net!newspump.monmouth.com!newspeer.monmouth.com!colt.net!newspeer.clara.net!news.clara.net!news.vas-net.net!server2.netnews.ja.net!news.ox.ac.uk!plato.wadham.ox.ac.uk!jstacey From: J-P Newsgroups: comp.os.msdos.djgpp Subject: *** OFF-TOPIC *** Re: ok, I have more info on problem at hand Date: Sat, 2 Sep 2000 18:47:40 +0100 Organization: Oxford University, England Lines: 24 Message-ID: References: <8oqt7m$6of$1 AT plato DOT wadham DOT ox DOT ac DOT uk> NNTP-Posting-Host: plato.wadham.ox.ac.uk Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.ox.ac.uk 967916947 4969 163.1.164.74 (2 Sep 2000 17:49:07 GMT) X-Complaints-To: newsmaster AT ox DOT ac DOT uk NNTP-Posting-Date: 2 Sep 2000 17:49:07 GMT To: Jason Green In-Reply-To: Xref: news.mv.net comp.os.msdos.djgpp:103100 *** OFF-TOPIC *** On Sat, 2 Sep 2000, Jason Green wrote: >> ... unless you ever want to resize, in which case use malloc() and >> realloc() and explicitly cast the pointers. > >The standard containers will let you resize. Do you mean the standard classes? Because I'm sure even Bjarne Stroustrup (sp?) has said otherwise in some tome, but I could be wrong. If so, that isn't much use if you're not using the standard classes. I merely wanted to mention it as an /option/, not as a flame. Which is why I don't particularly want to redirect this to comp.lang.c++, because [a] they probably only deal with the ANSI recommendation, whatever that is this week (that sort of , and [b] they've probably had this argument several times before, initiated with the intention of flaming. If malloc() has no place in C++, then it's odd that you're still able to use it. J-P