Lee Bieber wrote:
I was just talking with Brian about this and he suggested I open this up
to the mailing list. I'm currently pulling out functions from
drizzled/item.cc/.h and moving them into the drizzled/item directory.
For all Item_* routines, I create a .cc and .h file using the last part
of the name, for example, Item_decimal now is split into
drizzled/item/decimal.cc and drizzled/item/decimal.h. Works
great....most of the time. What about Item_float, doesn't work to have
float.h as the compiler picks up the system float.h instead of the
intended float.h Brian suggested for these conflicts name them
ifloat.h, istring.h when there is a conflict. Anyone else have a better
suggestion or method to deal with system naming conflicts??
The compiler should not pick up any conficts if the file is
referenced/included properly.
Using #include <file.h> specifies a system file.
Using #include "file.h" specifies a user included file.
Although the implementation of search paths is technically left up to
the compiler, the general rule is that using the "" method searches in
the current directory, then to directories including that file, then the
-I directories, then system include directories. The opposite is
generally true for the <> method.
So, why wouldn't we name the files drizzled/item/float.h and reference
it as so:
#include "drizzled/item/float.h"
Compilers should not be confused by this, AFAIK.
-jay
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
