[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Containers



TT: As promissed long I go I know have put my collected afforts for
TT: building a datatypes and algorithms collection on the
VisualOberon
TT: download page (http://www.ping.de/sites/edge/download.html).

Considering that the idea of Oberon is that of an extensible system,
it is a bit sad that very few people actually share their library
code
with others.  On the other hand, maybe too many people are writing
code that is unsuitable for reuse.

Anyway, thank you, Tim!

TT: So, now its your turn. The oberon community is badly in need for
such
TT: library - in my opinion.

True enough.

PF:    I agree! I would suggest that most of us take a look and we
try to come
PF: up with some of the *truly* necessary abstractions next. 

We had already had a discussion about linked lists.  The prose on the
mailing list was a very good starting point, but needs to be
formalized into a module interface for further discussion.  

PF: Those can then be implemented by different people [...].

This is possible, if an elaborate framework exists and has been
agreed
upon.  For example, the OOC IO libs have been built this way. 
Without
a good framework (and good documentation), things won't work out.

Also remember my "godfather" posting.  It was not intended as a joke.
In my experience, without a "godfather" nothing will happen beyond
calls to "let's do this or that".

PF: PS: OOC and VisualOberon are still not in the Oberon Webring?
Why's
PF: that? :-)

Go pester Juergen about the OOC page.  He might do something about it
:-)

-- mva