Re:A basic forking server in Oberon-2
by vidarh on Thursday May 05, 2016 @10:56AM
(#11636630)
> It would probably be nicer to have two compilation artifacts, the extracted human-readable interface part and the object-file implementation part.
Oberon implementations traditionally generates symbol files, that while I believe they are usually binary tends to have tools to generate textual representations, and there are plenty of tools to generate versions of the modules with implementations stripped as well. To compile a module you should need only the symbol files of the modules you import, not the compiled modules themselves.
Oberon implementations traditionally generates symbol files, that while I believe they are usually binary tends to have tools to generate textual representations, and there are plenty of tools to generate versions of the modules with implementations stripped as well. To compile a module you should need only the symbol files of the modules you import, not the compiled modules themselves.