🚀 go-pugleaf

:> :In article <4emato$3rd@solutions.solon.com> makholm@diku.dk (Henning
Makholm) writes:
:> :
:> :   David Robinson <drobin1@po-box.mcgill.ca> writes:
:> :
:> :   >Anyone have any good C interview questions for candidates
:applying
:> :   >for an entry-level programming position?
:> :
:> :   "Do you use gotos when you program?"
:> 
:> That's a good one.
:> 
:> :Here's one:
:> :
:> :       Why is the following code inefficient?
:> :
:> :       #include <string.h>
:> :       #include <stdio.h>
:> :
:> :       char s[] = "abcdefghijklmnopqrstuvwxyz";
:> :       extern int check(char); /* returns 0 or 1 */
:> :       int i;
:> :       for (i = 0; i < strlen(s); i++) {
:> :               if (check(s[i])) {
:> :                       putchar(s[i]);
:> :               }
:> :       }
:> 
Isn't character-at-a-time I/O supposed to be slow?

Assuming the strlen call is optimized out of the loop, I'd say that
calling putchar several times is much slower than building a new
array & passing it to puts (or fputs)  -- at the cost of some memory.

-Tony

P.S. hope I got the quotes right.