News for hackers. Stuff that matters.

A comment on Why we need a book about naming. Parent comment

Re:Why we need a book about naming by geocar on Thursday February 13, 2020 @05:12AM (#22316588)
> Contrary to parent comment I found it absolutely unacceptable to call a function "asm".

You can take your snark up with GCC, and leave me out of it:

https://gcc.gnu.org/onlinedocs/gcc/Global-Register-Variables...

[ Parent | on HN ]
Re:Why we need a book about naming by quelltext on Thursday February 13, 2020 @05:28AM (#22316643)
I think they may have simple misunderstood what your example was about (G, not asm(...)).

On the other hand their criticism contradicts their earlier point about widely used public/stdlib function names best having short names.

[ Parent | on HN ]
Re:Why we need a book about naming by marcosdumay on Thursday February 13, 2020 @05:39AM (#22316690)
Widely used libraries have one more constraint, in that they will always be used a lot, but they'll never be the most used things on any code base.

As a consequence, they shouldn't use very short names. They should let the 1-3 letter names available for local code. (But there are exceptions, of course. There always are.)

[ Parent | on HN ]