Re: Contribution for PECL
| From: | Alan Knowles | Date: | Sat, 28 Dec 2002 05:15:47 +0000 |
| Subject: | Re: Contribution for PECL | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-11865@lists.php.net to get a copy of this message | ||
Maxx wrote:
otherwise how about just using a letter mtemplate... (looking blindly at some code that used tmpl_xxx or mtemplate_xxx(), you would instantly know what one did, the other would be a guess. (is it some kind of temporary storage?)how about maxxtemplate ? -- seems reasonable appropriate.. maxxtemplate_*Disagree. That's going to be too long for function names, and I don't think it's a good idea to make personal monuments here. actually it was a play on words = as in max = maxspeed... / your name.. - bit like linus <=> linux :)
I'm afraid we will have to call it DummyTemplate. =| At least, in this case noone will ever ask "Why not Smarty?". =) It's not that bad :)
Anyway, I believe that "tmpl_" prefix is good for template functions. It is short and self-descriptive. my only conerns that template engines are one of the few areas where it is almost expect to see numerous solutions to the same problem, and that the only requirement was that the namespaces for each one would not affect other packages. (most of the PHP ones do that by using classes...)- for the end user - if you are running a server with PHPbb, and postnuke, and they used 2 different templating engines.. - you wouldnt want to have conflicting functions....
-Maxx-- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com