Re: some thoughts about php 6

On Tue, Jan 28, 2014 at 7:22 PM, Andrea Faulds <ajf@ajf.me> wrote: > > > On 28/01/14 16:13, Pierre Joye wrote: >> >> Anyone not being a developer will never use it. Let alone conservative >> projects, or already released applications. There is no gain. However >> there are tools already to apply whatever CS one wishes to existing >> source code, or to check CS on commit. That's what one can uses case >> sensitive naming without us having to break everything out there. I >> think we can disagree on that and do not discuss that forever, if >> there is a RFC about it, we will vote on it and that's it :) My >> mistake was to send this mail too early, more important points coming >> :) > > > I don't care about coding style. Coding standards are part of the problem, that's not something we can ignore. > I care about sanity here, Why pre commit checks do add sanity checks to existing projects, today. > and I think > case-insensitivity leads to more problems than it solves, especially, as > others have pointed out, when autoloading comes into play. Right, while I did not meet one for years but we may work with different projects or developers. > A case-fixing tool could be run once on existing codebases, break no > backwards compatibility, and make those codebases work on PHP 6. I will 200% surely change my mind the day I see such tool working with all major frameworks and applications out there without a single point of failure. However, I would suggest to waste too much time arguing about case sensitivity, almost all of us agree that it is a good thing to have. Only question is if it is a good idea at all to do it and only the votes will solve this question. Cheers, -- Pierre @pierrejoye | http://www.libgd.org