Hello Roman, Stas, even more so you want to have it as close as possible so that one can in fact get a clue what is going on manually. And if only generators use that stuff - well it doesn't matter to a generator if it has to write braces or not. We create syntax for humans - otherwise we would simply do binary stuff
marcus Thursday, December 6, 2007, 2:09:49 PM, you wrote: > I don't agree with that. I think multiple namespaces per file would be > fine with the current syntax as this is a feature that would not be > used by that many people and if it's used it's not for development > purposes (who wants to read a class bundle with no comments, > linebreaks etc.?) and therefore the readability/consistency doesn't > matter much. > It's not that I don't like braces but imho its not a necessity to move > to braces just to allow multiple namespaces in a file. > Roman > On Dec 6, 2007, at 1:34 PM, David Zülke wrote: >> Am 06.12.2007 um 04:22 schrieb Jeremy Privett: >> >>> I know I just finished praising you just some hours ago, Stas, but >>> I'm going to have to step in and agree with Larry on this one. It >>> really doesn't make sense for there to be no braces for namespaces >>> (especially if you're going to allow multiple per file). A >>> namespace is a logical grouping of classes/functions and other >>> constructs of this type in PHP use braces. That is very confusing >>> syntax when compared to other areas of the language. >> >> +1. If we allow multiple namespaces per file, then braces are an >> absolute must for consistency IMO. >> >> >> David >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
