AW: AW: AW: AW: [C++-sig] New implementation for opaque_pointer_c onve rter

[Gottfried.Ganssauge at HAUFE.DE]

> I'm sorry to say that this version causes an illegal memory free()
> call, according to VC++'s debug mode.

How did you manage to provoke that failure?
I'm running like this:
  boost-rc-1.30\libs\python\test>bjam -sBUILD=debug-python opaque
  ...found 2038 targets...
  ...updating 2 targets...
  python-test-target
..\..\..\libs\python\test\bin\opaque.test\msvc\debug-python\runtime-link-dyn
amic\opaque.test
  Adding parser accelerators ...
  Done.
  running...
  [6285 refs]
  python-runtest-target
<libs!python!test\opaque.run\msvc\debug-python\runtime-link-dynamic>
opaque.run
  Adding parser accelerators ...
  Done.
  running...
  [6285 refs]
  ...updated 2 targets...

  boost-rc-1.30\libs\python\test>

I obtained the sources this morning from the CVS and applied my
opaque_pointer.patch.3 I sent to you yesterday.
Unfortunately bjam -sBUILD=debug failed because it linked the python_d-libs
but tried to run with python.exe. When I removed the python_d-libs it
wouldn't link at all asking for the python_d-libs...

My compiler ist MSVC 6 SP5 which I'm also using for my production projects

clueless ...

Gottfried