Re: Is this ground dead? Also, info on Mach that's more recent

[dewar@merv.cs.nyu.edu (Robert Dewar)]

Peter says

<<Checking at compile time is to put a bucket under the hole
instead of fixing the leak!

Typechecking done by the compiler is (IMHO) the wrong place.
It should be done at link time (or load time) .

Typechecking at compile time will among other things create
awful code at those times where typechecking is not wanted.
(like printf() ) and does not really prevent one from
screwing up arguments under all circumstances.
>>

Peter must I guess be a C programmer with very little imagination as
to what can and cannot be done by type checking. It is of course
perfectly possible to do thorough type checking at compile time (there
are many languages which show this, e.g. Algol-68 if you want to look
at structural typing, or Ada if you want to look at a more elaborate
typing scheme.

Of course type checking at compile time does not generate awful code?
What on earth are you talking about? The whole point of type checking
at compile time is that it generates NO CODE AT ALL!

As for printf, it is perfectly possible to design a formatted print
interface that is type safe, and no less efficient than printf, indeed
one generally would expect a formatted print facility to generate much
BETTER code than printf, precisely because printf has to do runtime
type checking by its very nature.

Peter, you have got things amazingly upside down here. It is almost
incredible that you can have things so precisely wrong! You really
should broaden your horizons and learn a little bit more about other
programming languages!