On 2014-10-30 10:23, John Colvin wrote:

Slightly derailing the conversation, but I see this all the time...

Isn't the situation actually this:

GC allocated objects are not guaranteed to be de-allocated before
program termination.
If a GC allocated object is deallocated, its destructor *is* guaranteed
to be called.
Except:
Destructors are not called for arrays of objects, whether they are
structs or emplaced classes, even when they are de-allocated.

Yes, that's the longer explanation :)

--
/Jacob Carlborg
  • Re: D/Objective-C 64bit Christian Schneider via Digitalmars-d-announce
    • Re: D/Objective-C 64bi... Jacob Carlborg via Digitalmars-d-announce
      • Re: D/Objective-C ... Christian Schneider via Digitalmars-d-announce
        • Re: D/Objectiv... Jacob Carlborg via Digitalmars-d-announce
          • Re: D/Obje... Christian Schneider via Digitalmars-d-announce
            • Re: D... Jacob Carlborg via Digitalmars-d-announce
              • R... John Colvin via Digitalmars-d-announce
                • ... Jacob Carlborg via Digitalmars-d-announce
              • R... Christian Schneider via Digitalmars-d-announce
                • ... Jacob Carlborg via Digitalmars-d-announce
                • ... Christian Schneider via Digitalmars-d-announce
                • ... Jacob Carlborg via Digitalmars-d-announce
                • ... Christian Schneider via Digitalmars-d-announce
                • ... Christian Schneider via Digitalmars-d-announce
                • ... Michel Fortin via Digitalmars-d-announce
                • ... Christian Schneider via Digitalmars-d-announce
                • ... Jacob Carlborg via Digitalmars-d-announce
                • ... Christian Schneider via Digitalmars-d-announce

Reply via email to