Monty Taylor wrote:
Jay Pipes wrote:
Right. If it was included as:
#include "libmemcached/string.h"
I don't believe there would be any conflicts.
This might be bikesheddy stuff, but I'm in favor of not prefixing
filenames with "i" or "f" or stuff like that if there is a solution of
just using the proper #include directive...
I think this is important to work on - given the other cleanup we're doing.
I know we had to prefix decimal.h with f in the field split - but I'm
not sure _why_. I think it was before we went to prefixing all includes
with full paths.
In fact - I just checked, and in fact, moving drizzled/field/fdecimal.h
drizzled/field/decimal.h works.
So...
My vote is for drizzled/item/string.h ... and if that breaks something,
lets try to figure that out.
+1.
-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
