Re: [SMARTY-DEV] Smarty changes error_reporting() level
| From: | Jan Rosier | Date: | Wed, 08 Oct 2003 10:01:33 +0000 |
| Subject: | Re: [SMARTY-DEV] Smarty changes error_reporting() level | ||
| References: | 1 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-1886@lists.php.net to get a copy of this message | ||
I vote for this.
I also think that turning off E_NOTICE maybe not necessary anymore
altogether since the assign function was changed to accept empty values.
(see
http://cvs.php.net/diff.php/smarty/libs/Smarty.class.php?r1=1.315&r2=1.316&ty=h).
All variables that are assigned in php will also be available in the
template
Greetings,
Jan Rosier
* I like pigs. Dogs look up to us. Cats look down on us. Pigs treat us
as equals. - Sir Winston Leonard Spencer Churchill *
Bharat Mediratta <bharat@menalto.com> wrote:
> I use Smarty as the templating library for a much larger application,
> as I'm sure many of you do. It works wonderfully in that capacity.
> However, I noticed that Smarty turns off E_NOTICE if it is not
> running in debug mode.
>
> In my application, I want to have total control over the warnings and
> notices that are generated so that I can find and fix every
> occurrence. It not always beneficial for me to run Smarty in debug
> mode, but if
> I *don't* do run it in debug mode, then Smarty hides valuable
> information from me. So now, every time I update I have to patch
> Smarty undo this behaviour.
>
> I recognize that by now people have probably built apps that require
> E_NOTICE to be disabled in order to function properly, so I guess it's
> not an option to simply undo this behaviour. However, I would love it
> if we could make this optional. If I submit a patch to make it
> optional, (perhaps by setting a Smarty global variable) would it be
> accepted?
>
> thanks,
> -Bharat