Re: Standard Euphoria Library project
Juergen Luethje wrote:
>
> Gordon Webster wrote:
>
> <snip>
>
> > I would propose the following compromise ...
> >
> > Focus initially on a small group of ibrary modules that are most urgently
> > needed and concentrate effort on making each of these consistent within
> > itself. If you can make each library module consistent with the other
> > modules as far as pssible, all the better, but if not, live with it and
> > document the inconsistencies between modules as "to-do's" for the
> > subsequent releases.
> >
> > I would focus on core language needs first, since higher level things will
> > be built upon them and if they are robust and mature, the higher level
> > stuff will be as well.
> >
> > One obvious example would be a Euphoria "Collections" module to extend
> > the functionality of sequences in some much needed areas. Mirroring
> > the excellent Java "Collections" class, this module could implement
> > associative arrays (HashTables), sets, indexed arrays etc. etc. This
> > alone would would be an invaluable start to the library.
> >
> > Other things ... keep RDS in the loop so that unnecessary effort is not
> > wasted creating features that the next version of Euphoria will implement,
> > and also for feedback (nobody knows more than they do about the behavior
> > of the language). Solicit help, make allies. Release fast, release often.
>
> I agree. 
>
> Regards,
> Juergen
>
>
For the most part my quick and unscientific survey finds that a lot of "standard
library" functionality exists in the archive. I think that it is just a question
of pulling it all together and then finding out and adding whatever is still
missing.
=====================================
Too many freaks, not enough circuses.
j.
|
Not Categorized, Please Help
|
|
