Poll: Are you stuck on an old Boost release due to a defective compiler?
Hallo, I'm trying to gauge the number of Boost users that are actually using an older version of the libraries because they have to use a compiler that's not supported by more recent versions of the libraries they use. As for myself, I work on a project where Borland's BCB6 is used and we're stuck with Boost 1.31 mostly because more recent versions of uBlas do not work with our compiler. Cheers, Nicola Musatti
Nicola Musatti wrote:
Hallo, I'm trying to gauge the number of Boost users that are actually using an older version of the libraries because they have to use a compiler that's not supported by more recent versions of the libraries they use.
As for myself, I work on a project where Borland's BCB6 is used and we're stuck with Boost 1.31 mostly because more recent versions of uBlas do not work with our compiler.
We're stuck on boost-1.32.0 with BCB6 due to ublas (but we managed to patch ublas enough to get basic matrix, vector and their operations working along with lu_* functions working which is what we really needed). Cheers Russell
"Nicola Musatti" wrote:
I'm trying to gauge the number of Boost users that are actually using an older version of the libraries because they have to use a compiler that's not supported by more recent versions of the libraries they use.
As for myself, I work on a project where Borland's BCB6 is used and we're stuck with Boost 1.31 mostly because more recent versions of uBlas do not work with our compiler.
I am able to use latest Boost libraries with BCB6 out of the box (serialization plus dozen of others). I periodically check the CVS whether anything got broken. However I am offloading as much functionality as possible from BCB to VC++ since BCB randomly crashes when a project grows too big. As for ublas: wasn't it possible to extract 1.31 ublas and replace the new version? I know how nasty this is but Boost releases are only twice a year. /Pavel
Pavel Vozenilek wrote:
However I am offloading as much functionality as possible from BCB to VC++ since BCB randomly crashes when a project grows too big.
I've had this for a long time and finally listened to the posts on the borland groups about disabling class explorer permanently. I haven't had any compilation/ide crashes since (still occasional debugger crash but not very often) for over a week now on too machines. If you haven't, try it. Delete the registry key in HKCU\Software\Borland\C++Builder\6.0\Known IDE Packages which ends in bcbcxp60.bpl (well I renamed it to bcbcxp60.bpl.old) instead and the IDE prompts you to disable it next time you start. It has been *much* more stable since.
As for ublas: wasn't it possible to extract 1.31 ublas and replace the new version? I know how nasty this is but Boost releases are only twice a year.
I've thought about this at the weekend and will attempt it with 1.33.1 when I get some free time to try and start building under BDS. Cheers Russell
"Russell Hind" wrote: [ BCB bugs ]
I've had this for a long time and finally listened to the posts on the borland groups about disabling class explorer permanently. I haven't had any compilation/ide crashes since (still occasional debugger crash but not very often) for over a week now on too machines. If you haven't, try it. Delete the registry key in HKCU\Software\Borland\C++Builder\6.0\Known IDE Packages
which ends in bcbcxp60.bpl (well I renamed it to bcbcxp60.bpl.old) instead and the IDE prompts you to disable it next time you start.
It has been *much* more stable since.
The IDE crashes are the smaller problem (Class Explorer is disabled, IDE crashes say every few hours). I've got random internal compiler errors, in project consisting from small, separate DLLs. They can get "worked around" by shuffling code, splitteing sources or renaming variables. This randomness is the main reason why I limit my dependence on BCB. /Pavel
Nicola Musatti wrote:
Hallo, I'm trying to gauge the number of Boost users that are actually using an older version of the libraries because they have to use a compiler that's not supported by more recent versions of the libraries they use.
As for myself, I work on a project where Borland's BCB6 is used and we're stuck with Boost 1.31 mostly because more recent versions of uBlas do not work with our compiler.
I'm happy to say that last month, I bit the bullet and moved our last remaining VC6.5(boost.1.30.2) product to vc7.1 & boost.1.33.1. This ended up being only a few hours work, primarily related to the changes in the iterators library. I ended up wishing I did this much sooner. Jeff
We're stuck on boost 1.32.0 but spirit 1.6.0 with BCB6
participants (5)
-
Jeff Flinn -
Nicola Musatti -
Pavel Vozenilek -
Russell Hind -
Simon Carter