[Oberon] Re (2): Re (2): syntax in BB, CP, GPCP and V4 compared to Oberon-2.
joerg.straube at iaeth.ch
Fri Jul 21 22:56:43 CEST 2017
The convention for file names "prefix.module.Mod" is normally used if you have different versions of the same module. Eg
Windows.Display.Mod and Linux.Display.Mod could be different source versions of the same module Display, once written to map Display to Windows APIs once written to map Display routines to Linux APIs.
The reason why I called the module V4Sort is simple: Linz Oberon (aka V4) has already a module called Sort and I didn't want the complier to overwrite the object file.
> Am 21.07.2017 um 17:31 schrieb <peter at easthope.ca> <peter at easthope.ca>:
> I've never used V4 or a derivative and need to be more clear about
> From: Douglas G Danforth <danforth at greenwoodfarm.com>
> Date: Thu, 20 Jul 2017 18:08:06 -0700
>> The BlacBox naming convention only uses one "."
>> The module would need to be named "Sort" and placed
>> in the directory "Oberon/Mod".
> Appears V4 recognizes directories.
>> References to any procedure P within Sort would be "OberonSort.P"
> If the module is Sort, shouldn't the invocation be Sort.P ?
> Why OberonSort.P?
> From: SvZyZw== <joerg.straube at iaeth.ch>
> Date: Fri, 21 Jul 2017 11:35:49 +0200
>> Attached the V4 version.
> Wow. Thanks!
>> MODULE V4Sort;
> You suggest all the V4 module names in the wikibook begin with
> "V4"? Rather than use the context naming?
> MODULE Sort (* IN V4 *);
> Reasonable possibility, although a single universal naming scheme
> has appeal.
> Seems the file name could also be V4Sort.Mod rather than V4.Sort.Mod.
> Thanks again, ... Lyall E.
> 123456789 123456789 123456789 123456789 123456789 123456789 123456789
> Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757
> http://easthope.ca/Peter.html Bcc: peter at easthope. ca
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon