RE: [SMARTY-DEV] case-insensitive plugins

I'm not 100% on either side of the fence on this one (yet), but I think our decisions must be based upon the future and longevity of Smarty. Helping out the designer is good, but we also don't want to do anything that will cause unforseen problems or limit future possibilities. It sounds like a compromises must be made at some level. (I certainly don't think we want this configurable.) Maybe some examples will help: {foo var="blah"} {FOO var="blah"} What would you expect to happen? Both call the same function "foo"? Call different functions "foo" and "FOO" (which throws error on not found)? Or? How about modifiers? {$foo|bar} {$foo|BAR} Also, we haven't touched on the case of attributes. They are currently case-sensitive AFAIK. {foo var="blah"} {foo VAR="blah"} Monte On Tue, 2003-04-29 at 20:32, boots wrote: > warning: more CS, doh. Don't take it overly serious. > > --- Luis <luis@fuegolabs.com> wrote: > > most interfaces will be HTML based that's why XHTML is important. > > How does HTML make XHTML important? I should think it makes HTML > important. > > > they will understand that <B> is wrong and <b> is right > > Why in the world is <B> wrong and <b> right? Because a face-less > commitee populated by people working for companies with immense > self-interests say so? Who does this help? Machine parsers, which have > one iota less work to do. It doesn't help the designer one bit. It > doesn't make him more expressive, doesn't solve any design challenges > or improve anything at all measurable. All it does is make the system > fragile to case errors which in themselves have no semantic meaning. It > doesn't help the application designer one bit because (alas) in PHP, > you can't implement different funtions whose names vary only in case. > It makes his life worse because now he is also binded by the fact that > the filesystem of some (but not all) platforms are CS. Smarty doesn't > have very robust debugging or error reporting--it is hard, but mostly > frustrating, to track casual errors--especially for "designers". From > end-to-end it adds nothing to the experience or process of anyone Doing > Their Job. So everyone is unhappy except the parsers. Okay that's > unfair. It makes beard stroking gurus happy because they got everyone > doing things The Right Way. > > As it is, nothing is easy. Must everything be hard? People don't think > about case when it doesn't add any meaning to their process. If someone > on this list marks a quote as "boots", "Boots" or "BOOTS", who > are they > talking about? > > BUT CS is in the XHTML (via XML) standard. So you gotta ask yourself: > is this a pragmatic world or not? If so, then IMVHO tying your ribbon > on the XHTML donkey's tail is not the safest bet. > > I can't believe I couldn't keep my mouth shut! My bad. > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com -- Monte Ohrt <monte@ispi.net>