I'm with you on that. You guys taught me code separation and even when I write Javascript and CSS I always use an external separate file.
Code -> presentation separation is how I've learned and I prefer it that way.
However I think it is just a poor implementation as i'm sure you could separate PHP and HTML and use includes also to achieve similar separation.
But I also had a situation where my sisters boyfriend contacted me in a panic as their ecommerce site went down, it's written in PHP.
He asked me to look into it for them, when I ran the script it threw a tonne of warnings for bad coding such as non-declared variable use (like strict), but this didn't stop the script running.
I said we need to clean this up, I'm not a PHP head, so before I can work out why this script has stopped working, we need to clear up these bad practice errors and diabolical coding.
He wasn't interested and just went on about how it had worked for years, I left him to it.
so my experience with other peoples PHP isn't a good one either, very sloppy coding indeed. Though I did work on an open source project called the Google Rank Extractor and ported over someones PHP to a perl version, it was the best PHP I've seen yet, but still didn't separate PHP & HTML! - dunno maybe us perl heads are more anal? aferall there is some diabolical perl code out there, I shudder at the code I used to write a few years back!
Or maybe the difference is as this forum says ->
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS
;-)
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
MIME::Lite TLS Email Encryption - Perl v0.02 beta