Thank you, I appreciate English corrections very much -- I'm not a native English speaker, so I likely made some phrases that sound weird.

I will review and apply over the weekend, I may want to tweak some things. (and if you can then review my corrections, I will appreciate it :) )

I'd be happy to review any adjustments you make to this PR.

I committed small changes on top and merged. The version on https://castle-engine.io/modern_pascal is already updated to reflect the improvements. Thank you again!

Feel welcome to correct after me (see my commit 3a49511 ), simply create new PR :) In particular I remade the paragraph about "memory being zeroed" to say more explicitly what I intended:

A helpful property we can use to write robust destructors (that can handle half-created instances) is that the memory of the class is guaranteed to be zeroed right before the constructor code is executed. So we know that at the beginning, all class references are nil, all integers are 0 and so on. The strategy for writing a robust destructor is thus: "be prepared that any field may still be zero, and handle it without errors".

I read 3a49511 and would make one small change: I would change "code" to "the code" in:

In effect, code below works without any memory leaks, even though constructor execution is interrupted

(Sorry, this is too trivial for a new PR.)

I read 3a49511 and would make one small change: I would change "code" to "the code" in:
In effect, code below works without any memory leaks, even though constructor execution is interrupted
(Sorry, this is too trivial for a new PR.)

Thanks, done! ( d1212c9 )