Re: Re[10]: [SMARTY-DEV] More accurate compiled file names

On Mon, 31 May 2004 19:57:25 +0400 Dmitry Koteroff <delete@koteroff.ru> wrote: > AD> We should give deleloper possibility to forget about compiled > AD> templates at all. > Unfortunately it is impossible (at least before PHP's eval is not > grown up from the baby pants). I really don't see any need in "advanced eval()". 1) > Oh, really? (-; I just align compiled template FILENAMES in this > thread, not a machine code. 2) > I am writing there about line number synchronization. hmmm... =) there's something wrong with these phrases. > >> Text "generated for machine and for machine" could be readable by > >> human too. And if I should not pay for that and even must not > >> loot at them more often than before, why not? > AD> Could != Should > AD> I could jump off the roof, but should I ? > But what would you say if the President modify the law to > prohibit roofjumping for all the people in the world? It's silly. > (-; Well, nobody prohibits you to do it. It's just not recommended and seems rather silly to me to make roofs more comfortable for jumping =) But you are free to do it, of course. It's OpenRoof... oh, I meant OpenSource. > AD> Ok, let's stop here. Imagine such situation: Smarty handles > AD> most of possible errors correctly. And you don't have to look > AD> into compiled code to learn what happened. Is there some real > AD> need to dig compiled templates? > No. But there is REAL need to detect full source template name > (no any words about compiled code at all, eh?) on unexpected > fatal error. ok, no compiled code. readable filenames are good. > AD> no error -> no message -> no need to handle > "Every program has at least one error." > (seems, Knuth). Knuth is using Smarty? wow =) > You may disable message, but you cannot disable error. yep, you should handle it. that's right. that was the main my idea. let's improve error handling in Smarty Compiler. > Smarty should make all the people in the world happy! Please, > modify its code to achieve this. (-; ok, I'll offer $smarty->makeHappy() method shortly =) > Not satisfied - just astonished. (-; And all this four years you > programming without E_NOTICE and do not differ error and error > message? Strange. Strange and sad, that you've totally misunderstood me. > Maybe I don't know that I want, but I have a patch which works > and which is very useful in practical situations. (-; I'm proposing you to write a patch, that will be even more useful, 'cos your current patch seems to be not so popular, as you thought. Of course, we can do it together, if you don't mind. > AD> Maybe you need to read this: > AD> > AD> http://smarty.php.net/manual/en/chapter.debugging.console.php > How do you plan to use debugging console on E_ERROR raising? > I can use C debugger (gdb, for example) to debug crushed program. Do you know, that E_ERROR is not the only error type in PHP? =) I believe you do. > AD> So, this letter was just my imagination: > AD> > AD> http://lists.php.net/article.php?group=php.smarty.dev&article=2319 > AD> ? > And? Working with source template, not compiled, when we got > error message (E_ERROR or E_WARNING - no matter). The letter is > about that. (Glad to see that you have read this.) I thought we agreed to forget about compiled templates. BTW, you can help us to translate Smarty docs to Russian, if you want. I suppose it could be quite useful for your new book. Feel free to contact me about it. -- Wbr, Antony Dovgal aka tony2001 tony2001@phpclub.net || antony@dovgal.com