| 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: Fri, 7 Oct 2005 01:39:50 -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=hRN39NH1B0Wo91Cggcm9c32D7e92MotF29ZzH8zqGV8ytDrrakgXkmnXNGE+RFMeFd6iPvMLS48V5jR5BPuht1AaJU7SZa4cESzqVmKuj3Wi+oXNx9lD7uEJcnAz6gUOjTA7ssHE6wzax6pdnivb4+tUUqb+kLwV+HGPvFWPnZI=
On Thursday 06 October 2005 02:08 pm, Serge Semashko wrote:
> C++ is famous for the lack of common ABI
> supported by all compilers, each of the compilers has (or at least can
> have) its own exception handling implementation. Not to mention even
> more trivial things, they even do not have a common naming conventions.
Allegro is not coded in C++, so I don't see what C++ name mangling has to do
with anything here. C symbols *are* the same between compilers of the same OS
(both MinGW and MSVC use the same mangling for C). But what does that have to
do with exceptions?
> And for mingw even throwing exceptions across DLL boundary is a problem
I don't think it's technically across a DLL boundary. You're not throwing an
exception into or out of a DLL, but rather through it. The callback's code
and the code where the exception is caught are both in the program's space.
I'd actually think throwing an exception through a C-code DLL is safer than a
C++ one, since the C DLL has no risk of inadvertantly catching it.