[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Lua Style Guide ?
- From: Sean Conner <sean@...>
- Date: Tue, 6 Jun 2017 11:45:50 -0400
It was thus said that the Great steve donovan once stated:
> On Tue, Jun 6, 2017 at 2:32 PM, Pierre Chapuis <firstname.lastname@example.org> wrote:
> > I think style guide are important at company- or project- level: you
> > typically don't want mixed styles in your code base.
> Yes, that's part of being a professional and fitting in with everyone.
> > At community level I don't care about this. If we could all agree on
> > things that matter even when you don't look at the code (e.g. usage
> > of globals in modules, etc) I would be happy.
> Ditto and likewise! Some things are not a good idea, and there are
> tools which can identify these.
> I once had to use Pylint, and I've never come across a more
> opinionated piece of software, ever. And the real problems were
> happily buried in the style advice noise.
Fortunately, LuaCheck isn't *that* opinionated (it will complain about
lines longer than 120 characters and blank lines with spaces) and what it
*is* opinionated about can be ignored (either through a config file or via
special comments in the code itself).
-spc (Who has found real bugs in his code through using LuaCheck)