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

Showing content from https://mail.python.org/pipermail/python-dev/1999-September/001014.html below:

[Python-Dev] Tackling circular dependencies in 2.0?

• Previous message: [Python-Dev] Tackling circular dependencies in 2.0?
• Next message: [Python-Dev] Tackling circular dependencies in 2.0?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[Guido van Rossum]
> If I remember well, the only destructors not called would be __del__
> methods, since the dependencies between to-be-deleted instances are
> unknown to the collector.  Regular (C-level) destructors would of
> course be called.

Seems to me that the dependencies among to-be-deleted arbitrary C objects
are equally unknown to the collector.  Assuming there's a fundamental
difference between objects implemented in Python and objects implemented in
C seems shaky on the face of it.  Or if it's not just a convenient
assumption, on what is it based?

and-what-about-objects-implemented-in-fortran<wink>?-ly y'rs  - tim

• Previous message: [Python-Dev] Tackling circular dependencies in 2.0?
• Next message: [Python-Dev] Tackling circular dependencies in 2.0?
• 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