I've found a topic of 2 and a half years ago stating that the Lambda library was unusable in Borland C++. Now, in version 1.32.0, it continues unusable. The #inclusion of lambda.hpp itself triggers a lot of errors (nof_elems cannot be used without an object, etc...). There was a suggestion on using spirit/phoenix, but it also generates some errors in this compiler. So, my question again is: how to use Lambda functions or something equivalent in Borland C++? Thanks!
"Edson Tadeu" wrote:
I've found a topic of 2 and a half years ago stating that the Lambda library was unusable in Borland C++. Now, in version 1.32.0, it continues unusable. The #inclusion of lambda.hpp itself triggers a lot of errors (nof_elems cannot be used without an object, etc...).
There was a suggestion on using spirit/phoenix, but it also generates some errors in this compiler.
So, my question again is: how to use Lambda functions or something equivalent in Borland C++?
BCB doesn't have new version for more than two years, that's the main problem. I am guessing that trying to port lambda to BCB won't bring other results than prematurely gray hair. /Pavel
Pavel Vozenilek wrote:
"Edson Tadeu" wrote:
I've found a topic of 2 and a half years ago stating that the Lambda library was unusable in Borland C++. Now, in version 1.32.0, it continues unusable. The #inclusion of lambda.hpp itself triggers a lot of errors (nof_elems cannot be used without an object, etc...).
There was a suggestion on using spirit/phoenix, but it also generates some errors in this compiler.
So, my question again is: how to use Lambda functions or something equivalent in Borland C++?
BCB doesn't have new version for more than two years, that's the main problem.
Actually three+ years considering that no one uses CBX, which was a failed product from the beginning. Bcb6 came out 2/1/2002. The Bcb6 compiler was also an incrementally small improvement, ala C++, over the Bcb5 compiler, which was out in 1/31/2000. So over 5 years, Borland has essentially done nothing to improve their compiler's C++ conformance. I should know, since a few years ago I posted numerous C++ compiler bug reports, many taken from Boost, to Borland's bug tracking system, only to watch as Borland did absolutely nothing about them. Not to be negative but I do not think that Borland cares very much about their C++ compiler's conformance to the C++ standard. Instead they have been almost entirely focused, language-wise, on their Object Pascal and Java offerings in the last half decade. Nor does this situation look to be alleviated anytime soon.
Edward Diener wrote:
Not to be negative but I do not think that Borland cares very much about their C++ compiler's conformance to the C++ standard. Instead they have been almost entirely focused, language-wise, on their Object Pascal and Java offerings in the last half decade. Nor does this situation look to be alleviated anytime soon.
Here are some quotes regarding the new version of C++ builder from Feb '05 (from http://bdn.borland.com/article/0,1410,32958,00.html): "We've done some work on conformance for Boost and for ACE. We're going to specifically target boost and some customer complaints. We won't be 100% ANSI compliant" And they state that the product will now use DinkumWare STL rather than STLPort which should help a little too. While this isn't concrete proof, it hopefully is a sign that things will improve with the new release. But only time will tell if they follow through on this. Cheers Russell
Russell Hind wrote:
Edward Diener wrote:
Not to be negative but I do not think that Borland cares very much about their C++ compiler's conformance to the C++ standard. Instead they have been almost entirely focused, language-wise, on their Object Pascal and Java offerings in the last half decade. Nor does this situation look to be alleviated anytime soon.
Here are some quotes regarding the new version of C++ builder from Feb '05 (from http://bdn.borland.com/article/0,1410,32958,00.html):
"We've done some work on conformance for Boost and for ACE. We're going to specifically target boost and some customer complaints. We won't be 100% ANSI compliant"
And they state that the product will now use DinkumWare STL rather than STLPort which should help a little too.
While this isn't concrete proof, it hopefully is a sign that things will improve with the new release. But only time will tell if they follow through on this.
This is getting way off topic, but the saying "When I see it I will believe it", meaning much better Ansi C++ compliance for Borland's C++ compiler in this case, could not be more true.
Edward Diener wrote:
Not to be negative but I do not think that Borland cares very much about their C++ compiler's conformance to the C++ standard. Instead they have been almost entirely focused, language-wise, on their Object Pascal and Java offerings in the last half decade. Nor does this situation look to be alleviated anytime soon.
I believe they are working on a new version using the EDG front-end, which should improve their conformance enormously. I have no idea when they will release this new version though. Ben.
Ben Hutchings wrote:
I believe they are working on a new version using the EDG front-end, which should improve their conformance enormously. I have no idea when they will release this new version though.
They did a preview version of a compiler using EDG for the front-end, but that has been put on hold. I guess they are currently looking at improving the BCB6 compiler for the up-coming release mentioned in my previous post which is a shame as the EDG based compiler did show promise. Cheers Russell
Edson Tadeu wrote:
I've found a topic of 2 and a half years ago stating that the Lambda library was unusable in Borland C++. Now, in version 1.32.0, it continues unusable. The #inclusion of lambda.hpp itself triggers a lot of errors (nof_elems cannot be used without an object, etc...).
There was a suggestion on using spirit/phoenix, but it also generates some errors in this compiler.
So, my question again is: how to use Lambda functions or something equivalent in Borland C++?
Phoenix included with Spirit 1.6.x works on Borland. I already have too much grey hair to continue supporting the compiler :-) Cheers, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
participants (6)
-
Ben Hutchings -
Edson Tadeu -
Edward Diener -
Joel de Guzman -
Pavel Vozenilek -
Russell Hind