Re: Obstacles for Tcl/Tk commercial application development ?

Darren New <dnew@xxxxxxxxxx> writes:

[snip]

Static typing doesn't give you *any* guarantees of correctness. Maybe
it helps good programmers be better, but it doesn't give you any
guarantees. That's exactly 100% what I'm saying. Why are you arguing
with me? ;-)

Are you teasing me? I guess not, as you write too much for this
discussion being a joke.

proc foo { a b } {
return [expr { a + b }] ;# may bomb!
}

int foo(int a, int b) {
return a + b; // just fine
}

[snip]

Yah. I'm just discussing in general. I like calling people on things
when they make absolute statements that I think are inaccurate,
because occasionally I learn a new absolute truth! :-)

Please quote the text where I made an absolute statement or claimed a
"new absolute truth".

It seems that we are on a different wavelength. As I insist on claiming
a *limited* but quite real effectiveness of static typing on software
quality, you insist on an "all or nothing" view.

If you admit that software testing is necessary, how can you dismiss the
value of a feature that guarantees that *some* bugs does not happen? On
a dynamic language, you need lots of test cases for checking something
that a statically typed language checks while compiling.

All this discussion is summarized, from my part, saying that you have
some opinions wrong (see the first paragraph of this message) but I keep
failing to change your mind, partly because you ignore my warnings about
some things falling outside the coverage of static typing. If you are
interested on pursuing further a clarification about the usefulness of
static typing, ask somebody with a better English skills than me :-)

Last, but not least, in the case I need to implement some bizarre
feature on my datetime or string handling, be assured that the compiler
will point me to the "interesting" places that possibly need to be
changed and, after the change, it will refuse to compile code that does
not obey the checks that describes the new feature. (BTW, this is
something C++ does not do well, the first part due to automatic type
casts, and the second part due to poor expresiveness for type
constraints, something that the C++ community is trying to address on
the next standard).

What language *are* you using? It sure looks like something built on
top of LISP.

It just shares the syntax. The rest is unrelated.

--
Oscar
.

Relevant Pages

  • Re: Static vs. Dynamic typing (big advantage or not)---WAS: c.programming: OOP and memory management
    ... i believe it was, in fact, *you* who was running to extremes, when you said ... Saying sometimes is to invalidate the notion that static typing is ... > to understand the intent of the participants, then don't aggravate ...
    (comp.object)
  • Re: Static vs. Dynamic typing (big advantage or not)---WAS: c.programming: OOP and memory management
    ... i believe it was, in fact, *you* who was running to extremes, when you said ... Saying sometimes is to invalidate the notion that static typing is ... > to understand the intent of the participants, then don't aggravate ...
    (comp.programming)
  • Re: Obstacles for Tcl/Tk commercial application development ?
    ... I'm simply saying it's far less useful than one might think from the way you describe it. ... some things falling outside the coverage of static typing. ... Once you get to the point where you have different types for "string the user typed", "string I pulled out of a database column", "string with proper escaping for SQL injection attack prevention", and "string properly escaped for delivery over HTTP", I can see where it would catch a lot more errors. ... Is this a custom language of your own, ...
    (comp.lang.tcl)
  • Re: Why I dont believe in static typing
    ... >So static typing by no means mandates writing down all your types. ... to give you helpful error messages if it has more information about ... I'm not saying that such bugs wouldn't be just as easily ...
    (comp.lang.lisp)
  • Re: Why I dont believe in static typing
    ... In article, Garry Hodgson ... I am saying that I don't believe in static typing because I have met ... >> believe) of using static typing systems. ... There's actually empirical evidence that anti-lock brakes don't reduce the ...
    (comp.lang.lisp)