Thread: Help with writing a function

okay, let make some example between 2 statements to save ppl's name :

[1] scanf ("%[^\n]", variable);

and

[2] getchar (variable);

----

so what's a deal between 2 of them? some of ppl said using scanf concept is more faster than the getchar.

in my mind, assume that user entered the input name as "rock rolly", so the scanf should be scan every char of the variable and store into the variable until it meet the newline command ('\n').

compare this ...

getchar could take the whole chars of the variable and directly save it to the variable (it don't care anythings in it, eg : blank space, special char ...)

so, how's the conclusion?

Originally posted by stallion
well, i was suggesting this because we all should be striving for the best and fastest possible code.

nope nope nope nope nope. my favorite book on C explains a very logical rationale: above all make your code easy to read, easy to maintain, logical, well orgainized, well commented. only sacrifice that in extreme cases of critical loops that are repeated 2502480438340438034348 times per second or similar. the reasoning behind this is, in part:
1. through various black magic cleanly written code can often run a bit faster than hacked-up crap for no clear reason at all (really).
2. the 20/80 theory that 20% of your code takes up 80% of your time, so only making sacrifices in readability and maintainability in that 20% will optimize things all you need.

Originally posted by moi
nope nope nope nope nope. my favorite book on C explains a very logical rationale: above all make your code easy to read, easy to maintain, logical, well orgainized, well commented. only sacrifice that in extreme cases of critical loops that are repeated 2502480438340438034348 times per second or similar. the reasoning behind

I couldn't agree more. Readability is the key. No one wants to read fugly code. Which is why when I "do peoples homework for them", it's macroed to hell and back and is a nightmare to read...

Quzah.