Re: PHP 4.0 Bug #8294 Updated: Documented behavior of @ operator does not match actual behavior

** Reply to note from =?windows-1252?Q?Andr=E9?= Langhorst <A.Langhorst@itbnet.de> Sun, 17 Dec 2000 06:03:53 +0100 > > > I did not state that the behavior of the operator was was a problem. :) > > I stated that the documentation does not match how the operator behaves. I > > also noted that I thought that the current behavior made sense... > > sure, I *guessed* that such a clear thing does not need extra > documentation (the fact that "fatal error"s and "parse error"s are > significantly different) and I *guessed* that poeple are smart enough > to understand, that the parser does not want continue encountering > things like this: fo{o(); > I've got to say it... Never underestimate the power of human stupidity! - Lazarus Long (from: Time Enough for Love - Robert A Heinlin) But seriously, newbies with a web design background will have no idea about the difference between a parse error and a runtime error. Rick Widmer Internet Marketing Specialists http://www.developersdesk.com