Re: Nice example about the "inefficiently" of the tcl "c" api.

On 09.09.24 11:11, undroidwish wrote:

On 9/9/24 08:04, aotto1968 wrote:
 

...
I posted the code above just to show some simple facts:
1. Tcl has no "NULL" object → "NULL" is not even defined in Tcl
...

 I'd call this a non-argument performance and otherwise given that
even the inventor of NULL regretted this his invention, see
 https://en.wikipedia.org/wiki/Tony_Hoarehttps://en.wikipedia.org/wiki/Tony_Hoare
 in this quote
 "I call it my billion-dollar mistake. It was the invention of the null reference in 1965. At that time, I was designing the first comprehensive type system for references in an object oriented language (ALGOL W). My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn't resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years."

→ you compare "apple" with "orange"
a NULL in "C" is not the same as an "None" in python or a "null" in java
→ this guy complain about the "NULL-POINTER" mistake which crate a dump in misuse etc
→ the "NULL" I speak about is to introduce a "non existing reference" as an information which is **not**
   a NULL-pointer is "C".
   example: if you lookup "otto" in a database than you get a "non existing NULL" back it "otto" does not exists
            TCL has *no** default "NULL" type to indicate this issue, TCL can give an empty string back like "" **but**
            if the "empty string" is the real value for "otto" in the database THAN you can NOT distinguish the both cases
            1) "otto" does NOT exists
            2) "otto" exists BUT has the value ""