🚀 go-pugleaf

In article <14833@amdcad.UUCP> phil@amdcad.UUCP (Phil Ngai) writes:
>In a Unix system I am designing, I am considering catering to bad
>code. That is, like the VAX I propose to make location 0 contain a
>readable 0. I think that code which gets ported to a Sun machine often
>has to have this kind of thing cleaned up. 
>
>What do people think of this? Is it kind of disgusting?

On the VAX-11 under VMS, the bottom 512 bytes of the program virtual
address space is mapped out, and trying to access it crashes your
code.

When I ported systems code to the Vax, this was the SINGLE MOST USEFUL
THING ON THE MACHINE.  I simply could not believe how many old and
trusted programs were in fact wrong, and finally broke.  All those
places where the code looked at p->next before checking for p==NULL.

Tricky code is one thing.  But, in my opinion, for truly "bad" code,
ie code that explicitly violates the semantics of the language
standard, the best remedy is to crash it disgustingly as hard and as
soon as possible.  Then it gets fixed.

>Just how much code has this problem? Did every program you ported to a
>Sun have to be fixed, or 10%, or something in between? 

Too much (again in my opinion), and partly because too many implementors
are "kind" to bad code.

> Phil Ngai +1 408 982 7840
> UUCP: {ucbvax,decwrl,hplabs,allegra}!amdcad!phil
> ARPA: amdcad!phil@decwrl.dec.com

But please remember that this is just the eccentric and intolerant 
opinion of

Robert Firth