On Sat, Apr 14, 2012 at 1:35 PM, Rasmus Schultz <ras...@mindplay.dk> wrote:
> > From: Arvids Godjuks <arvids.godj...@gmail.com> > > To: Kris Craig <kris.cr...@gmail.com> > > Cc: PHP internals list <internals@lists.php.net>, Yasuo Ohgaki < > yohg...@ohgaki.net> > > Date: Fri, 13 Apr 2012 03:26:16 +0300 > > Subject: Re: [PHP-DEV] [RFC] New .phpp File Type for Pure-Code PHP > Scripts > > 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. > > That was my reaction as well. Why someone would spend this much time > and documentation on such a trivial issue, I'm at a loss. Don't we > have bigger fish to fry? > We can walk and chew gum at the same time. Just because more immediate concerns exist doesn't mean that looking at longer-term issues (keep in mind that people are suggesting this for PHP 6, which is quite a ways off) doesn't mean it's invalid. Likewise, the fact that some people might not think this is important doesn't mean that discussing it because some people do think it is important is a waste of time. People bring up issues on this list all the time that I don't think are important, but I have enough respect for them not to derisively post that their issue isn't imporant or that they're wasting everyone's time. I don't think it's unreasonable to expect that such respect would be reciprocated. > > > 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. > > This is what I was thinking, plus this: the closing tag isn't even > required to begin with, so you can really think of "<?php" as a 5-byte > file-header. > Please refer to my previous posts on the matter. For me at least, this isn't about saving a 5-byte tag. It's about making it easier to structure your code with a stronger separation between design and backend function. > I don't see how getting rid of the file-type, and relying on > file-extension instead, is in any way a good thing. For one, IDEs > would need updates, because they use the opening tag to enable > syntax-highlighting. > > If anyone should learn from this, it's the other way around - perhaps > other scripting languages should use a small header to declare the > language/file-type... > I think you guys are stressing-out about the file extension idea a little too much, and here's why: What I'm proposing with regard to the .phpp extension is a convention, nothing more. The actual differentiation will be in the form of a separate handler that's essentially identical to the current one except for the few minor changes outlined in the RFC. In other words, the .phpp extension is NOT mandatory. Just as .php is a convention, so is this. If you want to give it an entirely differnet extension in the webserver configuration, you can do so. The .phpp is just what the convention calls for, but in actuality what matters is that it's just a different extension than what you're using for regular PHP scripts. So I would urge everyone to calm down on this point, because I'm not proposing anything new in terms of how file extensions are used. I would liken it to the difference between .php and .phps. You can give them whatever extension you want, so long as they're different. Make sense? > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
