> >>Just don't post your code to the list itself. It's rude to
> >>bloat the mails on the list. Provide a hyperlink to your annotated code.
>
> True, but what happens after you get your answer? You take the code down and
> move on. It would be nice to have a place to post the code where it can be
> organized and filed away with comments for future reference.
As I've replied earlier in a personal emil to Dave, the idea might be
nice. So you might want to go ahead and give it a try -- if it works out,
cool, if not at least you know that you have tried.
Personally I've found that it's much easier to find a few coders that you
believe that their style is good and learn from their code. In my early
days I've learned a great deal of idiomatic Perl coding from Randal's
columns:
http://www.stonehenge.com/merlyn/WebTechniques/
http://www.stonehenge.com/merlyn/UnixReview/
"Effective Perl Programming" by Joseph N. Hall
(http://www.effectiveperl.com) was the second source I've learned the most
from.
But you are probably talking about mod_perl specific idioms, and that's
why I think it might be a good idea, *if* people will actually find it
interesting/challenging enough to review each others code techniques. So
as I said go for it and you will find out.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://logilune.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
