>>>>> "Sam" == Sam Steingold <sds@...> writes:
>>>>> In message <Pine.SOL.4.21.0003242013060.26542-100000@...>
>>>>> On the subject of "Re: On Lisp"
>>>>> Sent on Fri Mar 24 14:14:33 EST 2000
>>>>> Honorable Stig Erik Sandoe <stig@...> writes:
>>> On Fri, 24 Mar 2000, Liam Healy wrote:
>>> > I would like to put the On Lisp code into clocc. I have a few
>>> > questions:
>>> > 1) How/where would I put the files in clocc? I am just
>>> > getting familiar with sourceforge and cvs, so any pointers (even to
>>> > a faq, webpage, etc.) would be helpful. This project will probably
>>> > be one or two files.
Sam> if you will agree to integrate your tools into cllib, you probably will
Sam> not need new files.
>>> Can this be integrated with cllib? I think cllib overlaps with the
>>> code from On Lisp. Sam?
Sam> I do use a couple of things from OnLisp and ANSICL, and I am willing to
Sam> integrate more functons, if there is demand.
Sam> onlisp.lisp is almost 2,000 lines long, so I would appreciate some
Sam> What functions are missing from cllib which you want to use?
I don't have a list handy, but there is much that is useful; why not
make it all available? In the modifications that I made, I split his
file into two, one covering Chaps. 1-18 which are utilities, the other
Chaps. 19-25, which are more complete applications (of a pedagogical
nature). To be honest, I've never loaded the second set - I only use
the first. The first set comes out to be 1643 lines (about 58k).
That doesn't seem excessive. It certainly would be possible to split
that further, however, if file size is a concern. I have put dividers
into the file by chapter, and it would be easy enough to break along
>>> > 3) What license should I use?
>>> Get a written permission from Paul Graham to release the code e.g
>>> into public domain or a specific license.
Sam> note that cllib is covered by GPL.