Re: Header File cleanup.
От | The Hermit Hacker |
---|---|
Тема | Re: Header File cleanup. |
Дата | |
Msg-id | Pine.BSF.4.21.0005291900300.608-100000@thelab.hub.org обсуждение исходный текст |
Ответ на | Header File cleanup. (Lamar Owen <lamar.owen@wgcr.org>) |
Ответы |
Re: Header File cleanup.
|
Список | pgsql-hackers |
I'll give you a different source to read ... the archives :) This one has been bounced back and forth a few times already, with *at least* twice that I can think of where to even shifted from one to the other and back again *roll eyes* On Mon, 29 May 2000, Lamar Owen wrote: > Enlighten me: > > Why use #include "header.h" over #include <header.h> for exported interface > header files? I've read the man and info page, and understand the differences > from a C preprocessor standpoint, so, suggestions to read those sources will be > piped to /dev/null -- I'm looking for why _we_ do it one way over the other. > > The reason I am asking is to see if anyone using the RPM's have had problems > #include'ing our headers.... but, as well, to see just what the advantages of > "" over <> are for our exported headers. > > -- > Lamar Owen > WGCR Internet Radio > 1 Peter 4:11 > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
В списке pgsql-hackers по дате отправления: