Re: cvs: smarty / NEWS /libs Config_File.class.php Smarty.class.php Smarty_Compiler.class.php /libs/internals core.create_dir_structure.php core.is_secure.php core.is_trusted.php /libs/plugins modifier.escape.php

--- Antony Dovgal <[email protected]> wrote:
> On 23.11.2005 23:36, boots wrote:
> > boots		Wed Nov 23 15:36:05 2005 EDT
> > 
> >   Modified files:              
> >     /smarty	NEWS 
> >     /smarty/libs	Config_File.class.php Smarty.class.php 
> >                 	Smarty_Compiler.class.php 
> >     /smarty/libs/internals	core.create_dir_structure.php 
> >                           	core.is_secure.php core.is_trusted.php 
> >     /smarty/libs/plugins	modifier.escape.php 
> >   Log:
> >   replace {} string access with equivalent substr() to avoid
> E_STRICT warnings in PHP 5.1
> >   
> 
> There is no E_STRICT notice in this case anymore.

Hi and thanks.

Has this been announced? RC6 throws the E_STRICT (I have not checked
HEAD recently) and based on the internals discussion and Derick's PHP6
summary notes, I figured it was going to happen. I did write to
internals asking that {} to be left alone (as many others did) but
there didn't seem to be any favour for that opionion.

I discussed this change with Monte and Messju and and while we were all
bothered by it, we decided it would be better to be pre-emptive and
avoid any possible user questions that may arise. Moreso, this means we
don't have to rely on whim quite as much -- surely substr() is safe?
Messju timed it and found (amazingly) that substr() is actually faster
than string offset access.

I also wrote internals and asked if "var" can get aliased to "public"
for 5.1 since it is already planned for 6.0. If that happens then
Smarty will be fully E_STRICT compliant as of 5.1.

Cheers,
boots

> -- 
> Wbr, 
> Antony Dovgal



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

-- 
Smarty CVS Mailing List (http://cvs.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php