[Oberon] Import hierarchies of display modules.

[Jan de Kruyf]

we will have to speak to google I guess

j.

On Wed, Oct 7, 2015 at 11:31 AM, Alexander Ilin <ajsoft at yandex.ru> wrote:

> Hello!
>
>   A few small corrections below.
>
> 07.10.2015, 08:38, "Jan de Kruyf" <jan.de.kruyf at gmail.com>:
> > Here is the english legend to Alexanders' diagram:
> >
> > Legend:
> >
> > Red text = module imports SYSTEM;
> > rectangular frame = module imports something from either subsystem Win,
> or a set of «KERNEL32, GDI32, USER32, SHELL32, COMDLG32, ADVAPI32, COM»;
> > no frame = module source code is not found;
> > oval frame = all the others, ie platform-independent modules (using the
> BlackBox framework only without low-level tricks);
> > simple arrow = IMPORT;
> > dotted arrow = imports through Dialog.Call (only if the call is made
> during the importing module's initialization).
>
> ---=====---
> Александр
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20151007/02b744b2/attachment.html>