In regard to: Re: ltdl.c and 1.4.1 (type conflicts), Gary V. Vaughan said...:
>Except that the function argument takes an lt_ptr which it passes
>through to a callback function. Sometimes it is a pointer to a
>structure that the callback uses, other times it is a pointer to a
>function. Creating two identical functions, but for whether they pass
>through a pointer to a function or a pointer to something else is not
>a good idea... I really think that the warning from xlc is
>misconceived.
Except it's not just xlc, it's Sun's Forte 6.1, recent versions of the
Tru64 UNIX C compiler, HP-UX 10.20's ANSI C compiler, and possibly others.
Even gcc 3.x can be made to warn about it. ;-)
None of them error out on it, but they all warn that it's "against the
standard". Maybe that's changed with C9X, so it's no longer a problem --
I don't know.
In any case, since no one has pointed out a compiler that won't accept this,
it's probably not worth worrying about at this point.
>Indeed. But K&R vs. ANSI is not the reason for this problem. Anyway,
>supporting K&R is really not at all difficult, so I have no problem at
>all with doing it.
As long as it's not a problem for you, great! Hopefully it never becomes
an issue.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
