From 3561379678170732061
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,8372ae6de42be399
X-Google-Attributes: gidf78e5,public
X-Google-ArrivalTime: 2004-02-25 09:50:09 PST
Return-Path: <devnull@stump.algebra.com>
X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f
Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!news.alt.net!comp-std-cpp-robomod!not-for-mail
X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov)
Delivered-To: std-c++@ucar.edu
From: wizofaus@hotmail.com (Dylan Nicholson)
Newsgroups: comp.std.c++
Subject: Re: Array of size 0
Organization: http://groups.google.com
Message-ID: <7d428a77.0402241229.71aaae63@posting.google.com>
References: <403601F6.8010706@ircad.u-strasbg.fr> <c15mlg$pdl$1@news1nwk.SFbay.Sun.COM> <m3y8qwp6uy.fsf@merlin.cs.tamu.edu> <7d428a77.0402221805.51174786@posting.google.com> <m3brnqpagi.fsf@merlin.cs.tamu.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1077654580 1167 127.0.0.1 (24 Feb 2004 20:29:40 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 24 Feb 2004 20:29:40 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 2.60-mulga_r1 (1.212-2003-09-23-exp) on 
	mulga.cs.mu.OZ.AU
X-Spam-Status: No, hits=0.1 required=5.2 tests=AWL,FORGED_HOTMAIL_RCVD2 
	autolearn=no version=2.60-mulga_r1
Approved: Fergus Henderson <fjh@cs.mu.oz.au>, moderator of comp.std.c++
Date: Wed, 25 Feb 2004 11:46:48 CST
Lines: 28
Xref: archiver1.google.com comp.std.c++:1224

Gabriel Dos Reis <gdr@cs.tamu.edu> wrote in message news:<m3brnqpagi.fsf@merlin.cs.tamu.edu>...
> 
> As a user of a popular OS, I happen to regretfully be a subject of
> those unpleasant experiments where the OS over-commits to memory
> allocation  and later proceeds on killing random processes (including
> sometimes "init").  

Ah, but I'm guessing maybe you can't detect the fact that the OS
overcommits memory from a C++ bad_alloc.  Which to me seems an odd OS
design - OS's shouldn't promise more memory than they can deliver (of
course if you've configured your OS to use an infinitely-expanding
page-file, it's impossible to tell the total virtual memory available,
given that you're competing with non-paging disk usage).

> 
> Given that 'T[0]' is ill-formed in the first place, what is expected
> about 'T[n]' when n has a runtime null value?
> 
How is T[0] ill-formed?  Or do you mean 'T local_array[0];' ?

Dylan

---
[ 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://www.jamesd.demon.co.uk/csc/faq.html                       ]



