| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Conflicting Types Between .h and .c files |
| From: | Danny Cox <DCox@xxxxxxxxxxxxxx> |
| Date: | Mon, 19 Aug 2002 14:52:08 -0400 |
| Cc: | XFS Mailing List <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <20020819194735.A32101@xxxxxxxxxxxxx> |
| References: | <1029504550.1808.5.camel@wiley> <20020819194735.A32101@xxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Christoph,
On Mon, 2002-08-19 at 14:47, Christoph Hellwig wrote:
> > while the .c file sez its:
> >
> > kmem_zone_t *<grump>;
> >
> > While I know it's the same thing, the compiler (2.96 from RH) apparently
>
> I don't think that's valid. And at least gcc 3.2 doesn't complain..
Yes, but 2.96 does. I'd think that several folks use 2.96, since
that's the standard gcc from RH 7.2.
> In this case not, as the kmem_zone_t is an object opaque to it's user.
> Compare it to kmem_cache_t in þhe core Linux code.
Okay, point taken. Nevertheless, the types between the .c and .h files
should be consistent, whatever is chosen, no?
--
kernel, n.: A part of an operating system that preserves the
medieval traditions of sorcery and black art.
Danny
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Conflicting Types Between .h and .c files, Christoph Hellwig |
|---|---|
| Next by Date: | grub and root partition with external log, Christian Rice |
| Previous by Thread: | Re: Conflicting Types Between .h and .c files, Christoph Hellwig |
| Next by Thread: | Re: Conflicting Types Between .h and .c files, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |