ftp.delorie.com/archives/browse.cgi | search |
From: | "Seyil Yoon" <wings AT interlog DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Exceptions in v2.02 |
Date: | Fri, 15 Jan 1999 16:00:26 -0500 |
Organization: | Data Recovery Labs |
Lines: | 20 |
Message-ID: | <77oajn$if1$1@nntp3.uunet.ca> |
References: | <77nrlj$cop$1 AT nntp3 DOT uunet DOT ca> <7832 DOT 990115 AT bspu DOT unibel DOT by> |
NNTP-Posting-Host: | 209.47.85.27 |
X-Newsreader: | Microsoft Outlook Express 4.72.3155.0 |
X-MimeOLE: | Produced By Microsoft MimeOLE V4.72.3155.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Alexander Bokovoy wrote in message <7832 DOT 990115 AT bspu DOT unibel DOT by>... >> catch(CException Exception) >try this variant of statement (it compiles and works for me without any warnings): >catch(CException& Exception) Hmm ... thank you for the help. I would still like to know if there is anything syntactically incorrect with the statement catch(CException Exception) It seems to be the way the statement is used in many books (including the Stroustrup book), so I would assume that, at the very least, it is correct (questions of style and what not being disregarded).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |