Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-December/040748.html below:

[Python-Dev] are CObjects inherently unsafe?

• Previous message: [Python-Dev] are CObjects inherently unsafe?
• Next message: [Python-Dev] are CObjects inherently unsafe?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> It had occurred to me that you could use this field for this purpose,
> but it hadn't occurred to me that this might have been the *intent* of
> this field.
> 
> Why a void* then?  That's particularly unassertive.  char* would be
> better, surely...

Jim only knows...  Probably a case of mistaken generality. :-)

--Guido van Rossum (home page: http://www.python.org/~guido/)

• Previous message: [Python-Dev] are CObjects inherently unsafe?
• Next message: [Python-Dev] are CObjects inherently unsafe?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4