Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I have worked on several very large perl code-bases, I am currently working on avery large code base.

    It is being refactored and like any code that was developed up to 4 years ago it is a bit rough around the edges, but with Test suites, log4perl, SQL Phrasebooks, Autodia generated API documentation, Good use of modules, and templates to seperate code from presentation it is fairly managable

    It will be even more managable once we finish moving all the suitable SQL into the phrasebook and refactor out the dubious code in the darker corners, but a) it works and b) we have not been bogged down when developing new features ( directors don't tend to view refactoring and abstraction as a good way to spend development time, when clients and staff are requesting changes, fixes and features ).

    Eventually we might move parts of the system to TT, but there is a large investment in HTML::Template and apart from jumping thru a couple of hoops to munge data into something that H::T can use is easier than rewriting hundreds of templates and hundreds of cgi's.

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;