On 12/06/2010, at 8:43 AM, Daevid Vincent wrote:

>> -----Original Message-----
>> From: tedd [mailto:tedd.sperl...@gmail.com] 
>> I believe, just because it can be done doesn't mean that it 
>> should be done.
>> My practice is *never* to use <?=
>> In fact, my practice is to not only use <?php echo, but to enclose 
>> the echo argument with a (), like:
>> <?php echo("The answer is $answer");?>
>> I am sure there will be some that think that my practice is an 
>> overkill, or not "good practice", but it's a good thing that we all 
>> have a choice. Make your choice to best serve how you want your code 
>> to look.
> As per http://us3.php.net/echo
> echo() is not actually a function (it is a language construct), so you are
> not required to use parentheses with it. echo() (unlike some other language
> constructs) does not behave like a function, so it cannot always be used in
> the context of a function. Additionally, if you want to pass more than one
> parameter to echo(), the parameters must not be enclosed within
> parentheses. 
> So you might want to reconsider your coding practice/style here and use the
> construct as designed or you might end up with a far worse scenario than
> short-tags could ever provide. Something more along the Python "print"
> debacle.
> Also, for the love of God, please don't embed a variable into a literal
> string and use preprocessing.
> Do it like so:
> <?php echo 'The answer is '.$answer; ?>

If you're doing it like that, you may as well use:

<?php echo 'The answer is', $answer; ?>

and leverage sending echo multiple parameters rather than using string 

Simon Welsh
Admin of http://simon.geek.nz/

Who said Microsoft never created a bug-free program? The blue screen never, 
ever crashes!


PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to