Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by LaminatorX on Sunday March 16 2014, @03:28AM   Printer-friendly
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.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by bucc5062 on Sunday March 16 2014, @01:13PM

    by bucc5062 (699) on Sunday March 16 2014, @01:13PM (#17167)

    "what would other Soylenters do to write efficient, pure, standards-compliant C?"

    Hire someone. Then, last time I wrote in c was back in college. Hell, back then we wrote c on punch cards, fed it into the univac machine where it spit out assembler cards that we then fed to the multivac to solve life's questions. Good times. Kid's got it easy these days.

    --
    The more things change, the more they look the same
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Monday March 17 2014, @10:51AM

    by Anonymous Coward on Monday March 17 2014, @10:51AM (#17502)

    Univac couldn't handle C code.