That's absurd - half a century of software engineering practice
clearly shows that catching an error at runtime is hugely more costly
than catching it at compile time. Of course not all errors can be
caught at compile time, but if possible, it's *far* better to do so,
and type safety helps with that a great deal.
Ian Collins said:Some people never learn, or maybe never stop trolling?
Apparently, over the many years he has posted assembly to c.l.c., you
*never* read *any* of his assembly code. If so, you'd know his preference
for extreme terseness. I.e., that #define should not be a shock to you in
I'm not skilled, but I did read one once!; It was for the maze solvingApparently, over the many years he has posted assembly to c.l.c., you
*never* read *any* of his assembly code. If so, you'd know his
for extreme terseness. I.e., that #define should not be a shock to you
He wrote his own assembly language. It's syntax is so terse, sparse, or
compact that even skilled assembly programmers can't understand it. It's
In order to avoid unnecessary sexism or speciesism, use s/he/it,
which is, of course, pronounced "shit".
James Kuyper said:On 09/14/2012 04:50 PM, Gordon Burditt wrote:
[Unatrributed text from a message that I wrote a couple of months ago.]
I've told you this before (2011-03-30, 2011-10-18, 2012-03-12, and
2012-03-14), but apparently I need to remind you again. Permission to
quote any part of any message I post, without proper attribution, is denied.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.