Dan Sugalski:
# On and off we get hints that there's some wild pointer mashing going
# on. Well, I'm working on the collector, and I can tell you for sure
# that we're doing this somewhere. I don't supppose anyone's got some
# hints as to where we're doing wild writes they might care to share?
Just that, though I haven't seen this recently, off-by-one errors seem
to be relatively common in key.c.
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking, regex hacker, embedding coder, and boy genius
#define private public
--Spotted in a C++ program just before a #include
