libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ltdl.c and 1.4.1 (type conflicts)


From: Gary V. Vaughan
Subject: Re: ltdl.c and 1.4.1 (type conflicts)
Date: Sat, 8 Sep 2001 04:31:33 +0100
User-agent: Mutt/1.3.21i

On Fri, Sep 07, 2001 at 02:45:11PM -0500, Tim Mooney wrote:
> In regard to: Re: ltdl.c and 1.4.1 (type conflicts), address@hidden:
> 
> >On Fri, Sep 07, 2001 at 12:43:31AM +0100, Gary V. Vaughan wrote:
> >> On Wed, Sep 05, 2001 at 09:52:10PM -0500, address@hidden wrote:
> >> >
> >> > Harder to fix is:
> >> > "ltdl.c", line 3204.58: 1506-280 (E) Function argument assignment
> >> > between types "void*" and "int(*)(const char*,void*)" is not allowed.
> >>
> >> Oh yuck!  Are there any mode switches to xlc to have it accept this
> >> ideom?
> >
> >AIX does accept it. However, ltdl.c is treating pointers and pointers
> >to functions the same (hence my statement that it makes liberal use of
> >pointers).
> 
> As Albert can probably verify, most of the other vendor compilers also warn
> about this very problem, but all the ones I've seen accept it grudgingly
> (i.e. it's not an error).

Phew!  Thanks for that info.

I'm open to suggestions for a cleaner way to implement this, but I
think that it is an unavoidable weakness in C that forces one to (ab)use
void* in cases such as this.

Cheers,
        Gary.
-- 
  ())_. Gary V. Vaughan     gary@(oranda.demon.co.uk|gnu.org)
  ( '/  Research Scientist  http://www.oranda.demon.co.uk       ,_())____
  / )=  GNU Hacker          http://www.gnu.org/software/libtool  \'      `&
`(_~)_  Tech' Author        http://sources.redhat.com/autobook   =`---d__/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]