I guess I am not so talented - no matter how well I design
my code ( and I do try ) there is always a point where I say
"Hmm. I didn't think of that" or "The specs have changed
and the code now has to do this" or "Boy, I was really
hitting the crack pipe hard when I wrote that", etc.
I have written a few toys that are not perfect, but they
basically grub through one piece of source code and pull
all the subs out. It then grubs through a whole lot of
other code and finds calls to those routines. It attempts
to determine context then attempts to print out the
full call ( my function calls frequently span lines ) and
a line number. As I said, isn't yet perfect but it works
pretty well. I have posted it in the catacombs.
It is not well polished - it was never intended to be used
by another person.
mikfire
Update: I modified this post slightly to add the URL | [reply] |
I guess I am not so talented - no matter how well I design my code ( and I do try ) there is always a point where I say "Hmm. I didn't think of that" or "The specs
have changed and the code now has to do this" or "Boy, I was really hitting the crack pipe hard when I wrote that", etc.
Thank you for the link to the code. Rapid prototyping is a very good development model for our
business and Perl is the most flexible language out there. Our code
has reached a point of reusability that i hadn't seen in Perl before and
now i am looking to grow our toolset that we use to control it.
The API is very well thought out and designed, however we still need to
depreciate the use of a function from time to time (much like perl itself =)
-pos
The truth is more important than the facts.
-Frank Lloyd Wright
| [reply] |