News for hackers. Stuff that matters.
Re:A basic forking server in Oberon-2 by coldtea on Wednesday May 04, 2016 @03:45PM (#11631144)
>Proper modules, separate files for interface and implementation parts.

Proper modules are great, but I wouldn't call the "separate files for interface and implementation parts" a good feature. That's a throwback to languages like C.

It's not DRY, and it's also busywork -- the interface can trivially be created/inferred from the implementation file alone.

Re:A basic forking server in Oberon-2 by MaysonL on Wednesday May 04, 2016 @05:14PM (#11631885)
Oberon does'nt have separately written interface and implementation files, although Modula did. In Oberon, an interface file was derived from the implementation file (or from the object file), not written by the programmer.
Re:A basic forking server in Oberon-2 by nine_k on Wednesday May 04, 2016 @04:19PM (#11631412)
It was easy to give your customers the proper interface files (they were compilable), so they could code against your interfaces. They are much lighter than the object files (it was the time of the floppy disk and 2400 modems).

One point of having interface files separate is tools like `make`. If the interface file's timestamp did not change, the interface is the same.

It would probably be nicer to have two compilation artifacts, the extracted human-readable interface part and the object-file implementation part.

It (in my case TopSpeed Modula-2) was waaaay faster than e.g. Borland C++ wading through endless .h files.

Re:A basic forking server in Oberon-2 by coldtea on Wednesday May 04, 2016 @05:05PM (#11631798)
>It was easy to give your customers the proper interface files (they were compilable), so they could code against your interfaces. They are much lighter than the object files (it was the time of the floppy disk and 2400 modems).

And how would they test/run their code, since the interfaces would at best link, but not run anything, being only stubs?

>It would probably be nicer to have two compilation artifacts, the extracted human-readable interface part and the object-file implementation part.

Yes, if interface-only coding was possible for the clients, and disk space was at a premium yes. Anything but having to manually write interface AND implementation.

Re:A basic forking server in Oberon-2 by hderms on Wednesday May 04, 2016 @07:27PM (#11632799)
You could generate a stubbed implementation from the header file, I guess.
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.

Re:A basic forking server in Oberon-2 by vidarh on Wednesday May 04, 2016 @08:41PM (#11633139)
It's also a "feature" that Oberon removed.