-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 03 September 2003 15:56, Paul A. Bristow wrote:
> #ifdef _MSC_VER // or BOOST_MSVC?
> #pragma warning (disable : 4511) // copy operator could not be generated
> #pragma warning (disable : 4512) // assignment operator could not be
> #endif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 20 August 2003 20:41, Maciej Sobczak wrote:
> This is my first attempt to build Boost 1.30.2 on FreeBSD with gcc 3.2
> installed.
Debian 3.0/x86 here.
> The command:
> $ tools/build/jam_src/bin.freebsd/bjam "-sTOOLS=gcc"
> builds Boost u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 20 August 2003 02:02, Trey Jackson wrote:
> It appears that stlport is only used with gcc 2.95.3 (and in Windows
> with Intel's C++ compiler and MS C++ 6.0).
>
> Is boost moving away from supporting stlport? Or are the regressions
> not b
lieve that the resulting
chaos is much smaller than it could be and better than the status quo. It
also means that mistakes will be made, but I'm willing to make them. I have
the hope that we can agree on a common ABI for most cases and the rest can
still use other means. Not daring to make a
fic or describing a problem differently than 'doesn't work'.
Ulrich Eckhardt
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
de that doesn't otherwise use any 'real code'
from boost...
Ulrich Eckhardt
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
planation
> of why.
There is on rather hackish way to use static linkage. We simply setup three
.cpp-files that included the .cpp-files from out of the boost sourcetree.
Works fine for 1.28 and 1.29 and only required one conditional for 1.30. If
there is interest, I can p
stem' in this case and 'ABI-tag' an identifier for the
compiler, possibly including the stdlib. (note: STLport already uses such a
scheme, I'd prefer just stealing their ABI-tags if there are no good reasons
to do otherwise).
Just my 2ยข
Ulrich Eckhardt
__
idiom ?
cheers
Ulrich Eckhardt
Outline:
- takes two types as template-arguments, the types of the owners that are to
be connected.
- bidi_ptr<>s come in pairs, bidi_ptr is complementary to bidi_ptr
- every bidi_ptr mainly consists of two pointers, one points to the owning
object (m_ow