🚀 go-pugleaf

In article <1992Oct29.195546.1@vax1.bham.ac.uk> mccauleyba@vax1.bham.ac.uk writes:
| There is another point that follows from all this when considering function
| pointers. The current standard does not allow any promotion of function
| pointers but can anyone say definitively if something like...
| 
| int strcmp(const char*,const char*);
| int (*p)(char *,char*) = strcmp;
| 
| ... could be safely allowed.
| 
| I can see no hazard in permitting conversion from (*)(const T*) to (*)(T*)
| but then I hadn't seen the danger of converting T** to const T**.

I've been wondering about a similar question.  Is there any danger of
allowing the "usual" conversions of pointers and references in parameter
types of function pointers?  Example:

    void f( int (*)(const void*, const void*) );

    int g(const char*, const char*);

    f( g );                                       // error
    f (int (*)(const void*, const void*) g );     // fine

If the usual T* ==> void* conversion were allowed for function pointer
parameters, no cast would be required when calling f with g.  Is there a
lurking danger here?

Scott

-------------------------------------------------------------------------------
What do you say to a convicted felon in Providence?  "Hello, Mr. Mayor."