Re: When is it better to NOT release a new module?

Actually I was pondering about the same thing...

I've written a BBCode parser, which is quite fast:

               Rate     BBCode::Parser  HTML::BBCode     Method One   
+  Method Two
BBCode::Parser 2.54/s             --          -92%           -98%     
+      -99%
HTML::BBCode   33.0/s          1200%            --           -80%     
+      -82%
Method One      161/s          6252%          389%             --     
+      -11%
Method Two      182/s          7060%          451%            13%     
+        --
[download]

Method One and Method Two is the same module, but the second is optimized.

Would it be worth to publish it? I'm afraid the code is not well documented at all though.

Is code runtime speed important in the case of a BBCode parser, anyway?

Comment on Re: When is it better to NOT release a new module? Download Code

Replies are listed 'Best First'.
Re^2: When is it better to NOT release a new module? by Aristotle (Chancellor) on Nov 02, 2005 at 20:48 UTC
What about working your routine into one of the published modules (or both) and sending the author(s) a patch? He might also decide he's lost interest in maintaining the module in the meantime and hand you the reigns. Makeshifts last the longest.	[reply]