[LispM-Hackers] Compile warnings

[James A. Crippen]

JM, I just finished compiling my brand new error code and I'm seeing
*scads* of compile warnings from mainops.cc and memobj.cc.  In particular
I see a lot of things like:

memobj.cc: In method `void memFEFHeader::dump(class ostream &) const':
memobj.cc:1168: warning: passing `e3Boolean' chooses `int' over `long unsigned int'
memobj.cc:1168: warning:   in call to `ostream::operator <<(int)'
memobj.cc:1168: warning: passing `e3Boolean' chooses `int' over `long int'
memobj.cc:1168: warning:   in call to `ostream::operator <<(int)'
memobj.cc:1168: warning: passing `e3Boolean' chooses `int' over `unsigned int'
memobj.cc:1168: warning:   in call to `ostream::operator <<(int)'
memobj.cc:1182: warning: passing `e3Boolean' chooses `int' over `long unsigned i

and like:

mainops.cc: In function `static int e3MacroOpTemplateClass<127>::disassemble<127>(class e3MacroOpCodeEngine *)':
mainops.cc:255: warning: passing `e3DefOp' chooses `int' over `long unsigned int'
mainops.cc:255: warning:   in call to `ostream::operator <<(int)'
mainops.cc:255: warning: passing `e3DefOp' chooses `int' over `long int'
mainops.cc:255: warning:   in call to `ostream::operator <<(int)'
mainops.cc:255: warning: passing `e3DefOp' chooses `int' over `unsigned int'
mainops.cc:255: warning:   in call to `ostream::operator <<(int)'

So do you have any clue why these are happening?  I don't want to go beat
on them if there's a reason for their existence.  But it does make it
annoying to compile and watch all these errors spit out, one for each and
every single line in a source file...

tnx
'james


-- 
James A. Crippen <james@unlambda.com> ,-./-.  Anchorage, Alaska,
Lambda Unlimited: Recursion 'R' Us   |  |/  | USA, 61.2069 N, 149.766 W,
Y = \f.(\x.f(xx)) (\x.f(xx))         |  |\  | Earth, Sol System,
Y(F) = F(Y(F))                        \_,-_/  Milky Way.