On 20 May 2009, at 22:13, Micha Nelissen wrote:
Jonas Maebe wrote:
On 20 May 2009, at 22:01, Jonas Maebe wrote:
The problem you have right now is that the program and each of
your libraries each contain their own copy of the exception class,
and therefore do not recognise (Pascal) exceptio
In our previous episode, Micha Nelissen said:
> Jonas Maebe wrote:
> > On 20 May 2009, at 22:01, Jonas Maebe wrote:
> >> The problem you have right now is that the program and each of your
> >> libraries each contain their own copy of the exception class, and
> >> therefore do not recognise (Pasc
Jonas Maebe wrote:
On 20 May 2009, at 22:01, Jonas Maebe wrote:
The problem you have right now is that the program and each of your
libraries each contain their own copy of the exception class, and
therefore do not recognise (Pascal) exceptions raised by any of the
others.
Well, that and the
On 20 May 2009, at 22:01, Jonas Maebe wrote:
The problem you have right now is that the program and each of your
libraries each contain their own copy of the exception class, and
therefore do not recognise (Pascal) exceptions raised by any of the
others.
Well, that and the fact that more
Jonas,
Thank you very much for the explanation.
-SG
--
This email is fiction. Any resemblance to actual events
or persons living or dead is purely coincidental.
Seth Grover
sethdgrover[at]gmail[dot]com
___
fpc-pascal maillist - fpc-pascal@lists.free
On 20 May 2009, at 21:50, Seth Grover wrote:
Imagine this scenario. I have an FPC-compiled executable (fpcprog) and
two FPC-compiled shared object libraries (libfpc1.so and libfpc2.so).
Each of which installs its own set of signal handlers:
That's not possible. Per process, Unix only supports
Actually, looking closer at this fix (bug 12704, fixed in rev 13077),
it might not be exactly what I was expecting it to be. Maybe somebody
could clear up something I've been thinking about for a while now.
Imagine this scenario. I have an FPC-compiled executable (fpcprog) and
two FPC-compiled sha
