FreeTDS Development Group

["Craig A. Berry" <craigberry AT mac.com>]

At 2:09 PM -0500 12/20/05, Lowden, James K wrote:
>
>I also think it's a good idea to have include files in one place and
>source in another, if the include is to be shared.  If the include is
>not to be used elsewhere -- i.e. the .h file is only for one file or for
>files in only one directory -- then it should stay with the files(s) and
>
>
>       #include "foo.h"
>
>will work fine. 
>
>In our case, rather than:
>
>       $ mv src/replacements/readpassphrase.h \
>               include/tds_readpassphrase.h
>
>I prefer:
>
>       $ mkdir include/replacements
>       $ mv src/replacements/readpassphrase.h \
>               include/replacements
>and
>       #include <replacements/readpassphrase.h>
>
>because it makes clear that our readpassphrase is a replacement, not a
>specialized enhancement.  Also, it has appealing parallelism:
>
>       src/replacements/*.c
>       include/replacements/*.h
>
>How does that sound? 

That sounds great.  And it has the added advantage of not changing
anything inside readpassphrase.c so upgrades will be simpler.  Thanks for
the replies.
-- 
________________________________________
Craig A. Berry
mailto:craigberry AT mac.com

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser