Stories
Slash Boxes
Comments

Dev.SN ♥ developers

Writing Efficient C Code?

posted by LaminatorX on Saturday March 15 2014, @11:28PM   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.
Writing Efficient C Code? | Log In/Create an Account | Top | 1000 moderator points   | 75 comments | Search Discussion
Display Options 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: 4, Informative) by c0lo on Sunday March 16 2014, @03:03AM

    by c0lo (156) on Sunday March 16 2014, @03:03AM (#17111)

    "Steal" in quotes of course. For string libraries? I'd seek out the best Free/Open source or find out what happens when I link against a black-box proprietary lib.

    a comparison [sourceforge.net] between string libraries.
    bstring seems to be GPL/BSD double licensed, you'd be able to fork under whichever you like.

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

  • (Score: 1) by smaug9 on Sunday March 16 2014, @09:50AM

    by smaug9 (96) on Sunday March 16 2014, @09:50AM (#17173)

    Yeah, bstr is nice. Better to not fork. Wrap it in the interface you like, but leave the library itself alone. Maybe writing the one or two missing features you are looking for, but otherwise reusing existing work.