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.
  • by dws (341) on 2003.03.20 1:20 (#18107) Homepage Journal
    To understand Rafe's point, it helps to read the blosxom [raelity.org] source. To my eye, in places blosxom goes a step over the line past being idiomatic Perl into being "look at home much stuff I can compress into one statement" Perl. That said, I'm still probably going to use it to replace some home-grown stuff, since blosxom provides a plugin-mechanism that'll allow me to retain the interesting aspects of my old system.
    • I agree; bloxsom is quite obscure in places. However, it doesn't have to be. A few well named functions would make all the difference to it.

      I also feel that the sample java code is even more obscure than the perl code. But maybe I've been hacking Perl too long. Neither extract is that good though. A correct implentation would have a nice function called count_slashes().

      I seem to recall schwern using the phrase "sufficiently encapsulated magic". Here, I'd agree with him. By all means have nasty co

      • I seem to recall schwern using the phrase "sufficiently encapsulated magic". Here, I'd agree with him. By all means have nasty code. Just hide it away in a function with a nice name.

        Piers Cawley did a nice lightning talk on "just" at a london.pm techmeet recently. The thrust was the same - you can hide as much technical complexity as you wish, if you are able to provide a nice, simple API