[bdfh42]

But you could reduce the JavaScript style guide entries to just "Use JSLint and do what it says".

Perhaps the others are more helpful or perhaps (more likely) other languages do not have Lint.

I am sure there is more to it but does not require lengthier posts - perhaps essays?

[diegoloop]

This is just an alternative for guidelines! It's like asking the developers what they really use in their daily code.

... I implemented so, that the title and the language are required, the description is not, so you can just have. Use PascalCase for methods. and added the C# tag, for example

[bdfh42]

Ok - but do you think that (continuing the example) the JavaScript entries do add up to something more than just what Lint says to do? Cos I can see it.

I do think there are benefits in more assistance for people with style and structure - I was just wondering if a longer format would suite the need better.

[diegoloop]

I think there is no right or wrong in writing code, it's a matter of style, so at CSG you have different alternatives and you can just pick what you think is most convenient for your code!

I dont understand what you mean by "if a longer format would suite the need better"

[bdfh42]

Surely "style" is more than "use === not ==". That's a tip - and perhaps not worth a lot as a tip if there is not a full explanation to back it up. "Why not?" and "What's wrong with that?"

Does not style devolve from structure? Hmn - maybe Structure devolves from Style. Tricky - thus I think that without a "long form" explanation of what you are trying to achieve and thus how each "tip" fits into the objectives then the contribution is lessened.

The original objective was to write "better" programs in a new language - a very worthy objective but without analyzing what "better" means and how any component contributes to "better" then I am not clear how you have advanced things.

I laud your objectives - and was just wondering about (grin) the style.