Toby Butzon wrote:
> Come on... mixing PHP and HTML in the same file isn't bad
> style... in fact it can make things easier to read, if you
> do it right.
>
> This is one of PHP's biggest features... otherwise we'd just
> have another Perl...
>
> ....my .02...
There are more differences between PHP and Perl than this.
Anyway, mixing PHP and HTML ties you HMTL rather firmly to your
PHP-Code and you will never be able to let anyone who doesn't know PHP
edit you design, which tend to be a bad thing since many
PHP-programmers don't like to design and most designers don't know PHP.
You get the most readable (smallest, in this case) code by generating
the HMTL in special functions calls, or by including you HTML. There is
no need to have that nasty HTML bloat your actual code, is there?
Ever heard about templates? This way, even a dumb designer who can't do
more than click-and-point can edit your design.
I, personaly, never found any use for having HTML and PHP highlighted
in the same file and am pretty contenc with emacs cc-mode or that
php-mode I got somewhere, which both don't do that.
There may of course be cases where nesting PHP in HMTL is useful, but I
can't think of too many of them now and never encountered one.
Especially with bigger projects, it definately is not the way to go.
Wagner
--
Sanity is calming, but madness is more interesting.
--
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]
