Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

chaoticset (2105)

  (email not shown publicly)
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)

JAPH. (That's right -- I'm not Really Inexperienced any more.)

I'm not just here, I'm here [], and here [] too, I ramble randomly in my philosophical blog [] and my other blog []. Soon I'll come in a convenient six-pack.

Journal of chaoticset (2105)

Thursday July 17, 2003
07:36 AM

Quick Overview (Note To Self)

[ #13500 ]
Okay. Last night you got the refresher checking if the perljobs RSS feed was fetched within the last 30 minutes, and if not, fetch a new one. (It's likely that the program will be used infrequently enough, so this will reduce the amount of fetching to something reasonable, hopefully.)

You also wrote the MW for the Tk, but not really much else.

Right now, your main problem is that the detailed feed coming out of perljobs is giving "not well-formed" errors when XML::Simple looks at it, and similar errors when IE tries to look at it. Have to figure out what I'm doing wrong with the RSS feed. (The normal one didn't seem to have issues, but you only looked at it once or twice.)

Figure out something with this, even if it means using XML::Parser.

Work out the rest of the Tk, too. Think about using the Form manager this time. Pack's quick, but kind of unwanted. Eh, we'll see.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • If XML::Simple has trouble with it, likely so will XML::Parser.

    Two options you should look into first:

    • characters: does the data contain any invalid characters? Does the character set agree with the content-encoding? The default for XML is UTF-8.
    • Proper, matched nesting of tags.

    All in all, the error message as produced by XML::Parser, should give you a very specific pointer, line and column numbers, to where it thinks the first error occurs. I don't know if XML::Simple is as explicit.

    • XML::Simple's been dumping XML::Parser's errors at me most of the time. (I can't recall right now whether or not this error's been from Parser or Simple, but I can check it easily when I get home.)

      I was under the impression that XML::Simple really just tells XML::Parser to do the most obvious thing and hope it works, but if the well-formedness is truly in question, perhaps I should figure out what's going on. Now I've just got to learn more about RSS and fetch my XML handbook, and perhaps I can actually


      You are what you think.