In message <7xeid9gtuq....@ruckus.brouhaha.com>, Paul Rubin wrote: > Lawrence D'Oliveiro <l...@geek-central.gen.new_zealand> writes: > >> That reinforces my point, about how easy it was to check the correctness >> of the code. In this case one simple fix, like this ... >> would render the code watertight. See how easy it is? > > Well, no, it's irrelevant how easy it is to fix the issue after it's > pointed out.
In that case, I can similarly discount your attempts to fix up issues with garbage collectors after they’re pointed out, can I not? > Part of the problem is C itself. And yet, what are these complicated garbage collectors, that you intend relying on to work correctly with all their layers of tricks upon tricks, written in? C. -- http://mail.python.org/mailman/listinfo/python-list
