cltl3-devel

cltl3-devel@common-lisp.net

23 discussions

[cltl3-devel] requirements on CL libraries
by Peter Denno 15 May '09

15 May '09

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

4 4

[cltl3-devel] getting mindshare
by Nikodemus Siivola 15 May '09

15 May '09

How does CLtL3 intend to get the mindshare it needs to succeed? I have a couple of ideas, but I'm asking because I assume this may have been discussed at ILC or elsewhere. My take: * Don't try to sell or do too much in a single go. Don't try to eg. build a massive system of classification for libraries before you have the libraries to classify. Don't try to sell MASSIVE ideas when you can get most of the way there with a few smaller ones. Decouple ideas initially. Let them aggregate only once they have acceptance and are implemented. * Remember to ask for what people *don't* want in addition to what they do want. This is not to say that controversial things cannot be done, but perhaps initial velocity (and trust in the projects ability to do its thing!) is best gained by focusing on the consensus. * Even if CL is a mudball of strength, I think what CLtL3 seems to aim at needs a razor sharp focus. Someone(tm) needs to keep the reigns tight and say "out of scope for now" to everything not in focus a the moment. Until a certain momentum is there focus is everything, I think. Cheers, and good luck! -- Nikodemus

2 1

[cltl3-devel] Initial message
by Stelian Ionescu 24 Apr '09

24 Apr '09

Test -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

cltl3-devel