From: Brendan L. <bm...@ri...> - 2010-05-29 02:12:39
|
Vikas, There are a few (not too many) file-operations routines in t4kcommon, e.g. int CheckFile(const char* file) char* find_file(const char* base_name) SDL_Surface* LoadImage(const char* file_name, int mode) By conflicts, do you mean name clashes, or duplication, or something else? I'm thinking of adding a prefix to all routines, e.g. T4K_CheckFile() to avoid naming conflicts until later in the summer, when it's time to permanently switch over TuxMath and TuxType to use the library instead of internal implementations. Then, it will be a choice between adding the T4K_ prefix to all function calls (ouch) or using macros to patch things up. But that's mostly my problem. If I Recall Correctly, Vikas, you're working on the admin tool? If so then I expect there will not be *too much* overlap between what you're writing and what is already in libt4kcommon. I will try to keep an eye on your stuff, and when it is almost complete, I think we should then move it into the library. You might have more "fun" with syncing your code between TuxMath and TuxType while you're developing it. Any ideas? Best, Brendan |