|
Hi,
I *switched* from using 'your' style to put the opening brace on the control line after reading Bruce Eckel's book appendix A so that I could easily see the difference between a definition and declaration.
What about house styles?
I'm paid by the hour!
ATL Student
|
|
|
|
|
One probably shouldn't comment out large blocks of code at all. You can always use #if 0. You can leave the comment tokens for actual comments . It is very easy to comment out code this way, with less possibility for error when compared to /* */. There are likely more good arguments but I can't remember any of the top of my head.
#if 0
... lots of code to be commented out
#endif
|
|
|
|
|
I only use /* ... */ to comment out blocks of code while debugging, it's so much quicker to type that using #if 0... with the Numpad. 'Permanently' commented out code will be moved to another file, and a small comment added to the original file saying where to find it.
David Wulff
dwulff@battleaxesoftware.com
|
|
|
|
|
I don't get why people find it easy to read
if (x==0){
do something
}
when the braces DON'T LINE UP !!!!!!
This is much easier
if (x==0)
{
do something
}
because you can SEE where the scope begins and ends - they LINE UP !!
Let the flames begin.
Christian
The content of this post is not necessarily the opinion of my yadda yadda yadda.
To understand recursion, we must first understand recursion.
|
|
|
|
|
> I don't get why people find it easy to read [...]
Remember that for lots of people, Practice makes Habit.
As an example, I would bet that most Americans cannot read Chinese, but with practice, they can. Chinese did not get easier all of a sudden, they just got used to looking at (reading) it.
(Bad) practice makes (bad) habit(s).
Peace!
-=- James.
|
|
|
|