Re: tip50 Accepted

On Dec 19, 10:04 am, Arnulf Wiedemann <arn...@xxxxxxxxxxxxxxxx> wrote:
For more information on new/added features in itcl please look
at:http://wiki.tcl.tk/itcl-ng

So this is interesting. I follow the link http://wiki.tcl.tk/19873 and
see this comment:

apw 2008-12-11 Again 3 days of heavy searching and fixing memory
leaks. And now beta 1 version of itcl-ng (itcl4.0b1) is released see:
[6]. This is also the version to be bundled with Tcl core 8.6 beta.

Is it really true that memory leaks are being plugged in code which is
being included in the Tcl core?

MEMORY LEAKS! WTF! Does anyone remember why Tcl was a safe language?
Lack of memory leaks was one reason. Another reason: lack of morons
including code which might contain memory leaks. Another reason: lots
of non-morons telling the morons to take their leaking code somewhere
else.

Mr. A.R.N, get a clue. Code which leaks memory is not beta code. It is
trash code, junk, poop. Not beta, not alpha, just junk.

It is really unbelievable that a developer would be hunting down
memory leaks and a few weeks later releasing code. More unbelievable
is that other core developers would allow this nonsense. Obviously
this person doesn't understand their code.

Again: memory leaks! On December 11, two weeks ago. Now the author
thinks the code is okay for everyone else? Core maintainers agree? Is
there a point to this? This kind of laziness leads to huge disasters
like the current MS IE browser bug, or the Debian cryptography
screwup. What happens is you get a batch of new programmers who fail
to understand the motivations and goals of the existing code. Their
goal is to add "missing features" to the language. Somehow memory
leaks are worth the new features.

This is a pretty easy call: if your code has any memory leaks, if you
were recently engaged in ridding your code of memory leaks, why do you
think it is anywhere close to being included in code which has no such
problems? Do Tcl Core maintainers actually trust someone hawking pre-
alpha code? The ultimate result of memory leaks is application
failure, sometimes server (as in total machine) failure. It is nearly
unbelievable that code in such a state of development would even be
considered for inclusion in Tcl core. This is serious stuff. If the
developer can't prevent memory leaks, why inflict this disaster on
people who just want to use what they think is nice, safe Tcl code?
.

Quantcast