Re: Bahamut ircd
As far as I'm aware it's a compiler oversite. The warning comes
when an implicit cast from integer to pointer is found that the
compiler doesn't know is OK, because Alpha's have 64 bit pointers
and 32 bit integers. The warnings should go away by sticking
an explicit cast at every place that you get a warning, but the
object code should be identical to that produced before. (As far
as I'm aware.)
M Campbell wrote:
> Well, it definitely caused a problem in this case? And there are a
> lot more of these in this code
> I don't know anything about C, but I wouldn't
> mind trying to clean up the specific warnings that I get on compile.
> Is this pretty basic stuff, or should I try to bug someone who knows C
> to do it? Any resources or hints about things to look for?
> On Mon, Mar 10, 2003 at 02:41:20AM +0100, Falk Hueffner wrote:
> > firstname.lastname@example.org writes:
> > > My 2?: It's the very rare source code that compiles without that
> > > "cast from integer to pointer of different size" warning. I quit
> > > worrying about it many years ago.
> > It can be harmless in some cases, but it is certainly not a warning
> > that should be ignored, and it is usually easy to fix.
> > --
> > Falk