warning: assignment makes pointer from integer without a cast

[drhowarddrfine]

warning: assignment makes pointer from integer without a cast

I get that when I compile a C file where the function is defined as this:
char **getvars()

and the calling function has this declared:
char **s;

and I write:
s=getvars();

What am I forgetting?

[drhowarddrfine]

Never mind. getvars() wasn't in my prototypes and that was the cause.

[drhowarddrfine]

I'm back. I'm getting the error again and it seems inconsistent. Yes, I'm changing things in the body of the code but sometimes this warnings pops up and other times it doesn't. Anyone see anything I'm missing?

[drhowarddrfine]

Ok, I found out there was another include file I forgot to include and now it's solved.

[Savage]

Ok, I found out there was another include file I forgot to include and now it's solved.

Are u OK?

Do u have temperature?

Savage

[AdrianH]

Are u OK?

Do u have temperature?

Savage

I think the dr. needs a Doctor. :D dr., you should know better then to post a question with not enough info to solve it. ;) Might have to tell Mary on you.


Adrian

[JosAH]

As a rule of thumb: when the compiler complains about a cast you know that
there was no prototype in scope which usually means that you forgot to mention
an include file; especially when the element (function) wasn't yours.

kind regards,

Jos

[drhowarddrfine]

Yeah, I don't have problems with pointers but the pointer to pointer syntax is what I thought was screwed up. I did have that messed up, too, as it turned out but it works now.

We don't have these problems in assembly language. Everything should be done in assembly.

[AdrianH]

Yeah, I don't have problems with pointers but the pointer to pointer syntax is what I thought was screwed up. I did have that messed up, too, as it turned out but it works now.

We don't have these problems in assembly language. Everything should be done in assembly.

LOL, yeah. I think I would rather die from a thousand cuts.


Adrian

[Savage]

Yeah, I don't have problems with pointers but the pointer to pointer syntax is what I thought was screwed up. I did have that messed up, too, as it turned out but it works now.

We don't have these problems in assembly language. Everything should be done in assembly.

No thank u.

I will rather mess up with pointer to pointer syntax.

Savage

[eglantine]

Hello,

I got the same warning using strrch() function:
compileing with GNU gcc 3.3.2 the following code:

# include <stdio.h>
#include <math.h>
:
{
char line[1000];
char comment=';';
int c0;
:
c0=strrchr(line,comment);
:
}

What can be the reason?

Thank you ;)))