🚀 go-pugleaf

In article <Frode.Nilsen-1508001004560001@129.241.250.12>,
Frode.Nilsen@mison.no (Frode Nilsen) wrote:

| Are you sure this is the intended interpretation of the standard ?

My specialty is the lib half of the standard, not the language half, so I
could very well be wrong.
 
| The heading for paragraph 15 is:
| "A new-expression that creates an object of type T initializes that object
| as follows:"
| 
| I don't think an array are considered as a separate type, just as a
| multiple of one type.
| 
| The mention of array in the other bullets are done in parantheses, not
| directly in the text. Just to make sure the reader understands that this
| includes arrays?
| I feel this then is implicit in bullet 3 and 4.
| 
| And since the form
| 
| long* item = new long( 0 );
| 
| is legal syntax, I find it strange that
| 
| long* array = new long[1024]( 0 );
| 
| should not be.

Section 3.9 enumerates the different types in C++.  Arrays are listed in
3.9.2/1/bullet 1.  So that's where I'm getting my notion of different
things that T could represent in 5.3.4. 
 
| Just my two cents.

Perhaps your question would make an appropriate post on comp.std.c++.  The
people that authored 5.3.4 will likely be there to give a more
authoritative answer.

FWIW, I also find it strange that the language allows for initializing an
array of longs to 0 (via the () syntax), but to no other value.

-Howard