SoylentNews

Writing Efficient C Code?

posted by LaminatorX on Sunday March 16 2014, @03:28AM   
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?"

• Re:Don't be clever Re:Don't be clever (Score: 5, Informative) by forsythe on Sunday March 16 2014, @05:02AM

  by forsythe (831) on Sunday March 16 2014, @05:02AM (#17088)

  I completely agree, and offer Rob Pike's notes [lysator.liu.se]. In particular, rule 3 of complexity stands out:

  Fancy algorithms are slow when n is small, and n is usually small. Fancy algorithms have big constants. Until you know that n is frequently going to be big, don't get fancy.

  Parent

  Starting Score:	1		point
  Moderation		+4
  Interesting=1, Informative=3, Total=4
  Extra 'Informative' Modifier		0
  Karma-Bonus Modifier		+1
  Total Score:		5

• Re:Don't be clever Re:Don't be clever (Score: 1) by Fry on Sunday March 16 2014, @07:38AM

  by Fry (642) on Sunday March 16 2014, @07:38AM (#17114)

  Fancy algorithms are slow when n is small, and n is usually small.

  Which is why I only use bubble sort!

  Parent

  • Re:Don't be clever (Score: 2) by Debvgger on Sunday March 16 2014, @08:27AM

    by Debvgger (545) on Sunday March 16 2014, @08:27AM (#17123)

    I only use Bubble Bobble, sort of.

    Parent