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.
  • Seems interesting. Can we expect code and documentation to appear on a public website? :)
    • It's not likely for a couple of reasons. First, this code was written on someone else's dime and has some customization for their needs. It belongs to them. I'd have to reimplement it from scratch. To make it a more general tool, I'd still need to change a few things about it.

      The other reason is a bit odd: many people abuse how cookies are used and making them a more flexible tool might encourage that abuse. Using a cookie this way can make it easier for a domain to set only one cookie (with the session id) rather than the multiple cookies that many domains currently set. This is a good thing. However, this also would encourage people to use cookie data as "global variables" and just shover everything in them without giving it much thought. That's similar to how many programmers -- including me -- have a bad habit of shoving everything and the kitchen sink into a hashref and then blessing that and pretending that their code is object oriented. The idea isn't a bad one but it would be very easy to abuse.

      • Maybe the problem isn't that you could stick all of your data in a hashref and bless it. Maybe the problem is that you don't pull it into saner pieces when you need it to be in saner pieces.