On 2005-11-18, Robert Cummings <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-11-18 at 03:12, Derick Rethans wrote:
>> On Thu, 17 Nov 2005, Robert Cummings wrote:
>> 
>> > On Thu, 2005-11-17 at 16:42, Rasmus Lerdorf wrote:
>> > > Andreas Korthaus wrote:
>> > > 
>> > > > Can someone tell me the reason for this decision?
>> > > 
>> > > Very few people converted to using {} so the argument about reading old 
>> > 
>> > Ugh, so those of us that did are going to have to comb back through our
>> > code and revert after following the original suggestion. UGH!
>> 
>> This should fix all occurences (even with PHP 5.1.0):
>> 
>> for i in `find . -name \*.php`; do php -l $i; done
>> 
>> atleast, if you turn E_STRICT on, with some smart grepping you know in 
>> no-time what to change.
>
> That's pretty cool. I always forget about the -l option. Thanks.

Scripts might act weird if you have spaces or other odd chars in your
directory names.  

find . -name '*.php' -exec php -l {} \;

-- 
Met vriendelijke groeten,
Tim Van Wassenhove <http://timvw.madoka.be>

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to