Dev.SN ♥ developers
Sections
Dev.SN
posted by
LaminatorX
on Saturday March 15 2014, @11:28PM
from the premature-optimization-is-the-root-of-all-evil dept.
from the premature-optimization-is-the-root-of-all-evil dept.
Subsentient writes:
"I've been writing C for quite some time, but I never followed good conventions I'm afraid, and I never payed much attention to the optimization tricks of the higher C programmers. Sure, I use const when I can, I use the pointer methods for manual string copying, I even use register for all the good that does with modern compilers, but now, I'm trying to write a C-string handling library for personal use, but I need speed, and I really don't want to use inline ASM. So, I am wondering, what would other Soylenters do to write efficient, pure, standards-compliant C?"
This discussion has been archived.
No new comments can be posted.
Writing Efficient C Code?
|
Log In/Create an Account
| Top
| 1000 moderator points
| 75 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I'm not a robot like you. I don't like having disks crammed into me... unless they're Oreos, and then only in the mouth.
-- Fry
(Score: 0) by Anonymous Coward on Sunday March 16 2014, @08:10PM
(Score: 1, Troll) by frojack on Sunday March 16 2014, @08:18PM
When the screen you post from clearly shows the supported syntax?
Discussion should abhor vacuity, as space does a vacuum.
(Score: 2) by maxwell demon on Monday March 17 2014, @01:26PM
Actually <blockquote> is the old one. It worked already before Slashdot introduced <quote> with its slightly different spacing behaviour, and it never stopped working.
The Tao of math: The numbers you can count are not the real numbers.