🚀 go-pugleaf

In article <4kr1p3$67g@mulga.cs.mu.OZ.AU> fjh@munta.cs.mu.OZ.AU (Fergus
Henderson) writes:

|> clamage@Eng.Sun.COM (Steve Clamage) writes:

|> >According the draft standard, the results of using a reference
|> >type as the last pararmeter before the ellipsis (...) are
|> >undefined.  See section 18.7 "Other runtime support" [lib.support.runtime].

|> Is there any good reason why this has undefined behaviour rather than
|> being ill-formed code?  Surely this should be very easy for implementations
|> to detect and diagnose.

Historical reasons, no doubt.  Declare the last parameter a char in C,
and you also get undefined behavior.

And it's surely no more difficult to diagnose a double underscore (and
at least one compiler does), which is also `undefined behavior'.
-- 
James Kanze         Tel.: (+33) 88 14 49 00        email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs-Bourgeois, F-67000 Strasbourg, France
Conseils, études et réalisations en logiciel orienté objet --
                -- A la recherche d'une activité dans une region francophone



[ 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         ]
[ FAQ:      http://reality.sgi.com/employees/austern_mti/std-c++/faq.html    ]
[ Policy:   http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
[ Comments? mailto:std-c++-request@ncar.ucar.edu                             ]