[Oberon] Unreferenced/unused code in Project Oberon 2013
joerg.straube at iaeth.ch
Sun Apr 28 01:35:16 CEST 2019
I would not have done some of your changes.
Just to give you some examples why it is as it is:
- FileDir: With your changes it will be difficult to write a module to repair disks, as all important fields are now hidden
- Display: By deleting the main dispatch handler Handle() it gets more difficult to code own new window managers.
By deleting Base, it’s not possible anymore to write a generic procedure to copy frame content to memory. With other resolutions, Base might change but the copy procedure could be left untouched.
-Kernel: It’s not wise to delete StackSize. If you want to improve, rather use StackSize in Modules instead of using a constant there.
-Modules: by hiding important parameters of a module, writing a debugger gets more difficult.
> Am 27.04.2019 um 22:42 schrieb Michael Schierl <schierlm at gmx.de>:
> I used some scripts to identify unreferenced code (after stumbling upon
> some unused variables in TextFrames), and was surprised how much code I
> could remove without affecting the system at all... (I also removed
> System.ExtendDisplay, as that one is of no use in Project Oberon, but
> apart from that I tried not to remove any command procedures.)
> Does anyone know if that code is there to be useful in the future, or
> did Prof. Wirth just not yet find the time to finish his software
> (which, if I recall correctly, is not finished when there is nothing
> left to add, but nothing left to take away)?
> Here is a diff:
> And here is a side-to-side view:
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon