Re: [SMARTY-DEV] Re: smarty-dev Digest 29 Apr 2003 17:01:26 -0000 Issue 123

From: Date: Tue, 29 Apr 2003 17:58:51 +0000
Subject: Re: [SMARTY-DEV] Re: smarty-dev Digest 29 Apr 2003 17:01:26 -0000 Issue 123
References: 1 2  Groups: php.smarty.dev 
Request: Send a blank email to php-smarty-dev+get-1302@lists.php.net to get a copy of this message
On Tue, Apr 29, 2003 at 10:41:38AM -0700, boots wrote: > Andrei wrote: > > No way. PHP being case-insensitive is simply bad. Let's not do the > > same for Smarty. > > I have to agree -- it is bad that PHP is case-insensitive. Or more > aptly, party case-insensitive and partly case-sensitive. Making Smarty > case-insensitive has to result in a tiny slowdown. Its dumb. People who > type {$myvar|CapITalizE} should be shot, not supported. > > But I digress. PHP is not not going to be made case-sensitive (IIRC the > heat from the ZE2 thread), ergo Smarty HAS to follow PHP's casing > rules. Its better to be consistently inelegant than schizophrenic. > People's expectations should be met. there is no right or wrong here and there is no common expectation that all people expect when they see something. i'm really sure we meet the expections of quite an amount of people if we have the template-language consistently case-sensitiv. smarty does not (and did never, and will never) touch the case of anything outside the delimiters. i feel very comfortable if smarty behaves the same inside the delimiters. it just took a bit for me to realize. :) a big amount of smarty is for people who are not interested in php or how it handles this and that, or how it php looks or fells or the like. there is no need to follow suit of php here. > xo boots > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > -- > Smarty Development Mailing List (http://smarty.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php

« previous php.smarty.dev (#1302) next »