lkml.org 
[lkml]   [1998]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: include file conflict
Theodore Y. Ts'o writes:
> P.S. I prefer to use linux/foo.h for the public interface, and
> linux/fooP.h for the kernel-private information; hence
> linux/serial.h and linux/serialP.h. Other people like to use
> linux/foo_i.h for the publically exported interface. This is just a
> matter of taste, but it seems nicer to me to reserve the "uglier"
> name for the internal header file, and to use the "nicer" name for
> the public header file.

I agree. Also, using fooP.h for private headers follows the Xt
convention, so it makes it just that little more obvious to the Xt
hackers out there.

Regards,

Richard....

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:45    [W:0.067 / U:0.624 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site