Speicherzugriffsfehler

Sat Apr 1 00:00:00 GMT 2000

>> In Kaffe, when we got tired of people using the wrong Klasses.jar or
> classes.zip or whatever, we added a consistency check to our classes.
> We did this by adding a private static int field KAFFE_VERSION to a 
> class that's loaded early on (say java.lang.Cloneable). This not only
> allows us to detect if somebody's trying to use Sun's classes.zip, but
> also if people try to use earlier, incompatible versions.
> Maybe that's a technique that gcj could employ as well (or a variation
> thereof.) It doesn't catch all cases, but we haven't heard anybody having
> this problem since. Kaffe then prints a long error msg that's really 
> verbose and explanatory.
>
Ouch. What did I just suggest?
In gcj's case, of course I would wish that the option would be merely
a diagnostic warning that could be suppressed and not a fatal error. ;-)
	- Godmar