Re: [ooc-compiler] Re: libadt issues (was: Re: Possible improvements)

[Michael v. A. <mi...@de...>]

"Marco Oetken" <Mar...@In...> writes:

> I am using libadt in some programs. The doublelinked lists and the strings.
> I guess both are very useful an could be used in VisualOberon and elsewhere.
> I have extended String and built a module, which implements Filenames
> (not portable though -- just for unix-like naming conventions).
> Michael states "being used" is very important. I regularly avoid using
> String because they are not supported in the standard library modules
> of OOC. It would be nice to have String supported by Readers e.g.

I want the core library and libadt to stay separate entities.  That
is, libadt may obviously use core, but not the other way round.

> ListDL and String seem to be most useful libadt modules and I suggest
> to include them into OOC. I could provide my filenamesmodule, too.
> Those 2 (3) modules will be used!

Regarding ListDL I would like to know if there are any votes for the
iterator stuff (Apply, Map, Select) to stay.  Or should it be dropped?
Likewise, should the `Rider' be dropped?

For `String' I would suggest to drop `String.Apply' and the Rider.

Someone needs to write the embedded Texinfo documentation before I add
the modules to the CVS repository ;-)

-- mva