question regarding borland

When I try to compile for Borland 5.64 - which always worked
before, I get

C:-Boost134-bin.v2-libs-serialization-test-test_array_text_w
archive.test-borland-5.6.4-debug
Compiler output:
test_array.cpp:
Support for Borland compilers older than BCB2006 is
deprecated in Boost 1.34

And no other message which looks like the compiler isn't
invoked.

a) Where does this message come from?
b) Why is it there.  How can some other library component
know whether or
not the serialization library will work with borland?

Robert Ramey



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Robert Ramey wrote:

> When I try to compile for Borland 5.64 - which always
worked before, I get
> 
>
C:-Boost134-bin.v2-libs-serialization-test-test_array_text_w
archive.test-borland-5.6.4-debug
> Compiler output:
> test_array.cpp:
> Support for Borland compilers older than BCB2006 is
deprecated in Boost
> 1.34
> 
> And no other message which looks like the compiler
isn't invoked.
> 
> a) Where does this message come from?
> b) Why is it there.  How can some other library
component know whether or
> not the serialization library will work with borland?

I don't know. This message is not emitted by Boost.Build, so
I
suspect it's Boost.Config, or something.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Robert Ramey wrote:
> When I try to compile for Borland 5.64 - which always
worked before,
> I get
>
C:-Boost134-bin.v2-libs-serialization-test-test_array_text_w
archive.test-borland-5.6.4-debug
> Compiler output:
> test_array.cpp:
> Support for Borland compilers older than BCB2006 is
deprecated in
> Boost 1.34
> And no other message which looks like the compiler
isn't invoked.

That's a *warning* from the compiler, emitted from
Boost.Config.  Other than 
the message being emitted everything should still build as
before.

HTH, John. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Hallo, Robert.

Robert Ramey <ramey <at> rrsd.com> writes:

> When I try to compile for Borland 5.64 - which always
worked before, I get 
>
C:-Boost134-bin.v2-libs-serialization-test-test_array_text_w
archive
>.test-borland-5.6.4-debug
> Compiler output:
> test_array.cpp:
> Support for Borland compilers older than BCB2006 is
deprecated in Boost 1.34
> 
> And no other message which looks like the compiler
isn't invoked.
> 
> a) Where does this message come from?
> b) Why is it there.  How can some other library
component know whether or
> not the serialization library will work with borland?

This message is generated by the
boostconfigcompilerborland.hpp header. It's
useless and annoying, but harmless. If I remember correctly
this is the result
of a discussion about whether 1.34 should still provide
support for BCB6. The
compromise was that support for this compiler would be
provided as "deprecated"
for this release and removed afterwards. Alisdair Meredith
probably knows the
story better than I do.

As each developer is free to decide which compilers to
support, I don't see why
support for BCB6 should be removed arbitrarily, at least as
long as testing is
performed regularly. All the more so considering that it is
still commonly used
within the Borland developer community.

Cheers,
Nicola Musatti


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Nicola Musatti wrote:

> This message is generated by the
boostconfigcompilerborland.hpp
> header. It's useless and annoying, but harmless.

What bothers me about it is its presumptiousness.  How can
author of one library insert such a message into another
library?

Its also incorrect.  BOOST_STATIC_ERROR won't work with
with borland?  Of course it will.

Are users of borland prohibited from using boost?  Of
course not.

It also couples boost to a particular set of compilers and
does not scale.  How about a message regarding - Digital
Mars compilers?  Why isn't such a message in there?

It really reflects an outdated view that should be a
tightly
coupled set.  This might have been possible (though still
a bad idea) at one time - but is completely unsustainable
now.

> As each developer is free to decide which compilers to
support, I
> don't see why support for BCB6 should be removed
arbitrarily, at
> least as long as testing is performed regularly. All
the more so
> considering that it is still commonly used within the
Borland
> developer community.

amen,

Robert Ramey



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Robert Ramey wrote:

> Nicola Musatti wrote:
> 
>> This message is generated by the
boostconfigcompilerborland.hpp
>> header. It's useless and annoying, but harmless.
> 
> What bothers me about it is its presumptiousness.  How
can
> author of one library insert such a message into
another
> library?

At all events, this is not a question for the boost-build
list.
Everyone, please follow-up on boost-devel.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build