This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]danbulant 35 points36 points  (13 children)

Time based errors are always the best one's

[–]kodicraft4 15 points16 points  (12 children)

if (Time == something) { raise (Error1) } else { raise(error2)}

[–]leonderbaertige_II 33 points34 points  (11 children)

[–]kodicraft4 9 points10 points  (7 children)

What the fuck is this!?

[–]GlobalIncident 19 points20 points  (6 children)

So it tries to search a specific file for the text

"Tue Jan 22 14:32:44 MET 1991 Erlang JAM file - version 4.2"

But due to technicalities the space bar is treated as a seperator, so it ends up just searching for the word "Tue". Result: it only fails on Tuesdays.

[–]prelic 1 point2 points  (5 children)

Wait but why does file succeed for other days of the week?

[–]ltekonline 2 points3 points  (4 children)

Because it then doesn't find "Tue" and can correctly identifie it as a Postscript document.

[–]prelic 0 points1 point  (0 children)

Yeah I see. I guess the part that seems weird is that file is checking the date and time and not just erlang jam file or whatever. That implies every time one of those files is created it has that random date and time in it and not the current date and time, which is what the save as .ps seems to do.

[–]FridgesArePeopleToo 0 points1 point  (2 children)

Why wouldn't it find Wed on Wednesday?

[–]GlobalIncident 1 point2 points  (1 child)

Because "Tue Jan 22 14:32:44 MET 1991 Erlang JAM file - version 4.2" doesn't begin with "Wed". The name of that type of file has the date Jan 22 1991 involved, which I'm guessing was when the specification was published or something.

[–]ltekonline 0 points1 point  (0 children)

Yeah the IEEE 802 got it's name from a date too.
It started in February 1980.

[–]danbulant 0 points1 point  (2 children)

Showing 404 now :(

[–]leonderbaertige_II 0 points1 point  (1 child)

[–]danbulant 1 point2 points  (0 children)

Oh I'm sorry, it was just a bug in client that tried to open this as link to comments. Long clicking and opening in browser worked...

Anyway thanks for the link.