I want to replace Array.dwim_sort_func with the C function at http://www.sourcefrog.net/projects/natsort/ ; it's much faster than the current Pike implementation, but is under the zlib license. I believe it's compatible with GPL/LGPL/MPL, but would like to be sure before I submit my patch. www.gnu.org explicitly says zlib is compatible with the GPL.
It looks compatible with MPL as well. You need to make a diff against Tools.Legal.Copyright as well.
/ Martin Nilsson (räfsfiskal)
Previous text:
2004-05-10 06:32: Subject: License question for contributed source
I want to replace Array.dwim_sort_func with the C function at http://www.sourcefrog.net/projects/natsort/ ; it's much faster than the current Pike implementation, but is under the zlib license. I believe it's compatible with GPL/LGPL/MPL, but would like to be sure before I submit my patch. www.gnu.org explicitly says zlib is compatible with the GPL.
-- Dan Nelson dnelson@allantgroup.com
/ Brevbäraren
Is the advantages worth it, compared to rewriting the dwim compare function in C?
/ Per Hedbor ()
Previous text:
2004-05-10 06:32: Subject: License question for contributed source
I want to replace Array.dwim_sort_func with the C function at http://www.sourcefrog.net/projects/natsort/ ; it's much faster than the current Pike implementation, but is under the zlib license. I believe it's compatible with GPL/LGPL/MPL, but would like to be sure before I submit my patch. www.gnu.org explicitly says zlib is compatible with the GPL.
-- Dan Nelson dnelson@allantgroup.com
/ Brevbäraren
The sole advantage, as far as I can see, is that somebody already did. Except for the pike glue, which has to be put in place, either way.
/ Johan Sundström (Achtung Liebe!)
Previous text:
2004-05-10 12:17: Subject: License question for contributed source
Is the advantages worth it, compared to rewriting the dwim compare function in C?
/ Per Hedbor ()
And widestring adaption, I presume?
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-10 14:59: Subject: License question for contributed source
The sole advantage, as far as I can see, is that somebody already did. Except for the pike glue, which has to be put in place, either way.
/ Johan Sundström (Achtung Liebe!)
Practically nothing. There's a function to index a pike_string, but you don't want to use that in tight loops since it's much more efficient to check the width first and then choose a loop compiled with the right char width. That's why there are so many large macros involved whereever any significant string fiddling is done internally in pike.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-12 11:38: Subject: License question for contributed source
Likely. I'm not too well versed in how much of that is handled by the includes.
/ Johan Sundström (Achtung Liebe!)
pike-devel@lists.lysator.liu.se
-
Dan Nelson -
Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum -
Martin Nilsson (r�fsfiskal) ＠ Pike (-) developers forum
-
Martin Stjernholm, Roxen IS ＠ Pike developers forum
-
Per Hedbor () ＠ Pike (-) developers forum