Winter Madness - Passing Python objects as Strings

[Nigel Rantor]

Hendrik van Rooyen wrote:
> It is not something that would find common use - in fact, I have
> never, until I started struggling with my current problem, ever even
> considered the possibility of converting a pointer to a string and 
> back to a pointer again, and I would be surprised if anybody else
> on this list has done so in the past, in a context other than debugging.

Okay, well, I think that's probably because it sounds like a fairly good 
way of making things slower and hard to port to another interpreter. 
Obviously depending on how you're achieving this.

If you need to pass infomation to a thread then I would suggest there's 
better, quicker, more reliable, portable and comprehensible ways of 
doing it.

It just smells to me that you've created this elaborate and brittle hack 
to work around the fact that you couldn't think of any other way of 
getting the thread to change it's behaviour whilst waiting on input.

Just my 0.02p

   n