inappropriate "initialization makes pointer from integer without a cast" warning

[MK27]

I think I've seen something like this before and someone had an explanation:

#include <time.h>
#include <stdio.h>

int main() {
	struct tm *data = getdate("1/1/2010 12 AM");
	return 0;
}

time_convert.c:5: warning: initialization makes pointer from integer without a cast

From /usr/include/time.h:

extern struct tm *getdate (__const char *__string);

[EVOEx]

You mean that error occurs if you don't include time.h? In that case, I can explain it (since it's assumed to return an integer since the function isn't declared). Otherwise, I'm not too sure.

[MK27]

You mean that error occurs if you don't include time.h? In that case, I can explain it (since it's assumed to return an integer since the function isn't declared). Otherwise, I'm not too sure.

I would expect it to happen if I don't include time.h, which is why I highlighted the fact that I did include it

[EVOEx]

Ah. You'll have to do "#define _XOPEN_SOURCE 500" before including time.h. I'm not sure why this is, though... It's a design choice of the makers of the header files. So there must be a good reason.

[MK27]

Ah. You'll have to do "#define _XOPEN_SOURCE 500" before including time.h. I'm not sure why this is, though... It's a design choice of the makers of the header files. So there must be a good reason.

That solves the problem, thanks. But what a function this turns out to be:

Variable: getdate_err

This variable of type int contains the error code of the last unsuccessful call to getdate. Defined values are:

1
The environment variable DATEMSK is not defined or null.

[...]

The interface to getdate is the simplest possible for a function to parse a string and return the value. string is the input string and the result is returned in a statically-allocated variable.

The details about how the string is processed are hidden from the user. In fact, they can be outside the control of the program. Which formats are recognized is controlled by the file named by the environment variable DATEMSK. This file should contain lines of valid format strings which could be passed to strptime.

So now I have to create some global system file and set an env variable in order to use "the simplest possible for a function to parse a string and return the value"? Grrr...I think I'm going back to the "tricky low level" funcs.

[EVOEx]

Maybe you could use strptime? Not sure if that's better, though. And it needs _XOPEN_SOURCE as well (apparently this is for UNIX compatibility or so...).

[MK27]

Maybe you could use strptime? Not sure if that's better, though. And it needs _XOPEN_SOURCE as well (apparently this is for UNIX compatibility or so...).

Yeah. Like, OMG:

	struct tm data;
	strptime("1/1/10 12 AM", "%D %I %p", &data);

That is too crazy. [Sarcasm] Somebody better write a more user friendly function, like "getdate".