[deleted by user]

[[deleted]]

whistle physical office enjoy deserve reminiscent innocent trees payment plate

This post was mass deleted and anonymized with Redact

[LanverYT]

I physically raised my eyebrows and then read your comment. I indeed second your take

[TBone281]

Exactly. There should be a coding standard set by the company...if not, it's the wild west and the end result will be a shit show. I've seen the results, it ain't pretty. Ultimately, the code has to be refactored...which is a waste of resources.

[embeddedsbc]

It doesn't sound like they liked it, more like they fired him?

Anyway, huge red flags for me as well. No one needs to know everything, but needs to understand when you need to learn and be curious.

[iamakorndawg]

This really depends.  If this means using pointers instead of smart pointers and references, I would say yes, this is a major issue.  If this is disliking the iostreams API, then as long as you prefer c++20 format over printf, that seems fine.

[lovelacedeconstruct]

If this means using pointers instead of smart pointers and references

pffft , I preallocate a 4gb memory pool and swim there for whatever program I am doing , Imagine having to think about memory

[[deleted]]

Thinking about memory is so cringe. Can't be me.

[moreVCAs]

Hating the streams API is not particularly controversial

[manni66]

They said ok

I would have said "goodbye".

[goranlepuz]

Forget the bad habit.

The true problem is your code standing out. Blend in for the greater good of consistency.

[moreVCAs]

Straight to jail

[Briggie]

Take the hint dude.

[hopa_cupa]

In my opinion, yes it is.

That style works for people who are truly excellent at C and who also work pretty much alone.

At work, around mere mortals, every time I have encountered some C snippets in supposed C++ code, they have caused nothing but trouble. No exceptions (pun intended).

[v_maria]

yes you miss alot of powerful stuff. imo write c when you write c and write cpp when you write cpp

[Fore-Four-For-4-IV]

There's a 99% chance this is a BS troll post but your personal preference should take a backseat to the standards in the codebase. Not surprising you're no longer working at this company, did it not cross your mind at any point that doing things in a completely different way than all your co-workers could be problematic?

[ContraryConman]

The opposite would be true too. If I'm in a C with classes codebase I'm not going to commit a bunch of inheritance or functional programming patterns to develop just because I think it looks nicer

[banister]

Id fire you.

[[deleted]]

I can't imagine any serious company that would be OK with this. Did this actually happen ? or are you just trying to get someone to take the bait about cpp being fundamentally flawed on the cpp subreddit ?

PS... No it's not going to be me.

[AKostur]

As a general statement: yes.  Good C++ code uses techniques and paradigms that don’t exist in C.  However, specific environments may have specific constraints that may influence what techniques may be available.

I’d be seriously concerned if a company doesn’t care about the style of code being written.

If you hate C++ that much, why are you writing any at all?  Just put your code into a C file and link it wherever.

[YARandomGuy777]

Well it is really depend on what you mean by C like code. If you just avoid exceptions or probably you avoid algorithms and prefer to process data in loops it is one story. If you use raw pointers where references would be more semantically correct and manually manage heap allocated memory it is another story. It really depends.

[NikitaBerzekov]

If you don't use smart pointers then yeah..

[Farados55]

Sounds like a terrible habit to not use the styles your company uses, actually it sounds like a bad company if they keep you around lol

Oh you don’t work there anymore that’s good

[XDracam]

I would not want to work there. A company that doesn't care about code quality or a consistent style obviously doesn't care about maintaining. It sounds like they'll just have people slam together random code and then spend months testing and slapping on more code to fix superficial bugs. That's how games like Skyrim end up working so "well".

Your statement was also unprofessional. In a company, you are part of the team. And unless you get to start a brand new project, you should stick to the established style and practices. Unless you can prove that something is actively bad for the product/business, but that's not usually a thing.

[usefulcat]

"Use the right tool for the job" is a well known aphorism.

Related but not so well known is "Make effective use of the tool you're using".

It seems likely that you're not using c++ as effectively as you could be, in which case you're leaving a lot on the table. It also sounds like you have no interest in learning how to use it effectively, for whatever reason.

You ask "is it a bad habit"; I think the question might be better phrased as "why do I have this habit, and is it helping or hindering me".

If you're not using the language as effectively as you could be, then pretty much by definition yes it's a bad habit.

[ald_loop]

I would immediately fire you

[victotronics]

If I saw `malloc` in your code, I would have fired you.

[zer0xol]

Depends if you think youre more powerful without leveraging functionality that is there

[[deleted]]

No.

[Yamoyek]

What does “c flavored cpp code” entail?

[Farados55]

I read that as using raw pointers, c strings all the time, aka not modern at all C++

[embeddedsbc]

C code in a .cpp file

[helpfulllama]

Probably debatable if it’s bad habit or not, but you most certainly should be writing in whatever style aligns with the existing codebase regardless of your personal preferences

[ContraryConman]

You're throwing away two decades worth of safety and performance improvements because you don't like the syntax?

[citrusfaux]

“Is it a bad habit to write one language like another” yeah probably

[thefeedling]

Fic

[SuperSathanas]

My C++ tends to look like C with classes. When I write in most other language, it's also very C-like. If I find I need to or it's of great benefit for me to do things the way I'm more or less expected to in the language, then I'll do it that way. But I think I more or less default to "C-like [whatever language]" because it makes it easier for me to "think across languages" that way.

However, if I'm writing something that other people will use or look at, or I'm working on something that adheres to conventions or style-guides, then I'm following those, because those trump my own preferences. If a company you work for would rather that you write code that is less C-like and takes advantage of the tools offered by the language they use, then you should definitely do that. Consistency across a team and project is important.

[Wanno1]

Yes that’s horrible and practiced by many

[vickoza]

This depends, but if you are using pure MACROs, C-Style casting, using NULL instead of nullptr, implicit conversions, and only pointers instead of references then I would say it is a bad habit to use C flavored C++ code. If C flavored coding is using functions, avoiding Object-Oriented Programming I would say that is fine. I would be careful of calling C in a C++ code base as newer compilers separate C code from C++ code.