On Thu, Apr 12, 2012 at 5:26 PM, Arvids Godjuks <arvids.godj...@gmail.com>wrote:
> Well, I just don't know how i can appeal to common sence to some people on > the list anymore. First the type hinting threads, now this. > With all due respect, Arvids, get over it. People are going to propose ideas you don't like. I'm going to propose ideas you don't like. You can either handle it like a mature adult or you can alienate the very people you're trying to persuade. I've seen a disturbing pattern of hostile behavior bordering on abusiveness from you on a number of threads and I would ask you to take a deep breath and tone it down. If you don't think you can post a response without engaging in personal attacks and hyperbole, walk away and come back to it later when you've had a chance to get the initial emotion out of your system. Spraying the list with insults whenever someone disagrees with you is not an acceptable way of working with others IMHO. So please try to work on that. > The world does not work only on one web server and there are different > type ls of them out there. I for once use nginx and i configure how to run > scripts by locations, not by file types. I just pass the params to fastcgi > server thet runs a php binary. And it does not.care about the extension. I > can use any extension.l for my code. Yes, i use .php, others use. phtml or > other variants. Extensions are just a convension, nothing more. You can > give a file any or none extension at all and it will not change a thing.Ok, > in windows you will not be able to open the file in a program by double > click, but through the open dialog in the app - be my guest. To PHP, > fastcgi and the web server it does not matter. It just matters to people so > they can distingush between a php file, js file and a css file. > I'd prefer to avoid getting into a heated argument over something that amounts to little more than semantics. Yes, file extensions are a convention by their very nature. And yes, there would need to be some changes in order to add support for a second parsing type. But you'll notice that's why I listed the target PHP version as 6.0. A major release such as that is where one would expect these sorts of fundamental improvements to be made, plus it gives us a long time to sort out the technical details since 6.0 won't be coming for at least another few years. --Kris 13.04.2012 2:01 пользователь "Kris Craig" <kris.cr...@gmail.com> написал: > > >> >> On Thu, Apr 12, 2012 at 4:44 PM, Arvids Godjuks <arvids.godj...@gmail.com >> > wrote: >> >>> So ok, i write my code in files without extension, what happens? >>> >>> As it was said before, interpreter will not distinguish by the file >>> extension, ever. It is os dependant and so on. >>> >>> Why are you poluting the mailing list with things that are clearly said >>> will never happen? >>> >> You might want to consider using less inflammatory, disrespectful >> language if you want people to respond favorably to your questions. I.e. >> accusing someone of "poluting [sic] the mailing list" because they posted >> an idea you don't like is neither constructive nor necessary. >> >> That being said, the .php file extension is not, as far as I know, >> determined by the operating system. It's determined by the webserver >> configuration. So if you have two different extensions, each with a >> separate SAPI handler to differentiate between them, there's no reason why >> this wouldn't work just fine. After all, the internet didn't explode when >> we dropped the .php3 extension. ;P >> >>
