Actually, the pages I've been working on lately have been so code-intensive
I've found it easier to echo/print the HTML, especially as not that much
has been generated.
When I turn PHP on and off I tend to have "OOPS" scenarios, and have to go
searching for the previous "?>" or "<?".
Miles
At 06:12 PM 01/10/2001 -0500, Brian Clark wrote:
>Hello Alexander,
>
>(AW == "Alexander Wagner") [EMAIL PROTECTED] writes:
>
> >> Mmmmppppfff... ultraedit's wordlist file still lacks the color of
> >> allaire's homesite - it does detect which parts of the .php file
> >> are HTML and what parts of the file are PHP code, and colours
> >> syntax very well...
>
>AW> Who needs that? Nesting PHP in HTML is bad style, IMHO.
>
>Bad style?!
>
>You _actually_ print() or echo() everything you want to send to the
>browser?
>
>If it doesn't need to be interpolated by PHP, why print() it?
>
>-Brian
>--
>Life may have no meaning, or, even worse,
>it may have a meaning of which you disapprove.
>
>
>
>--
>PHP General Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
