Re: [Somelib] SOME::Path changed - RegEx and BSD compile fix are next

[Thomas M. <tma...@ze...>]

John Palmieri wrote:

> Hope you have had a good Thanksgiving.

Very good, thanks.

> 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.

opendir, closedir, etc. are not available on Winders.  So these will have
to remain seperate.  I changed all of them to use stat for checking whether
its a dir because it seemed faster than what you were doing previously.

> 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.

I think if we used boost::regex we would have to leave it with their
license (as must our modified use of that code).  If you have experience
with that simple matching, then I would just go ahead and write it, rather
than try and modify regex for our use.

> --Quinticent

--
Thomas O Matelich
Senior Software Designer
Zetec, Inc.
sos...@us...
tma...@ze...