News for hackers. Stuff that matters.
Re:An Alternative Operator Precedence Rule (2013) by vidarh on Friday July 17, 2015 @08:43AM (#9902425)
> There's no round trip in the editors I've used.

My point exactly. It's an incredibly hard problem.

> You have the standard formatting, and that's it.

Which is why I don't use any of those editors, and won't ever do so.

> This functionality is actually a benefit, because you can type in something like this:

Every editor I've used in the last 20-30 years or so has been able to do that, but none of them have forced me into a specific formatting that I can't override. That's the difference.

> I don't really have a problem with automatically making everybody's code look pretty much the same.

Well, I do, and enough people I've worked with do (EDIT: The issue is not making everybody's code the same; the issue is that I'm not willing to have a specific format dictated to me and so unless everyone will format their code like me I won't use tools that attempt to force a single style), and so any attempt to standardise tooling like that just ensures that environment/language has one more barrier against adoption. There's plenty of people like me that avoid Python "just" over significant indenting for example.

Re:An Alternative Operator Precedence Rule (2013) by to3m on Saturday July 18, 2015 @06:39PM (#9909236)
Well I did say that I expect fixed formatting will become more common over time. Having to press the space bar less is one reason. Discussions such as this one are another ;)