The Lounge - CodeProject

I'm not Fatboy although I often got mistaken for him.

Wow, it is nice to hear from you ! Too bad you dropped software, but heck, my last productive line of code was almost 15 years ago, turns out I am better at managing others to do the job for me.
What are you playing ?

I wish you all the best with the kids, and the rest, times are hard.

pompey-boy wrote:
I used to own code project but Chris won it off me during a wild poker game in a strip club in malibu.

I thought we agreed we would not talk about this anymore Smile | :)

Do not escape reality : improve reality !

Are you in this camp

void AFunc(){
}

or this one

void AFunc()
{
}

I'm in the second

Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP

Depends on the language.

C#:

Method()
{
}

Javascrip / Typescript:

function() {
}

same. in C++ i do the latter. In C# I do the former.

To err is human. Fortune favors the monsters.

I have no opinion about braces one way or the other but I have to ask - Why use different styles in different languages? Given it's a choice it seems your personal sense of style would prefer one style all the time. No?

I generally just use what's in the specific language's style guide. It makes it easier when different developers work on a project if we stick to those.

Jacquers wrote:
I generally just use what's in the ~~specific language's~~ style guide.

For C/C++ there is about 42 different bracing / indentation styles fighting for dominance, so referring to "the specific language's" style, as if it was unambiguous, is meaningless.

From a logical point, I would prefer

void AFunc() {
   }

but I have never seen that promoted in any style guide.

The opening brace comes when the statement cannot be completed on the current line, indicating that a block is to follow. You should before you leave the line that you won't find a single one-statement line, but a block. I am one who think "if (day==sunday) weekend = true;" in one line is perfectly fine. "if (day==sunday) {" shows that the statement is not complete.

The following block is indented. An indentation always follows a brace. No an indentation without an opening brace; no opening brace without an indentation.

"if (day==sunday)
   {
   }

starts the indentation before the brace - that is inconsistent!
Undenting follows a closing brace. No undentation without a closing brace, no closing brace without an undentation.

"if (day==sunday)
{
   // indented code block
}

undents before reaching the closing brace - that is inconsistent.

Noone seems to agree with my logic. So I bow my head and follow whatever style guide is enforced upon me.

Switch statements mess up indentation in C/C++. One common layout is:

switch (day) {
   case (day == saturday):
   case (day == sunday):
      celebrate();
      break;
   default:
      gotowork();
      break;
   }

The case alternatives are not blocks, so they don't need braces (that is also why they need the 'break'!), but they are indented! I certainly wish they were blocks, for consistency's sake (and I really dislike the 'default is fall through'), so I prefer to make them blocks, adding braces, to justify the indentation. Very few agree with this logic, too - they are so used to seeing indents without any braces justifying it that the inconsistency doesn't bother them.

Why not just put blocks in if you prefer it that way? It also makes it so you can declare variables under the case without the compiler yelling at you.

C++

case 1: {
    // do work
}
break; // could be inside

To err is human. Fortune favors the monsters.

Yes, like I said. But I do not undent until after the closing brace, so I would indent that as well (and include the break in the block).

Why not just do it? Because you sometimes have co-workers. For some time, I was using an embedded language (CHILL) which provided the loop construct FOR EVER DO - infinite loops are not uncommon in embedded software. In a new job, programming IoT in C, in one of the modules I was responsible for, I added a "#define ever ;;" for being able to program "for (ever) {...". After a few months, this was discovered by another programmer (not working on my module), who immediately searched through the entire repository to reveal ever use of such "programming jokes", changing them all to "while (0)", deleting the #define and adding a rude remark on the edit where he requested that all programmers refrain from such unserious coding practices in the future.

In the next scrum, he brought up his discovery, reporting to everybody how he had 'cleaned up' my code. I asked if he would accept "while (true)", but no: The proper way to code an infinite loop is "while (0)", with a zero. In classical C, "true" is a #define symbol, not part of the base language, and should not be used for fundamental things such as infinite loops.

I got no support from the team at all. Not even for "while (true)".

In a code review with the same team, I was asked why I would "clutter up" the code with such unnecessary braces in switch statements. I had the same remarks when I added braces to justify the indentation in one-line conditional statements, like

if (day == sunday) {
   relax();
}

The coding standard did not allow the "relax()" to be put on the same line as the "if", but mandated the indentation. It didn't explicitly forbid the braces I would like to add - but the programming team did, telling me to remove them.

That's how it is working in a team. You have to be obedient. Don't try to make code more readable, or consistent, or safer, if it breaks with the unwritten laws of the team.

I've been spoiled for years by being in a situation where I set the standards and control the direction on account of my experience.

That said, I understand where you are coming from, but I don't envy you your coworkers. It sounds like you don't have enough written coding standards.

If you all wanted to increase your productivity and reduce problems, you'd have linting and formatting scripts for this if the project is significant enough in size. Or at least that's what I'd do, as it tends to pay for itself in terms of more legible and consistent code, and shorter code reviews. Big Grin | :-D

To err is human. Fortune favors the monsters.

I'm in the correct camp:

void AFunc()
   {
   }

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!

Indented braces ?

Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP

Yep. It's called "Whitesmiths": Indentation style - Wikipedia[^]
It's more consistent than Allman.

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!

That would depend on whether you consider the braces to be a part of the content or the header.
If your answer is neither you should consider GNU style. Poke tongue | ;-P

Wrong is evil and must be defeated. - Jeff Ello

pkfox wrote:
I'm in the second

I second you. Big Grin | :-D

"In testa che avete, Signor di Ceprano?"
-- Rigoletto

I distinctly remember a similar post on this site about 12 years ago.
The replies were all the same then as they are today.
Laugh | :laugh:

The later, is easier for me to follow.

PartsBin an Electronics Part Organizer - An updated version available!
JaxCoder.com

First: Java, Javascript, PHP
Second: C, C++, C#
Who needs braces: Python

Richard MacCutchan wrote:
Who needs ~~braces:~~ Python

FTFY!

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!

Second.

Come on!! What's next? Tabs vs spaces?

Mircea

A POX upon Tabs.

I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.

Please don't go there! One unwinnable debate is enough Smile | :)

We all have our ways of setting braces and indenting which we know to be right and we'll quash the unbelievers who dare to have a different opinion. We've done that since the time of the first crusade Big Grin | :-D

Mircea

I f-f-fart in the general direction of spaces. I had to work on code where some dev used a single space, some two, some 3 and some idiot 8.

As a result it was completely unindented. With tabs there wouldn't have been any issue.

GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X

Welcome to the Lounge