How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?
john at castleamber.com
Tue Aug 24 23:50:23 CEST 2010
David Kastrup <dak at gnu.org> writes:
> John Bokma <john at castleamber.com> writes:
>> On the other hand: some people I knew during my studies had no problem
>> at all with introducing countless memory leaks in small programs (and
>> turning off compiler warnings, because it gave so much noise...)
>> As for electrical engineering: done that (BSc) and one of my class
>> mates managed to connect a transformer the wrong way
>> around.... twice. Yet he had the highest mark in our class.
> Anybody worth his salt in his profession has a trail of broken things in
> his history.
Sure. The long version is: he blew up his work when he connected the
transformer wrong. He borrowed someone else's board and blew that one up
> The faster it thinned out, the better he learned.
He he he, his internships went along similar lines. Maybe he loved to
blow up things.
> The only reliable way never to break a thing is not to touch it in the
> first place. But that will not help you if it decides to break on its
I don't think transfomers connect themselfs in the wrong way ;-). I
agree with that accidents do happen, but some people just manage to make
accidents happen way above average. And in that case they might start to
think if it's a good idea them touching things.
John Bokma j3b
Blog: http://johnbokma.com/ Facebook: http://www.facebook.com/j.j.j.bokma
Freelance Perl & Python Development: http://castleamber.com/
More information about the Python-list