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.
  • In XML::RSS "permaLink" holds the guid URL if isPermaLink is true, and "guid" holds it if it is false.

    Sounds like bad API design to me. permaLink should always be the permalink, if there is one, and guid should always be the GUID, if there is one. How this is specified in the wire format is something the API should not expose.

    I don’t know if you’re at liberty to make such changes, though.

    (In fact, I boggle at the effort you’re putting into a module for RSS… Atom’s

    • Sounds like bad API design to me. permaLink should always be the permalink, if there is one, and guid should always be the GUID, if there is one. How this is specified in the wire format is something the API should not expose.

      It is bad API design in my opinion. But this was the API since XML::RSS 1.05 [cpan.org]. BTW, in RSS 2.0 what happens is that the guid element has an isPermaLink attribute which can be "true" or "false". If it is true, then permaLink will hold the contents of the "guid" tag, and if it's fals

    • > Sounds like bad API design to me. [....]

      Indeed. XML::RSS is mostly a big messy patchwork.

      > I don’t know if you’re at liberty to make such changes, though.

      The current focus is to slowly get the test coverage up and bugs fixed; when we have good coverage we can refactor the code and the API (while staying compatible with the old one). As you point out, there really isn't much need for innovations in an RSS module.

      I got sucked into looking after the module after finding a bug (like Shlomi
      --

      -- ask bjoern hansen [askbjoernhansen.com], !try; do();