Re: [SMARTY-DEV] optional spaces for modifiers

> Hi David. Takes a Wom.bat to get the zoo going, huh? yes... unfortunately, here in good old Germany, we have one single Wombat in a zoo far, far away from my home :) So somebody has to keep you folks up to scratch :) > Anyhow, OPTIONAL spaces only don't belong because the scanner wasn't > written with that in mind. In all respect, its superfluous to you, but > to me, it means something ;) For the same reasons, too, that { $var } > et al. are supported. Well... but you always have some sort of "rules", not only regarding programming. This issue with case-insensitivity (you remember? :)) seemed superfluous to some people too, but not to me, and the patch was reverted, despite the fact I needed it - because most people thought it didn't make sense... (I don't want to knock over my anger about this "failure" onto this issue, don't think that, please :)) Even daily life forces us all into certain norms, they keep things kind of clean and standardized... maybe it's more comfortable with that syntax, but a coffee-cooking Smarty would be comfortable, too, wouldn't it? :) Maybe I just didn't understand why you'd like that syntax supported, maybe you should tell me, so that I can understand. > Its not about teaching monkeys how to type, its about reading what the > monkey wrote--perhaps ten months later after the original monkey has > flown the coup (as monkeys are apt to do) and a new monkey is trying to > figure out where the bannanas are kept. The monkey was just an example, it was by no way meant devaluating or something like that ;) > Seriously, if it doesn't break anything, then I don't see why you > should reject it out of hand. Monkeys need space, too. Yes... maybe you're right. I just read that message, you know, and remembered some people saying Smarty is too weighty et cetera, ... I'm just a fan of programming languages with strict rules and syntax, and PHP is already far too sloppy regarding that, so why should Smarty become, too? :) Regards, David