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 November 01, 2001
08:50 AM


[ #1128 ]
Well, it's not *quite* doing what I need.

Morning coffee helps anything, right?

Anyway, I checked it out. Some of my error messages, upon consideration, aren't quite what the client's going to need. (The errors file used to say "$name is misspelled!" when a card from the inventory/stock file wouldn't match something in the Cl**ster file.) I'd found that Cl**ster has a few errors [missing commas!] and that the thing I'm using to make inventory files does too [missing LETTERS]. These are few and far between, though, so I just wanted to make sure the client was aware. That way he could go in and set his own prices. (The new message is "$name did not match to a price." I'll probably make it longer when I get around to it, but that should hold for now.)

Other than that and a few little nits here and there, it's working and worked out. On to the CGI!



Okay, from HECK, I guess, but still.

I've added the code that should handle the newest stock files (but won't, goddamnit) and I just need to start testing runs.

The Apache logfiles have some weird things occasionally. I keep getting those 'cannot find file' errors I mentioned earlier, except they're intermittant(sp?) and I don't understand them. If I did, I'd try to fix them. Since they don't seem to be breaking anything, I won't screw with it.

Testing, testing...brew more coffee...

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.