>And more, i think that 'inheritance considered harmful'))
>Because breaks encapsulation and hides relations between components.
Maybe some other feature (like multiple interfaces to one implementation)
do that work better.

I'm, building a control screen for simple i/o with FST modula-2.
The screen will contain some buttons and graphs.
Now i'm workin on drawing a graph diagram with scalable axes.
Actually it is a port from Turbo Pascal Library (T. Rugg, P.Feldman) in
combination with an extended version Jan Verhoeven's lowlevel library. I
forsee that, that when I want a screen with 6 graphs, that using a
graph-class is easier then a diagram.mod.

The coursebook "In the realm of Oberon" (Nikitin) describes nicely the
transistion of emperative programming to OO. Oberon is actually a hybrid
language, it has oo and emperative elements.

FST has also a oo extension. It does not use, unlike Oberon, pointers in
datastructures with classes (like java).

Back to the graph for now.

Greetings,
F.P. Vonck













> Jan > It would be very good if one set of components was chosen
> Jan > as a standard PC and development would be based on that one set
Jan > of hardware components.
>
> Not so needed IMHO. With working generic IDE driver, generic
> VESA framebuffer graphics, three generic types of network cards
> (Realtek, Intel, 3com), generic AC97 sound... we already mostly have
such unified office i386 x86-32 platform... Let's hardware support will be
> provided by NetBSD or Linux kernel compiled for 586-mmx.
> Just use it by syscalls from small programs, builded with optimising
linker.
>
> Jan > Yes, syscalls would be ideal. But it would be necessary to write a
Jan > new small kernel in assembler for the standardised hardware. Jan > A
terrible job.
>
> I don't think we really needs this 'millions lines of code'.
> It's not really achivement, those lines. It is traces of lazyness)) If
programmers was paying for each line of code we now have much better
programs))
>
> But anyway, why do so hard work)) Assembly usage must be minimised. We
need HIGH level environment, wich helps REDESIGN old systems and
iteratively
> desing new. And separate IMP/DEF of Modula-2 greatly helps in changes
ordering, isn't it?)) THIS is source of Modula-2 magic. Like arrow stabilizer
> or