Re: More compilation fixes for Camel

Instead of this cast-o-rama, have you investigated whether it would be
simpler and more correct to change the prototypes of the affected
functions instead (changing signedness or constness of char * parameters
as appropriate), and/or changing signedness/constness of the affected
char* variables? 

Maybe then the need for casts all over the place to avoid warnings would
diminish drastically?

--tml