I downloaded Slash 2.2.6 and took a quick gander at Slash.pm.

I quit reading when I got to this:

# this is the worst damned warning ever, so SHUT UP ALREADY!
$SIG{__WARN__} = sub { warn @_ unless $_[0] =~ /Use of uninitialized v
+alue/ };
[download]

Talk to pudge about that one. He's of the opinion that manually initializing all of your potentially interpolatable variables to the empty string is a hassle. I see his point; most of the warnings we see in embedded code in Everything are that exact message.

If you really want to complain about something, read the metamoderation code.

I agree in certain instances as well and when those come up I feel free to do so. Though if I may ask, why don't they use the no warnings pragma for uninitilazed? Older perl?

-Lee

"To be civilized is to deny one's nature."

Slash 2 may be cleaner than Slash 1 design-wise but it still does math worse than I do. Have you ever actually counted the number of comments that get displayed when you change from threshold to threshold on Slashdot? It rarely, if ever, matches the number displayed in the select box. I've also had instances of highly moderated replies being incorrectly reparented.

--
Grant me the wisdom to shut my mouth when I don't know what I'm talking about.

And you've filed a bug report and sent in a patch right?

-- vek --

I don't use slashcode on my sites (mostly because it would be massive overkill). I've never looked at the code. I can't produce a test case. I'm not in a position to be submitting a patch for this without becoming intimately familiar with a system I don't use so why would I? I'm sure someone with some slash experience has noticed it.

--
Grant me the wisdom to shut my mouth when I don't know what I'm talking about.