FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> Sent: October 11, 2002 8:19 AM
> > 
> I'd use a src/win32 directory... with some project file/makefile

I vote No on that suggestion.  

$ ls -l src |grep ^d
drwxr-xr-x  2 jklowden  staff    512 Sep 24 16:30 CVS
drwxr-xr-x  4 jklowden  staff    512 Oct 10 10:28 apps
drwxr-xr-x  5 jklowden  staff    512 Oct 10 10:28 ctlib
drwxr-xr-x  5 jklowden  staff    512 Oct 10 10:28 dblib
drwxr-xr-x  5 jklowden  staff    512 Oct 10 12:40 odbc
drwxr-xr-x  4 jklowden  staff    512 Oct 10 12:41 pool
drwxr-xr-x  4 jklowden  staff    512 Oct 10 10:28 replacements
drwxr-xr-x  4 jklowden  staff    512 Oct 10 10:28 server
drwxr-xr-x  5 jklowden  staff   1024 Oct 10 12:41 tds

The directory structure is organized by library.  The right place to put
Win32 stuff is in the library's directory.  Someone working on dblib can
focus on that directory (and perhaps ../tds), regardless of the OS he's
interested in.  That's equally good for all parties: if you segregate the
Win32 sources, you'll likely break them by ignoring them.  

If you find there's general Win32 stuff you need for all libraries, I'd say
"replacements" is the right location.  If in any directory you find you need
a lot of Win32 stuff, it might be a good idea to have a win32 subdirectory
for it (say, for example, src/dblib/win32).  

If you plop stuff in a src/win32 directory, you'll soon find a mixture of
API support in there, not nice for them who follow.  

--jkl




The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.