RE: [PHP] sloppy use of constants as strings. WAS: What does mean?

On Mon, April 30, 2007 9:05 pm, Daevid Vincent wrote: echo EOF BROWSER: $_SERVER[HTTP_USER_AGENT] EOF; Isn't that form (sans quote marks) deprecated and frowned upon? ?php error_reporting( E_ALL ); echo EOF BROWSER: $_SERVER[HTTP_USER_AGENT] EOF; Why would cleaner, perfectly

Re: [PHP] sloppy use of constants as strings. WAS: What does mean?

On 01/05/07, Daevid Vincent [EMAIL PROTECTED] wrote: echo EOF BROWSER: $_SERVER[HTTP_USER_AGENT] EOF; Isn't that form (sans quote marks) deprecated and frowned upon? ?php error_reporting( E_ALL ); echo EOF BROWSER: $_SERVER[HTTP_USER_AGENT] EOF; Why would cleaner,

RE: [PHP] sloppy use of constants as strings. WAS: What does mean?

echo EOF BROWSER: $_SERVER[HTTP_USER_AGENT] EOF; Isn't that form (sans quote marks) deprecated and frowned upon? ?php error_reporting( E_ALL ); echo EOF BROWSER: $_SERVER[HTTP_USER_AGENT] EOF; Why would cleaner, perfectly error free code be frowned upon?

Re: [PHP] sloppy use of constants as strings. WAS: What does mean?

Personally, I *hate* that it does this work, and would love to see a little stricter parsing done and throw a fatal error if you try to use an undefined constant. You can do this yourself. See http://php.net/set_error_handler -- Postgresql php tutorials http://www.designmagick.com/ -- PHP