Hi. Richard Stallman recommends to write functions like this:
int
function()
not like this:
int function();
Can anyone tell me what the difference is to the compiler.
I personally use the latter, but like the look of the GNU style declaration.
thanks.
Remember that all that code you write turns into this:
0100100100110010010011100100111001001
0010100100100001001111100010010010010 ....
The compiler doesn't care.
http://en.wikipedia.org/wiki/Indentation_style
Pick a style, and apply it consistently.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Ah, now I know the name of my style - BSD/KNF style (or similar). I never use two-line headers.
Last edited by maxorator; 05-31-2007 at 07:40 AM.
"The Internet treats censorship as damage and routes around it." - John Gilmore
I only write template functions using two lines for the header
Code:template <class t> int run(t aType) { }
>Can anyone tell me what the difference is to the compiler.
Differences in formatting are for you, not the compiler. That particular convention is designed for code outside of a modern IDE where to search for a function definition, all you have to do is search for the function name at column 0. Any legitimate call will not be at column 0 if you use proper indentation. However, that convention really isn't necessary these days with advanced code editors.
In fact, a lot of older conventions that save you from your stupidity and make working with code easier are obsolete with newer compilers and editors.
My best code is written with the delete key.
Prelude, I think you're forgetting that stupidity evolves just as quickly (or possibly even more quickly) compared to compilers and editors.
Naturally I didn't feel inspired enough to read all the links for you, since I already slaved away for long hours under a blistering sun pressing the search button after typing four whole words! - Quzah
You. Fetch me my copy of the Wall Street Journal. You two, fight to the death - Stewie
Considering how often I'm hacking with minimal tools on the command line, I don't think conventions that make code more readable for such tools are ever obsolete.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
