> What do other people feel? Should signed/unsigned conversions be
> avoided in new code? Should these be eliminated in 2.2? Will patches
> towards that goal be accepted if all they do is clean up error
> messages?
Signed/unsigned comparisions should (nearly) _always_ be avoided. It's a
symptom of inconsistancy/sloppy typedefs in the code. If it doesn't bite
you today, it might bite you tomorrow on a different architecture.
0.02c's worth
Mark
---------------------------------------------------------------------------
Mark Cooke The views expressed above are mine and are not
Systems Programmer necessarily representative of university policy
University Of Birmingham URL: http://www.sr.bham.ac.uk/~mpc/
---------------------------------------------------------------------------