Hi all, I have been meaning to port the Haskell FilePath library to Chicken, because I find its API to be quite elegant and better organized than the existing file name manipulation routines in Chicken. This discussion has prompted me to create the filepath egg, which is an almost verbatim transliteration of the Haskell code, with a few Chicken-specific idioms here and there. I have included a flag parameter, which can be used to enable "Posix" mode or "Windows" mode for path name parsing and manipulation. The Windows mode supports weird things like UNC names and is aware of the DOS reserved names (CON, PRN, etc). I would appreciate it if people look at it, as I would like to see some variant of this API supersede the existing Chicken path manipulation stuff.
-Ivan Vincent Manis <[EMAIL PROTECTED]> writes: > I strongly disagree with this particular recommendation. Sometimes I > have code running on Unix that manipulates Windows file names > (thanks to VirtualBox, that's something I want to do more often, > these days). I recommend a design that has a flag with settings such > as `this is a Windows name', `this is a Unix name', and a default > setting of `this is a name for the OS I'm currently on', which can > certainly work the way Peter suggests. _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
