Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 201 Vote(s) - 3.37 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Why does having an `int (*)(float)` point to an `int foo()` trigger a warning, but having an `int (*)(double)` point to it doesn't?

#1
I have this piece of code:

```c
int foo() { return 0; }
int main()
{
int (*float_function)(float) = foo;
}
```

When compiled using `x86-64 GCC 12.2`, with `-Wall`, it produces the warning ([Link](

[To see links please register here]

)):

> warning: initialization of 'int (\*)(float)' from incompatible pointer type 'int (\*)()' [-Wincompatible-pointer-types]

But, when I change from `float` to `double` ([Link](

[To see links please register here]

)):

```c
int foo(){ return 0;}
int main()
{
int (*double_function)(double) = foo;
}
```

The warning is now gone.

But I think that both of these should get a warning.

Am I wrong somewhere? Why does GCC not complain about the second example?
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through