serious parsing bugs above

1,095 registered users | 1 active user | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #4,054 by Fearless Freep 8/7/01 12:23:42 PM Reply	serious parsing bugs above a) I initially used a "code" tag but was warned I had unmatched tags (which I didn't) b) "pre" tag should not have forced "br" tags for line breaks c) "long" was embedded within the line with a pre tag so I don't know why it got it's own line Jay O'Connor "Going places unmapped to do things unplanned to people unsuspecting"
Post #4,057 by Yendor 8/7/01 12:59:38 PM Reply	Well... c) "long" was embedded within the line with a pre tag so I don't know why it got it's own line The pre tag is a block-level element, so when you start/stop it, it gets its own block, which means that it gets its own line inside most browsers, basically... -YendorMike In order to understand recursion, one must understand recursion.
Post #4,058 by Fearless Freep 8/7/01 1:04:44 PM Reply	Fair enough.. ...I forgot about that.... Jay O'Connor "Going places unmapped to do things unplanned to people unsuspecting"

Ugh. One more reason not to use Windows. - (admin) - (5) - Aug. 7, 2001, 10:54:40 AM EDT

Overflow error.... - (Fearless Freep) - (4) - Aug. 7, 2001, 12:21:42 PM EDT

serious parsing bugs above - (Fearless Freep) - (2) - Aug. 7, 2001, 12:23:42 PM EDT

Well... - (Yendor) - (1) - Aug. 7, 2001, 12:59:38 PM EDT

Fair enough.. - (Fearless Freep) - Aug. 7, 2001, 01:04:44 PM EDT

Doesn't work, even if you use an unsigned long long -NT - (jb4) - Aug. 7, 2001, 02:02:49 PM EDT

That's very funny, a fly marrying a bumblebee!
100 ms