Re[2]: More accurate compiled file names

I  am trully shure that it is IMPOSSIBLE to handle all PHP errors
while  compiling  the  template.  And  more - it is not good from
design  point of view - handle errors of one subsystem (PHP) from
another subsystem (Smarty).

Perl  has  a  very  powerful  eval().  PHP's  eval  is  much more
primitive  -  it  does  not allow us to handle critical errors (I
don't  know  why). So, the only method to improve debugging is to
simplify detection of buggy file.

-- 
Best regards,
  Dmitry Koteroff.

AD> On Sun, 30 May 2004 02:31:49 +0400
AD> Dmitry Koteroff <[email protected]> wrote:

>> Hello.
>> 
>> Smarty  saves  its  compiled  code to files with unreadable names
>> (like  %%23t2763%%sjhdjsdhjshgd.php).  It  makes too difficult to
>> find  fatal  error in the template (for example, {$obj->spoon()},
>> where spoon is non-existent method).

AD> Again, I don't see any point in fixing this.
AD> Imho compiled templates are some kind of technical data, which
AD> should not be read by user/programmer. 
AD> Forget about them, these errors, which you're talking about, should be
AD> handled BEFORE they happen.
AD> So, I'm strongly -1 now.
AD> But I would give my +1 for a patch, which will allow to handle all
AD> possible errors before they get into compiled templates.
AD> What do you think about such patch? Can you try to write one?

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