A
andrew.may
Guest
4With a GC, the developer manages the lifecycle of an object by controlling the object reference's scope. If they don't control the reference scope, then deleting the object manually will just lead to invalid handles in hard to track down locations. This "I don't trust the GC " worry was one that a lot of C programmers had when they started Java/C++ ... that debate is long since settled in favour of trusting the GC - a google session should find a lot of articles. If I came across a load of OO code that didn't trust the GC & deleted objects manually, I would run & hide (or just double the estimates of time required to support it). (It would have the same code-smell to me as seeing masses of RELEASE statements in ABL).
Continue reading...
Continue reading...