in reply to Is code related to reverse engineering appropriate?

Perhaps a Meditation on how (and why) you did it, and a CPAN module with your code might be in order. Just be careful with Intellectual Property and Copyright issues (consider the problems that Samba had in the early days of the project). Bear in mind, you are setting yourself to be called "Guru of XXXX"....

----
I Go Back to Sleep, Now.

OGB

  • Comment on Re: Is code related to reverse engineering appropriate?

Replies are listed 'Best First'.
Re^2: Is code related to reverse engineering appropriate?
by lilphil (Scribe) on Jul 14, 2009 at 22:49 UTC
    Thanks to both of you.

    After some thought, I have posted in meditations. It is certainly not enough code to make a module out of, and I'm defiantly no guru!
    See Automatic Sage Line 50 stock adjustments

    Hopefully it will help someone who is having the same ideas I have been having.
      Not enough code to make a module out of? Whatever gave you that idea? If it does something useful, then it doesn't matter how big it is!
      It just so happens that I was looking at the source of Image::Resize on CPAN yesterday. Very useful module. If I were to remove the pod from it, the remaining code would be about the same size as what you posted in your meditation.

      Assuming your code works (I've never even heard of Automatic Sage Line 50 before, so I have no idea how to test it), it is definitely worthy of getting a proper API, a little documentation, and some tests, then going up on CPAN.

        Thanks for the encouragement! I guess I'd be a little happier about it if I was more certain about the header. Its kind of still in a "works for me" state, and Sage Line 50 version 11 is somewhat out of date.

        I wonder if anyone has a later version of Sage to test against?
        I'll give it some better testing when the stocktake comes around at the end of this month - hopefully it will all go smoothly.