Out of curosity I deceided to try reimplement the Display
module of DOS386 Oberon with the aim of creating a new
version that would run at a higher resolution my SuperVGA card.
Since DOS386 Oberon does not include a Display.Mod file I
recreated the module using the definition generated from
Browser.ShowDef and by adding the appropriate export marks
and other things necessary to make it compile. Unfortunately
I could not find a way to create a new Display.Obj file without
also creating a new Display.Sym. The addition of a Display.Sym
file would of course have a new key and would invalidate all
the client modules. I double checked my work to make sure
that I had not forgotten anything but that does not seem
to be the case. I suspect the problem is that my
sequence of exported objects is slightly from the orginal
module and so the one-pass compiler generates a slightly
different symbol file ( - although the browser gives the
same definiton for my new module and the previous one ).
It is at least sufficiently different so that the
simple byte-wise comparison of old symbol against
the new symbol file fails. If this is correct, than I
suggest there should be a compiler switch which would allow
a new symbol file to be generated using the key of an
existing symbol file.
Whitney