Recommendation for a CL data structures library
in [Lisp]
|
Prev: [2nd CfP] 7th European Lisp Workshop at ECOOP'10, June 21/22
Next: §§§ 2010 Cheap wholesale ED Hardy Suit, Baby Suit, Lacoste Suit ect at www.rijing-trade.com <Paypal Payment>
From: RG on 18 Mar 2010 14:40 In article <4ba2128a$0$273$14726298(a)news.sunsite.dk>, "Alex Mizrahi" <udodenko(a)users.sourceforge.net> wrote: > ??>> What do you need precisely? > > R> For now just an associative map that's O(logN) for inserts and lookups > R> on ordered keys. But I figured as long as I was looking I'd fill out my > R> collection as completely as possible in anticipation of future needs. > > I was looking for a sane library which implements binary tree-based > associative container, but wasn't able to find any :(. > There are some tree implementations, but they lack iterators and stuff like > that. > > If you're looking for a general data structures library, cl-containers [1] > is supposed to be it, but quality is lacking -- API is not consistent, > documentation is auto-generated (basically, it is a list of functions), some > things just do not work. But, I think, all code is there, it just needs some > cleanup. > > [1]: http://common-lisp.net/project/cl-containers/ Thanks, will look at that too. rg
From: Pascal J. Bourguignon on 19 Mar 2010 09:24 "Alex Mizrahi" <udodenko(a)users.sourceforge.net> writes: > ??>> What do you need precisely? > > R> For now just an associative map that's O(logN) for inserts and lookups > R> on ordered keys. But I figured as long as I was looking I'd fill out my > R> collection as completely as possible in anticipation of future needs. > > I was looking for a sane library which implements binary tree-based > associative container, but wasn't able to find any :(. > There are some tree implementations, but they lack iterators and stuff > like that. What about http://darcs2.informatimago.com/lisp/common-lisp/llrbtree.lisp (Left Leaning Red-Black Tree). It even has a with-tree-iterator macro! -- __Pascal Bourguignon__
From: Raffael Cavallaro on 19 Mar 2010 11:01 On 2010-03-19 09:24:34 -0400, Pascal J. Bourguignon said: > What about > http://darcs2.informatimago.com/lisp/common-lisp/llrbtree.lisp > (Left Leaning Red-Black Tree). > It even has a with-tree-iterator macro! Maybe you don't realize this Pascal, but even though much of your code may be quite interesting, no one who currently works on a commercial, published product, or who contemplates working on a commercial published product in the future, can take the risk of using your libraries because they are GPL licensed. Using them would place their employer or the commercial organization to which they belong under the obligation of publishing all of the source code for any released product that included your library. As a result, most people working on commercial published software, or who contemplate doing so in the future, simply avoid gpl libraries altogether. This is why so many c/c++ libraries are released under the lgpl, not the gpl. It is also why so many lisp libraries are released under the llgpl, bsd, apache, or mit style licenses. Your libraries would see much wider use if they were bsd or apache licensed, for eample. warmest regards, Ralph -- Raffael Cavallaro
From: Alex Mizrahi on 19 Mar 2010 11:13 RC> Maybe you don't realize this Pascal, but even though much of your code RC> may be quite interesting, no one who currently works on a commercial, RC> published product, or who contemplates working on a commercial RC> published product in the future, can take the risk of using your RC> libraries because they are GPL licensed. Indeed, good catch!
From: Pascal J. Bourguignon on 19 Mar 2010 12:57
Raffael Cavallaro <raffaelcavallaro(a)pas.espam.s.il.vous.plait.mac.com> writes: > On 2010-03-19 09:24:34 -0400, Pascal J. Bourguignon said: > >> What about >> http://darcs2.informatimago.com/lisp/common-lisp/llrbtree.lisp >> (Left Leaning Red-Black Tree). >> It even has a with-tree-iterator macro! > > Maybe you don't realize this Pascal, but even though much of your code > may be quite interesting, no one who currently works on a commercial, > published product, or who contemplates working on a commercial > published product in the future, can take the risk of using your > libraries because they are GPL licensed. > > Using them would place their employer or the commercial organization > to which they belong under the obligation of publishing all of the > source code for any released product that included your library. As a > result, most people working on commercial published software, or who > contemplate doing so in the future, simply avoid gpl libraries > altogether. > > This is why so many c/c++ libraries are released under the lgpl, not > the gpl. It is also why so many lisp libraries are released under the > llgpl, bsd, apache, or mit style licenses. Your libraries would see > much wider use if they were bsd or apache licensed, for eample. > > warmest regards, I know. I worked hard to write it (*), I expect a compensation. I reclaim as compensation to be able to see the source of any application using it that I might buy. Is it too high a price? Notice that the GPL is not contradictory to commercial interests, on the contrary. In fact, it would be in the best interest of any commercial endeavour to distribute the sources of their software and firmware under the GPL license, since otherwise a competitor could patent the core techniques. Or if the original company patents it itself, then it will have published it already so no evil would come from giving a copy of the source along with any product. Now, perhaps I should explicitely state in each file that commercial licenses are also available upon request, but I guess that if commercial entities were interested I would have contacted with me already. If I ever win big a lottery, or if I ever become a civil "servant", I may publish my code under BSD or MIT. But until one of these unlikely events occurs, I will stick to GPL or commercial licensing, with a very strong favor for the former. (*) But much less hard than Robert Sedgewick, let's thank HIM for the really hard work, which americans did by paying his tenure, and the other peoples of the Earth by supporting (willingly or not) the american debt. We've already paid for his ideas. -- __Pascal Bourguignon__ |