[Python-Dev] are CObjects inherently unsafe? (original) (raw)
Michael Hudson mwh at python.net
Mon Dec 8 05:02:32 EST 2003
- Previous message: [Python-Dev] are CObjects inherently unsafe?
- Next message: [Python-Dev] Re: are CObjects inherently unsafe?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greg Ewing <greg at cosc.canterbury.ac.nz> writes:
Michael Hudson <mwh at python.net>:
Why a void* then? That's particularly unassertive. char* would be better, surely... A string isn't the only thing that could usefully be used as a descriptor.
What else would you consider useful? I'm only really aware of the most straightforward uses of CObjects (and wonder if the advanced uses actually see much use...).
Cheers, mhw
-- Just point your web browser at http://www.python.org/search/ and look for "program", "doesn't", "work", or "my". Whenever you find someone else whose program didn't work, don't do what they did. Repeat as needed. -- Tim Peters, on python-help, 16 Jun 1998
- Previous message: [Python-Dev] are CObjects inherently unsafe?
- Next message: [Python-Dev] Re: are CObjects inherently unsafe?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]