2 ms·
> Not that you could not write it, but seeing this would not pass me reviewing the code. hear, hear... Few of my recent features were passing through 7 layers
by trhway 12y ago
> Not that you could not write it, but seeing this would not pass me reviewing the code.
hear, hear... Few of my recent features were passing through 7 layers owned by 4 teams (C++) with one team also having Java subteam (who seem to have never heard about Java coding style, etc...) Each team has a person who like you is enforcing his the _only_ right way ... which happen to be different from each other. Well, i just code to whatever style that module is written in :) After 25 years in the industry i've seen a lot of "right ways"...
>The add_one example, as simple as it is, is a horrible example.
>Why not embrace value semantics and write it like:
int add_one(int x) { return x + 1; }
>There is simply no need for pointers or references. Write simple code first.
yea, man. That particular style is there too. Slow as hell. Works for the teams of really average programmers who can't grasp and keep together in mind more than one simple aspect of a small piece of functionality at a time.