From -5982964425027180091 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,1ac63fff730e7d59 X-Google-Attributes: gidf78e5,public From: "Ken Hagan" Subject: Re: C++ Memory Allocation Bashing Date: 1999/08/13 Message-ID: #1/1 X-Deja-AN: 512276909 Approved: Valentin Bonnard References: <37b445e8.82613572@news.airmail.net> X-Original-Date: Fri, 13 Aug 1999 10:09:01 +0100 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Organization: - X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBVAwUAN7QtgKwEuYhIxRhxAQEYrgIApdcddrwmuOnnPgPVxnIfkvFos+KnowSs JRDytifReHshUjq20b/ebKQZ+hMXOustaSbrydUPFujQxTT5ELtNgw== =7DQ4 Newsgroups: comp.std.c++ Certainly. The author appears to understand why C++ does things differently. However, he believes that type safety isn't important and that you can't build a debugging allocator in C++. The first is at very least, contentious. The second is definitely false. He concludes with a wish that the tight binding between new and constructor invocation should be broken. Presumably none of his classes have significant invariants, or internal state. My guess is that this was written by a student who hasn't done any real programming yet. William H. Bloodworth wrote in message <37b445e8.82613572@news.airmail.net>... >Hello, > >Would anyone (Bjarne preferably) care to comment the information presented on C++ memory >allocation at this location: http://www.pdos.lcs.mit.edu/~dm/c++-new.html ? > >Thank you, --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html ]