From 8382510869407905254 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,a3fcfd059f7c78ee X-Google-Attributes: gidf78e5,public From: Francis Glassborow Subject: Re: Does throw() help compilers optimize? Date: 1998/09/22 Message-ID: <0VvI5YA9r2B2Ewuu@robinton.demon.co.uk>#1/1 X-Deja-AN: 393681065 Approved: stephen.clamage@sun.com (comp.std.c++) References: <199809220222.WAA09741@kauai.newjersey.sco.com> X-UID: 0000000001 X-Status: $$$T Organization: Southfield Microcomputer SS Mime-Version: 1.0 Reply-To: Francis Glassborow Newsgroups: comp.std.c++ Originator: clamage@taumet In article <199809220222.WAA09741@kauai.newjersey.sco.com>, Jonathan Schilling writes >So I think the bottom line is: adding throw()'s can help with some >applications, but make sure your compiler is optimizing based on >them first. Thanks for the info. I think that we need to have a major campaign with implementors to support throw() optimisations because without it we have a serious problem in writing efficient portable code. Francis Glassborow Chair of Association of C & C++ Users 64 Southfield Rd Oxford OX4 1PA +44(0)1865 246490 All opinions are mine and do not represent those of any organisation [ 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 ]