Coding Style Guidelines?

[wolfwalkereci]

Originally Posted by c0ncrete

hah. i just got through trying the 2 character indentation after looking at google's style guide. i had to take a shower afterwards.

Lol man that cracked me up.
I support the idea of any standard the senior dev's put out.

[lerxst2112]

I worked on a project a long time ago that we licensed some code for. It was in C with 1 space indents, all uppercase where possible, and with most variable/function names being 32 characters long which was the limit of the compiler. It was the most horrible thing I'd ever seen.

Even back in the dark days of 80x50 DOS terminals I'd rather break a line in the middle than indent less.

[Drajor]

I have a suggestion which is related to standards, but not so much about syntax. I would love to see ALL embedded SQL moved to a single file and perhaps one day we could even transition into stored procedures.

[trevius]

Thought of 1 more reason why I prefer to stick with tabs over spaces; If we move to spaces, that means I have 1 of 3 possible choices, which all kinda suck:

1. I change every other project I work on to use spaces instead of tabs, so I don't have to switch the configuration back and forth every time on my editors when changing between projects.

2. I change my editor settings each time I switch between projects and hope I don't forget and start mixing tabs and spaces by mistake.

3. I live without the editor config change to use spaces in the place of tabs and it makes coding in the emu a bit more annoying/time consuming.

Again, it is definitely not a huge issue, but trying to keep everything in mind before anything gets set in stone.

[addingice]

I have a suggestion which is related to standards, but not so much about syntax. I would love to see ALL embedded SQL moved to a single file and perhaps one day we could even transition into stored procedures.

I agree on the moving out of inline, I personally would prefer a SQL folder where the SQL goes (maybe broken up by purpose? ,shrug> whatever, out of the inline at least).

i personally would be highly against the stored procedure bit though.

I agree entirely with this piece:

http://www.codinghorror.com/blog/200...s-anyways.html

[KLS]

Yeah definitely no to stored procedures, we're gonna rewrite the database system soonish though. So we can at least support prepared statements as well as potentially other backends besides MySQL if people choose. That all involves cleaning up the current mess that is our SQL though.