On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote: > ... > >>- u_char **bufp; > >>+ caddr_t *bufp; > ... > Of course. Very often in ilmid.c the type caddr_t was used, and nearly > the same count of 'const char *'s was used. I've searched the include > files for caddr_t (core address) and found it defined as 'char *', so I > decided to used commonly caddr_t - maybe later I check which of them > could be changed into 'c_caddr_t' for being const. But You can of couse > replace all 'caddr_t' which 'char *'.
Shouldn't we care about u_char vs char? On some machines it matters, and on all machines compilers tend to notice and generate warnings. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
