[cltl3-devel] requirements on CL libraries

[Marco Antoniotti]

Hi

I don't want to sound negative...  but this effort *must* be really 
taken lightly and ecumenically.  If you can access the CLRFI/CLURFI 
logs, you will see that it is very easy to get into very heated fights.  
I know as I was one of the major offenders.

Yet I think I had some decent ideas about how to go ahead and "organize" 
extensions and categorize them.  I will dig the proposal out as soon as 
I get to my other computer.

Cheers
--
Marco



Peter Denno wrote:
> Hi,
>
> I support the idea of developing a "standard" common lisp library. 
> Doing so will provide common lisp with some of the capabilities that 
> today's programmers expect. Here are some thoughts on the requirements 
> that such an effort might address:
>
> - A common style of presentation should be used across the parts of 
> the library. This will reduce the effort required of the programmer to 
> understand the purpose of the library, and how its capabilities may be 
> interfaced to his program.
>
> - There needs to be a common and simple means for programs to 
> reference the library. Just to illustrate (not to suggest a solution) 
> URLs might be used to reference parts of the library.
>
> - There should be consistency as to how the parts load into the lisp 
> program. There should be a lightweight interface for querying a 
> program to determine what parts and versions thereof it contains.
>
> - There needs to be an orderly "lifecycle process" to track and 
> express the maturity of parts of the library.
>
> - We should address the most important parts first. It is likely that 
> there would be some debate as to what those parts are. My list 
> includes regular expressions, XML handling, http and web page 
> production, Relation DB interfacing. Note that there already is good 
> code in all of these areas!
>
> IMO, doing anything like this will require someone with the requisite 
> abilities assume a "Project Editor" role -- responsible for 
> development of most of the work products (specification of the 
> interfaces to the parts, a guide to using the library, etc.). It would 
> also require that some of the lisp community's  top talent contribute 
> with recommendations, text, and critique of the work products.
> -- 
>
> Best regards,
>   - Peter Denno
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> cltl3-devel mailing list
> cltl3-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cltl3-devel
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: antoniotti_marco.vcf
Type: text/x-vcard
Size: 366 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/cltl3-devel/attachments/20090515/ec86af10/attachment.vcf>