From 4685017949166079992 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,a7bb6560624ae2c1 X-Google-Attributes: gidf78e5,public From: Kevin Kostrzewa Subject: Re: More M$ Not Conforming points... Date: 1999/08/24 Message-ID: #1/1 X-Deja-AN: 516733402 Approved: Fergus Henderson References: <7ps1sg$dev$1@nnrp1.deja.com> X-Original-Date: 24 Aug 1999 13:11:48 -0400 X-Complaints-To: news@news.unimelb.edu.au X-Trace: izvestia.its.unimelb.edu.au 935528095 32226 128.250.29.17 (24 Aug 1999 20:54:55 GMT) Organization: Msen, Inc. X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBFAgUAN8MGj+EDnX0m9pzZAQGdmQGAiOM6aVf5NOL5mRWg11IWPKkI2z8Pbhlk CSmtD+fRy28cXyb96XpAKXDetL5ZYVc7 =Ik2e NNTP-Posting-Date: 24 Aug 1999 20:54:55 GMT Newsgroups: comp.std.c++ whbloodworth@my-deja.com writes: > The standard states that 'unexpected' will be called if a function > throws something other than what is specified in the throw > specification. For example, ... > Using M$ VC++, the above function Foo will successfully (depending on > how you look at it) throw F() and the caller can catch it. ... the latest version of VC++ does not handle exception specifications. If you have MSDN for October 1998, the MSDN page: mk:@MSITStore:C:\Program%20Files\Microsoft%20Visual%20Studio\MSDN98\98OCT\1033\vccore.chm::/html/_core_exception_handling_syntax.htm says: Microsoft Specific -> Microsoft C++ does not support the function exception specification mechanism, as described in section 15.4 of the ANSI C++ draft. END Microsoft Specific -- kevin kostrzewa work: kkostrzewa@csisolutions.com home: tkkost@newsguy.com --- [ 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 ]