🚀 go-pugleaf

In article <3938@enea.se> sommar@enea.se (Erland Sommarskog) writes:

>do in different situations. If the program runs too slow you can always
>buy a faster machine. But if you don't get the code on time, what do you
>do? Buy a faster programmer?

	Hell yes.
	How many teamsters does it take to screw in a light bulb?
	15!! YOU GOT A PROBLEM WITH THAT?

	Nuclear power plant construction suffers cost and schedule
overruns,  I guess we should conduct more reasearch on fast setting
epoxies.

>     Apple : Apple_type;
>     Pear  : Pear_type;
>In many old-fashioned languages I can't do this. (Fortran, Cobol, C?).

	Can you read, write, speak the english language?
	Good thing nobody uses dinosaurs like C anymore!  Just think
what could have happened... compilers, editors, operating systems, and
embedded systems may have been horrendously implemented.

>Other languages let me do this, but when I by mistake write:
>    Apple := Pear;   or
>    Eat_an_apple(Pear); -- Parameter is of Apple_type.
>the compiler will not always warn me. (Pascal, Modula-2?, Oberon?)

	C'mon. Everyone knows that nikky's tighter than a TIG weld when it
comes to type checking, not that I'm against it. Well, almost

>  Some languages that enforce this string type checking are Ada, 
>Eiffel, Simula and C++(?). Hardly just a coincidence that all of 
>them but Ada are object-oriented.

	Oh, so you can read, write, speak the english language.

>  You may wonder why this is important. Let me just answer with a
>common, but good, clich'e: Get the errors out early.

	What a concept. Are you planning to publish?
	By the way, what happened to that oxy-acetalene C flame you
had goin' for a while in your .sig?  And why did you stop posting?