--- In Boost-Users@y..., "Gennadiy E. Rozental" wrote:

This was discussed during Boost.Test review. Peter some time ago made a changes in boost::shared_ptr that allows it to be used with Borland 5.5 namely in the situation you described.

Gennadiy.

Hi...could you clarify this? All I noticed was that shared_ptr had that compile time check for an incomplete type removed, whereas scoped_ptr still has it. Are you saying that if I switch from scoped_ptr to shared_ptr the destructor will get called? Regards, Brian Neal

From: "Brian"

--- In Boost-Users@y..., "Gennadiy E. Rozental" wrote:

...

This was discussed during Boost.Test review. Peter some time ago made a changes in boost::shared_ptr that allows it to be used with Borland 5.5 namely in the situation you described.

Gennadiy.

Hi...could you clarify this? All I noticed was that shared_ptr had that compile time check for an incomplete type removed, whereas scoped_ptr still has it. Are you saying that if I switch from scoped_ptr to shared_ptr the destructor will get called?

Yes, shared_ptr will call the destructor. It only requires a complete type at construction time.

From: "Brian"

--- In Boost-Users@y..., "Peter Dimov" wrote: ...

...

Yes, shared_ptr will call the destructor. It only requires a complete type at construction time.

Hmmm... we tried using shared_ptr today and our destructors were still not called. This is with C++ Builder 5.5. I am now trying to see if another department has a copy of 6.0 we could try.

What version of boost? Can you post a minimal example? It works here: testbed.cpp: #include class X; boost::shared_ptr<X> create(); int main() { boost::shared_ptr<X> px = create(); } testbed2.cpp: #include #include <iostream> class X { public: X() { std::cout << "X::X()\n"; } ~X() { std::cout << "~X::X()\n"; } private: X(X const &); X & operator= (X const &); }; boost::shared_ptr<X> create() { boost::shared_ptr<X> px(new X); return px; } Output: C:\Documents and Settings\pdimov\My Documents\Projects\testbed>bcc32 -v testbed.cpp testbed2.cpp Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland testbed.cpp: testbed2.cpp: Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland C:\Documents and Settings\pdimov\My Documents\Projects\testbed>testbed X::X() ~X::X()

From: "Nicola Musatti"

Peter, the Borland 5.5.1 compiler behaves differently according to whether you enable the generation of debugging information or not. To further confuse the issue, the command line compiler has debug information generation turned off by default, while BCB5 has it on.

The problem with shared_ptr only happens with debugging information turned on. The 1.28.0 version of shared_ptr is handled correctly by the 5.6.1 compiler (the one in BCB6 with Update 2 installed).

Once again, can someone please post an example that demonstrates the problem? I did use the -v switch with my example, and it worked.

Peter Dimov wrote:

From: "Nicola Musatti"

[...]

...

The problem with shared_ptr only happens with debugging information turned on. The 1.28.0 version of shared_ptr is handled correctly by the 5.6.1 compiler (the one in BCB6 with Update 2 installed).

Once again, can someone please post an example that demonstrates the problem? I did use the -v switch with my example, and it worked.

I was too hasty. shared_ptr from 1.28.0 appears to work with Borland's 5.5.1 compiler regardless of debug switch setting. Cheers, Nicola Musatti

Hi...could you clarify this? All I noticed was that shared_ptr had that compile time check for an incomplete type removed, whereas scoped_ptr still has it. Are you saying that if I switch from scoped_ptr to shared_ptr the destructor will get called?

The problem still persists with C++ Builder 6 and scoped_ptr, shared_ptr is OK though. John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm