[C++-sig] Re: Boost.Python bug

[Niall Douglas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5 Oct 2003 at 16:29, David Abrahams wrote:

> > You just need to cast off the throw(). This probably makes undefined
> > behaviour though as some PCS's mangle their symbols differently for
> > null throw()'s though TBH I can't see how any PCS could penalise you
> > as the direction of effect is opposite.
> 
> I'm sorry; I meant "do you know of a workaround I can use in the
> Boost.Python internals?"

Unfortunately I don't understand how they work, and so I didn't know 
whether the obvious solution would work or not. I've patched pyste to 
add the relevent cast but that's no use to you.

> >> There are lots of corner cases which don't work on various
> >> compilers due to bugs in the compilers.  I don't feel the need to
> >> document each one that we discover.  HOwever, if you want to
> >> contribute an appropriate doc patch I'll gladly check it in.
> >
> > Well I was more thinking of saving you time in having to deal with
> > support which I know sucks time from any maintainer.
> 
> Thanks, but if you really want to save me time, you'll submit the doc
> patch.

I hate to sound stupid, but is a doc patch like a GNU diff of the 
documentation HTML? If so, do I email it to you?

Cheers,
Niall





-----BEGIN PGP SIGNATURE-----
Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2

iQA/AwUBP4CBFsEcvDLFGKbPEQIvUwCdGSwGeprBkGOJbt9X6UoU+XmrexcAnR+L
nrhXazkjmKzAi4epJHt1SVo0
=CLyS
-----END PGP SIGNATURE-----