C functions without header files

Question

This should be very trivial. I was running through a very basic C program for comparing strings:

#include <stdio.h>  
int strcmp(char *s, char *t);
int main()
{
    printf("Returned: %d\n", strcmp("abc", "adf"));
    return 0;
}

int strcmp(char *s, char *t)
{
    printf("Blah\n");
    while (*s++ == *t++)
    {
        if (*s == '\0')
            return 0;
    }
    return *s - *t;
}

So I've basically implemented my own version of the strcmp function already present in string.h. When I run the above code, I only see return values of 0, 1, or -1 (at least for my small set of test cases) instead of the actual expected results. Now I do realize that this is because the code doesn't go to my implemented version of strcmp, but instead uses the string.h version of the function, but I'm confused as to why this is the case even when I haven't included the appropriate header file.

Also, seeing how it does use the header file version, shouldn't I be getting a 'multiple implementations' error (or something along those lines) when compiling the code?

your last test `*s++ == *t++` which could fail will still increment your pointers… is that what you want? — Benoit, May 08 '11 at 08:03
Yep, you're right. That last line should be return *(--s) - *(--t) — M.K., May 08 '11 at 18:22

score 15 · Accepted Answer · answered May 08 '11 at 06:50

You're using gcc, right? gcc implements some functions as built-ins in the compiler and it seems that strcmp is one of those. Try compiling your file with the -fno-builtin switch.

Header files just tell the compiler that certain symbols, macros, and types exist. Including or not including a header file won't have any effect on where functions come from, that's the linker's job. If gcc was pulling strcmp out of libc then you probably would see a warning.

and BTW "mu is too short" is way too long :) – MByD May 08 '11 at 07:07 — MByD, May 08 '11 at 07:07

score 6 · Answer 2 · answered May 08 '11 at 07:19

Not as elegant as the earlier answers, another way to get this done

#include <stdio.h>  
static int strcmp(char *s, char *t); /* static makes it bind to file local sym */
int main()
{
    printf("Returned: %d\n", strcmp("abc", "adf"));
    return 0;
}

int strcmp(char *s, char *t)
{
    printf("Blah\n");
    while (*s++ == *t++)
    {
        if (*s == '\0')
            return 0;
    }
    return *s - *t;
}

score 1 · Answer 3 · answered May 08 '11 at 06:51

1

Without knowing what compiler and lib. version you use, all conclusion are only 'possibility'. So the most reasonable thing that stdio.h already includes stdlib.h or string.h

answered May 08 '11 at 06:51

Dewfy

23,277
13
73
121

score 0 · Answer 4 · answered May 08 '11 at 08:00

0

strcmp is the name of a standard library function. As such you are only permitted to declare the function (although you must use a correct declaration); you are not permitted to provide another definition for it. The implementation can assume that whenever you use strcmp you are referring to the standard library function even if you haven't used the correct #include for it.

If you want to provide an alternative strcmp then you should give it an alternative name.

answered May 08 '11 at 08:00

CB Bailey

755,051
104
632
656

I can provide redefinition of most library functions. Most of them are declared weak in glibc; also, standard says only about definition in the header. If no header is included, there is no any "library function" and I can declare anything, even the `y0()` or define somthing in non-standard way, e.g. `double strcmp(int, float*)`. Many implementations allow user to turn off the assumption about standard library (`-fno-builtin` or `-ffreestanding`). Standard says about library in "Hosted environment" (`conforming hosted implementation`), but there is a `conforming freestanding implementation`. – osgx Jul 21 '11 at 08:55

C functions without header files

4 Answers4