View Single Post
Old 09-01-2025, 05:55 PM   #16
jbjb
Somewhat clueless
jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.
 
Posts: 779
Karma: 10535853
Join Date: Nov 2008
Location: UK
Device: Kindle Oasis
Quote:
Originally Posted by Quoth View Post
Who are these "expert programmers"?
You’ll know them when you see them 😂.

Quote:
Array accessing is NOT user pointer/address arithmetic
In C it most definitely is. A[B] is by definition just another way of spelling
*((A)+(B)), which is clearly pointer arithmetic.

Quote:

Worry about improving performance after it's working.
For many applications performance is part of the definition of working, e.g. hard real-time control.


Quote:
Unless you are coding 200 Ms /s DSP or a tiny micro controller managing 1MHz signals, performance is the last thing to worry about.
Precisely my point- sometimes you *are* writing high speed DSP code or using tiny embedded processors (or kernel code, or memory management code, or any of a gazillion other areas where pointer arithmetic is useful).

What’s normal in one field isn’t necessarily so in others.
jbjb is offline   Reply With Quote