From: John P. <jo...@ma...> - 2000-11-27 21:32:43
|
Hope you have had a good Thanksgiving. SOME:Path has changed to Path encapsulating the platform specific code of PathDriver. (Before XPPath was being inherited by platform specific code Path). PathDriver should be duplicated under the HPUX and Windows directory and changed to reflect the platform (ie __IS_DIR back to _IS_DIR). From our last e-mail I got the impression that directory searching is the same on Windows, Linux and HPUX (except for the macro)? Is this true for Windows 9x or just NT (I know NT is somewhat Posix complient for military use). I would like to keep these seperate for different platforms even if they are the same on these three platforms, being that it will make it easyer to port to some esoteric OS that does not support Posix. Am I wrong in stating that opendir, closedir, etc. are not ANSI standards? If they are then the PathDriver is redundant and can be folded into Path. I will beimplementing simple regular expressions for file searching next. I am still not sure about using boost. How are their feelings if we take their code LGPL? I can see using smart pointers but the Regular Expression code is going to be highly modified. Will this meen that under their licence I can not make someone give back code if they modify the RegEx portion of the code? I also feel bad about taking someones code and making it completely open if they wish that people can use it in closed source apps. I havn't looked at it yet and I have a feeling that it is a bit more complicated than we need anyway. All I want is the old dos pattern matching. * for wildcard, ? for 1 char wildcard and the rest literals. --Quinticent |