I absolutely agree with Benjamin. It would be bad mojo for the engine OR the client to silently ignore any error. While it may be trivial for the developers to code around your type, they can't code around all of ours. I constantly type form for from but I do not expect the client or the engine to make up for my deficiencies.
I know the original poster was trying to make a point of offering a helpful suggestion (at least that's what I got form your original post) but 1) he/she/it addressed it as a bug(let) which it is not. It is at best an annoyance to the original poster. 2) It is bad form to expect the client/compiler or interpreter of any language to make up for your typos. BTW, the source is available to MySQL, if you REALLY consider it a bug, fix it and submit the patch...and can you do the form->from thing for me too? :) =C= * * Cal Evans * The Virtual CIO * http://www.calevans.com * -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Benjamin Pflugmann Sent: Tuesday, July 23, 2002 2:06 PM To: Alain Williams Cc: denonymous; Gerald Clark; [EMAIL PROTECTED] Subject: Re: Very minor buglet IMO, it's the right thing. An empty command makes no sense. Having an empty command is a mistake. The interpreter should inform me, if I make a mistake and not silently ignore it. Maybe the double semicolon is the result of a bigger mistake. The interpreter surely is not able to spot any mistake I am able to make (in fact, the opposite is true: it can spot only a few ones), but when it can, it shall inform me. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
