From: AlisdairM (alisdair.meredith_at_[hidden])
Date: 2006-01-31 03:36:08
Jeff Garland wrote:
> I understand, but that just means 1.34 will be delayed for fixes to
> these outdated relics and new lousy compilers. We would be better
> making a clean break now and letting folks with old compilers stick
> with 1.33.1.
That is harsh for Borland users.
The new compiler was released AFTER 1.33.1, with which needs to update
several workarounds and then config file before compiling as well as
If 1.34 does not support Borland either you are really hurting these
people, as they have a shiny new improved compiler, but no Boost
support and three choices:
i/ carry on using a broken compiler, compatible with Boost but with
serious bugs that don't show up in the Boost tests.
ii/ move to the new compiler that fixes the most serious compiler bugs,
but does not have ANY boost support, so stop supporting BOost
iii/ Move to the new compiler as above, and fix Boost for yourself,
knowing that many other Borland customers are doing the same.
(iii) will likely lead to a fork of the Boost project, just to support
the Borland compiler as this compiler IS used with these libraries in
large production systems today.
I will happily assist library maintainers hunting down and eradicating
support for older Borland compilers, so long as the most recent is
supported (until such time that 'most recent' is reasonably conforming
and no longer auto-deprecated when a new compiler is released)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk