|The stupid question is the question not asked|
Re: My coding guidelinesby fruiture (Curate)
|on Nov 25, 2002 at 18:51 UTC||Need Help??|
I think it's no great use making guidelines in general. You'll have to agree on guidelines in one project and it's good to have concrete ideas. The actual decisions will depend on the group.
Some of the things you mention are in my eyes means of sane programming (system calls, exit code). I don't think you can work seriously with someone who has to be told these things. Also, I'd never say "SHOULD". Say "MUST", so first of all there is no doubt: "Use strict! No exceptions. That's it." Someone who _really_ knows when to disable strictness, will do it. Someone who doesn't will struggle for a solution and ask for help and then someone else may tell him "This is the exception, you may disable strict here."
So there are some general rules i'd make (and in general i agree with you):
These are the rules I consider "general". Other things are matter of personal taste but should be equal inside a project:
Now finally the Tab-issue: I really think that one should use tabs, but only for indentation. Don't use tabs for alignement.
This way your alignement won't break in someone else's editor using a different tab-width, but logical indentation is still present. I am really convinced that this is a solution.--