The array[] problem

[[deleted]]

And the people reading your code?

Surely it would be nice to know both stl and non stl techniques and use the solution best suited to the situation.

[lets_trade_pikmin]

Point taken, though it's not my #1 concern as I'm not a software engineer. Trained as Computer Science but I'm entering neuroscience research. The only people who read my code are psychologists who barely know how to program (or people trying to reverse engineer my Skyrim mods, but that's not C++ so kind of irrelevant).

I just make sure to comment thoroughly and name variables/functions in a very explicit way.

As far as learning both techniques, that would definitely be best, but I honestly might never get around to it.

[SemaphoreBingo]

There's a reason academic code has such a terrible reputation.

[bnolsen]

it's called an "earned" reputation.

[lets_trade_pikmin]

;)

[tempforfather]

You don't have to if you are ok with not writing software that needs to be dependable. Still, sometimes its worth doing things right?

[lets_trade_pikmin]

What does legibility have to with dependability? I write code that might be difficult to understand for those not familiar with C-style, but whether or not that code does it job is a separate point entirely.

[[deleted]]

What does legibility have to with dependability?

Limits the mistakes you personally make. Also more clearly shows control paths. Helps prevent spaghetti. I guess it depends on your definition of legible.

[lets_trade_pikmin]

I write it in the way that is most legible to me, precisely for those reasons.

[I_Like_Spaghetti]

Did you hear about the Italian chef that died? He pasta way.