Sent from my iPhone
On Mar 13, 2009, at 11:19 AM, Stefan Seefeld
wrote:
I'm willing to participate, in particular, if other folks such as
David, I notice you already indicated support. Could we team up for
this ?
Sure, I'd be glad to
___
Niall Douglas wrote:
I would say that any GSoC project should choose *one* of the above
rather than try combining them. Better to do one thing well and in
stages than many things at once (unless you have loads of spare
time!).
I agree. (I wouldn't mind seeing projects for all of the abov
Oh, Thank god, so at least it is not only me. :)
I just double-check this, and this behavior not only happened in debug
build, it will happen in release build too,
But the pointer showing up would not be 0x but something arbitrary.
P.S.: I have already changed to follow you guys' advices
I just reproduced the behaviour. Out of habit, I compiled with release the
last time. Using a debug build, I get the same behaviour (using const&,
non-const& etc).
I'm guessing this is a case of "undefined behaviour" resulting from mixing
Debug/Release dll's. Changing to Release (or reading Dave
That is very very strange. Removing const should not change anything. If it
does... well... black magic?
The debugging link Dave provided is very important if you must compile debug
versions. I remember something about not mixing debug/release versions of
python but I just avoid the issue by never
