A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-June/045631.html below:

[Python-Dev] Heap allocated type objects from C

[Python-Dev] Heap allocated type objects from C [Python-Dev] Heap allocated type objects from C"Martin v. Löwis" martin at v.loewis.de
Sat Jun 26 06:52:32 EDT 2004
Eric Huss wrote:
> First, could someone tell me if I took the correct route for creating a
> type object on the heap (based on my patch).
> 
> Second, shouldn't there be a more direct API for doing this?  Perhaps a
> more generalized interface to type_new(), or maybe something completely
> new??

I don't understand why the patch needs to be so complicated. Why can't
you just make a global function that returns new type objects which
are struct seqs? IOW, why do you need the factory type? Type objects
are callable themselves, so they act as factories.

Regards,
Martin


More information about the Python-Dev mailing list

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