Lack of update can be explained many ways -- hens have produced eggs in the same form for a bit more than the decade since Dr. Perin published CodeRead...and Perin himself has had other fish to fry (take a gander at his CV: the notion of 'publish or perish' comes to mind). However, the 1998-2001 CodeRead discussion on his UNC pages identifies some shortcomings ("
not working very well" to throw out a PM
bete noir) which suggest that if he was using it last year, he's also likely to have improved it.
his CV, http://perrin.socsci.unc.edu/cv.pdf strongly suggests that CodeRead was originally developed while he was a candidate for his PhD. His "computer tips" page suggests that he produced some interesting Perl s/w within the past few years... and provides an email address.
The academic world being what it is, an inquiry directed to him might be fruitful.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.