|
|
Boost Testing : |
From: Alisdair Meredith (alisdair.meredith_at_[hidden])
Date: 2005-04-19 07:37:41
Vladimir Prus wrote:
> Does this mean static linking to runtime, or complete avoidance of
> shared libraries? I'd find it surprising that borland does not allows
> to work with DLLs.
Borland seem happy to live with their known bugs until the next release
- whenver that is. They have announced they are working on it again,
but until then we are dealing with a 3 year old compiler, with most of
its bugs unpatched.
The are enough bugs in the dynamic RTL vs the statically linked RTL
that it is simply best avoided - and that is the advice we give out in
the Borland support groups.
Likewise, always disable function inlining, as the optimiser often
fails to call destructors in stack unwinding if an exception is thrown.
I agree it is surprising these bugs are still present after 3 years or
more, but Borland have not been too focused on their own compiler over
the last few years. I believe that is changing now, but until then we
must support the compiler that is out there.
> I think it's possible. Say, we can add
>
> <toolset>borland:<link-runtime>static
>
> to Boost-wide requirements to force static linking to runtime on
> borland.
That would be great!
AlisdairM