As per various comments:
I agree with Ken (hence why I suggested the namespace). Most data structures have corresponding algorithms. There is already an Algorithm namespace, but no Datastructure namespace.
Data seems to be full of random things, usually related to debugging, data persistence or presentation.
List isn't good because it impliesthat it deals with Perl lists.
I thought about putting it in the Tree space, since tecnically a skip list is a redundant tree, and people looking for tree algorithms might find skip lists useful... but unless they know what a skip list is and are already looking for it, I'd be accused of spamming the namespace. So that's not a good idea. (And most of the Tree modules probably belong in Algorithm anyway).
Rob
On 7/31/2004 11:05 AM Ken Williams wrote:
On Jul 30, 2004, at 1:35 PM, Robert Rothenberg wrote:
I have a module called List::SkipList which has been on CPAN for quite a while. I'm thinking of renaming it to Algorithm::SkipList, which seems more appropriate (and nobody said yeah or nay to my request for the List::SkipList namespace on [EMAIL PROTECTED]).
Does anyone consider that an inapropriate name?
That's exactly the right name.
I think the comments about "data structure vs. algorithm" are misplaced - a skiplist (as you know) is both a data structure and an algorithm, either without the other would be a bit silly.
-Ken
