| Re: [AD] Exception Support for Allegro |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Exception Support for Allegro
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Wed, 5 Oct 2005 14:07:06 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=UyyrHOJfsG3SbpsL4TzGcNh2atrknlwXErX1q3ZfK4caUM5QO0bh8H9uL0xlUKyb+m5D0qG/M5/LdSDvIln2oq/s0M/Yqj+lMsRYOJuExbtn47e3KGTdybRYB6y8OaIiIn1zvPGdOGMOKT7ORdPYCbTJYGpRaDGglDnNRLVkZdg=
On Wednesday 05 October 2005 06:57 am, Evert Glebbeek wrote:
> Allegro is a C library. You cannot safely use exceptions from callbacks.
These two statements have nothing to do with each other. Just because it's C
doesn't make exceptions unsafe in callbacks. You can use -fexceptions to
safely allow exceptions in callbacks from C. It's where/how those callbacks
are used that matters, and that makes no difference if it's C or C++.
If Allegro was a C++ library, would you force -fno-exceptions because the
callbacks are unsafe for exceptions? If not, then why disallow them as a C
library? As long as it's documented how the callbacks are called, it should
be up to the programmer to decide if it's safe to use them. If there's
problems, then it's their fault.