Date: Sun, 02 Mar 2003 13:53:13 +0100 From: Jens Rehsack <rehsack@liwing.de> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Juli Mallett <jmallett@FreeBSD.org>, current@freebsd.org Subject: Re: PATCH: type errors in src-tree Message-ID: <3E61FEB9.2020102@liwing.de> References: <3E5EA13E.9020208@liwing.de> <3E60F1CF.2030400@liwing.de> <20030301155546.A39174@FreeBSD.org> <3E612F7F.1090002@liwing.de> <xzpel5qc6nj.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav wrote: > Jens Rehsack <rehsack@liwing.de> writes: > >>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 *'. > > > This is wrong. caddr_t should be uniersally replaced with void *. Good to know. I think I have done it where it's possible, and where really (unsigned) char *(*) was required, I've used that. There're some places in code where I'm not sure about it's being correct, but that has nothing to do with char */void *. > DES Jens To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E61FEB9.2020102>