Python 2.0

[Yukihiro Matsumoto]

Hisao Suzuki <suzuki611 at okisoft.co.jp> writes:

|In article <87pv3eorg4.fsf at ev.netlab.co.jp>,
|Yukihiro Matsumoto <matz at netlab.co.jp> wrote:
|> BTW, did I say Ruby can invoke arbitrary destructors specified by
|> arbitrary users?  It can't.
|
|Is this your mental premise in your opinion about garbage
|collection?  Then, the unpredictability might not be matter at
|all...

I was talking about real GC in general.  I was saying real GC does not
fall into unpredictable automatically.  As for Python, I agree with
your statement in <u37lpndko6.fsf at ares.sys1.ngo.okisoft.co.jp>:

|Even if Python has "real" GC someday, IMHO, the GC should be
|used only to imitate infinite resources.  For the sake of
|conceptual simplicity, the future Python should still use
|reference counting both to invoke __del__ methods and to free
|storages; the GC routine should be used as the last resort.

						matz.