Hi!
What happens though when it is a class that you then decide to expose
for folks extending the server? Do we rename classes then?
Personally I prefer to keep naming conventions such that if we change
our minds in the future, we don't have to go around renaming everything.
Cheers,
-Brian
On Dec 9, 2008, at 9:22 AM, 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...
Cheers,
jay
Brian Aker wrote:
On Dec 9, 2008, at 9:08 AM, Jay Pipes wrote:
#include <libmemcached/string.h>
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
