From: Vikas S. <vik...@gm...> - 2010-05-29 16:53:25
|
Hello On Sat, May 29, 2010 at 7:42 AM, Brendan Luchen <bm...@ri...> wrote: > > > 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. > > My problem was to consider libt4k-common for my code or not. So , as David pointed out that it would be better to go without considering libt4k-admin I also decide to go with that. > >If I Recall Correctly, Vikas, you're working on the admin tool? My work will aslo involves changes in Tuxmath and Tuxtype. > 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. Yes, that will be fine. -- Regards , Vikas Singh |