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
every Perl script that says:
"Don't be stupid."
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
API design (Score:1)
Sounds like bad API design to me.
permaLinkshould always be the permalink, if there is one, andguidshould 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 where it’s at, nowadays. Though I guess we need solid code for consuming the RSS that’s sadly already around.)
Reply to This
Re: (Score:2)
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
Re: (Score:1)
Atom [rfc.net]’s just RSS without the bugs [diveintomark.org].
Re: (Score:2)
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();