From: Thomas M. <tma...@ze...> - 2000-10-24 21:57:03
|
Well, I finally finished my project files for Windows. On our (probably my :) TODO list is documentation for using SOMELib on Windows. There's a few tricks involved. You may notice the addition of some_string_map.h in SOMELib. This was necessary due to the way windows does its dll's and the fact that std::map uses a static pointer called Nil for keeping track of things. This static would apparently get created both in the app and the dll, then when the map was modified by the dll in the initSOMELibInfo function it would have a different address than the exe. Essentially it became fubar. The solution was to write my own map, which was surprisingly easy. Only a few real lines of code. This change has been ifdef'ed for windows only and the API remains the same. The Makefile situation needs some real work, too bad the Software Carpentry solution is still on the horizon. I have as yet been unable to get the makefiles to work. Also, the SOMELib, TestApp, and BasicTestLib Makefiles are missing. If you could put those in Quintecent, I would appreciate it. So what else do we need to do before we can go 1.0? Docs, Docs, Docs: 1) Finish out API documentation 2) I'd like to get a homepage put on the sourceforge site 3) Doxygen also generates latex, man, and rtf formats, should I add those to CVS? 4) Tutorials Code: 1) Formatting. I was going to run astyle on it. Are you CoreLinux++ guys using a pretty printer? 2) Spell check. 3) Name analysis. Are these the names we want for our classes 4) Namespaces. Pretty please :) 5) Error conditions. Currently a few exceptions. Do we like this? 6) Write the searchForLib func. 7) Do we want a getAllLibsInThisDirectory type function? Examples: 1) Like what you did there Quinticent, do we need more? Lets try and think of other tricks people might want to do with this. What did I miss? Should we make a beta dist next week and make a freshmeat posting? -- Thomas O Matelich Senior Software Designer Zetec, Inc. sos...@us... tma...@ze... |