Path: news.mv.net!news.shore.net!newsfeed.mathworks.com!EU.net!blackbush.xlink.net!newsfeed.germany.net!news.vas-net.net!server2.netnews.ja.net!news.ox.ac.uk!plato.wadham!not-for-mail From: jstacey AT plato DOT wadham DOT ox DOT ac DOT uk (J-P) Newsgroups: comp.os.msdos.djgpp Subject: Re: *** OFF-TOPIC *** Re: ok, I have more info on problem at hand Date: 3 Sep 2000 11:58:58 +0100 Organization: Wadham College, Oxford Lines: 22 Message-ID: <8otati$ei1$1@plato.wadham.ox.ac.uk> References: NNTP-Posting-Host: plato.wadham.ox.ac.uk X-Trace: news.ox.ac.uk 967978825 25551 163.1.164.74 (3 Sep 2000 11:00:25 GMT) X-Complaints-To: newsmaster AT ox DOT ac DOT uk NNTP-Posting-Date: 3 Sep 2000 11:00:25 GMT Xref: news.mv.net comp.os.msdos.djgpp:103122 In article , Jason Green wrote: >> 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. > >"Using resize() on a vector is very similar to using the C standard >library function realloc() on a C array allocated on the free store." Sorry: yes. What I wrote was the exact opposite of what I meant, due to multiple rewrites before sending. I meant that /only/ in the standard classes was there a realloc() equivalent. >The C++ standard, as far as possible, is backward compatible with >conforming C code. However, there were a few things the C++ standard >committee felt were more important then backward compatibilty, and >implicit conversion of void pointers was one of them. I think we're going to end up violently agreeing with each other here, especially as implicit pointer conversion (bad due to polymorphism) hasn't got much to do with realloc(). J-P