note shockme I ++'d this thread. Even though I don't make a practice of using non-meaningful names, I think it's hilarious to stumble across something like this when I'm supporting/maintaining code. The <I>only</I> reason I refrain is because my memory blows chunks. I need meaning ful names so, when I'm revisiting my code at a later date, my intentions are fairly apparent. <P> This thread does bring to mind a funny, but extremely off-topic, error message my team received from an OS core dump on an older VMS system some years ago. The error message was "Shut 'er down Clancy, she's pumping mud!" Oddly, this error message was undocumented. After a fairly lengthy conversation with one of the OS's authors, he stated that this error message should never be reached. For some reason, they had a conditional similar to the following: <CODE> if true { ...do something; } elsif false { ...do something else; } else { print "Shut 'er down....."; } </CODE> And somehow, we managed to be neither true <I>nor</I> false. <P> <I>If things get any worse, I'll have to ask you to stop helping me.</I> 156816 156816