Re: Digest for EUforum at topica.com, issue 5000
> Subject: Re: Standard Euphoria Library project (was: Re: Garbage collection
> (real featur posted by: Jason Gade <jaygade at yahoo.com> Juergen Luethje wrote:
>
>>>
>>> Christian Cuvier wrote:
>>>
>>> <snip>
>>>
>>
>>>> > The Standard Euphoria Library project on Sourceforge is dead.
>>>> > The OpenEuphoria group, which is the one you're referring to, is dead as
>>>> > well.
>>>> > Its homepage is at oedoc.free.fr actually.
>>>> >
>>>
>>>>> >> Now I wouldn't want to organize such a thing because I am not an
>>>>> >> experienced
>>>>> >> developer. But I would want to contribute ideas, documentation, or
>>>>> >> code.
>>>
>>>> >
>>>> > I was originally the doc manager for OpnEU. I wound up docig sequences
>>>> > in C++ when the group imploded. Now I'm admin of a souceforge defunct
>>>> > project. Wanna get in?
>>
>>>
>>> I'd like to join the Standard Euphoria Library project. 
>>>
>>> Regards,
>>> Juergen
>>>
>>>
> I'll look at the OpenEU docs for ideas. I think many features requested in
> the language could be implemented in a new standard library.
>
> What needs to be done is look at what kinds of things users need, what kind of
> facilities exist in other languages (either in their library or as a standard
> part of the language) and figure out how the library should be structured.
>
There are two problems with libraries as Eu uses them:
1/they are external files, which may take time to load and parse,
especially under 2.5
2/most important, they cannot take advantage of the inner working of the
core language, which leads to sometimes considerable efficiency loss
(see for instance the ins/del sequence elements routines.
It may be argued that:
1/ If truly modular code is available, only small libraries will be
needed at a given time, so that 1/ above may be made moot (split
win32lib !!)
2/ if there's a tool to precompile files into some sort of VM code, the
latter allowing really low level operations, 2/ above may be made moot.
> Find which parts of the library are already written and in the archive, and
> include them as needed. (strtok, win32lib or wxeuphoria, etc.)
>
> I think one of the "gotchas" in doing it would be interdependencies between
> functional areas of the library.
>
> One idea is to reference Win32lib in order to see how a good library is
> written and structured.
What do you mean here?
>
> I'm willing but my experience is low. I can't guarantee that I won't lose
> interest but I would like to try. I think it will require much research and
> planning before any lines of code are written.
>
> =====================================
> Too many freaks, not enough circuses.
>
> j.
CChris
|
Not Categorized, Please Help
|
|
