chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] Bug in canonical-path?


From: Elf
Subject: Re: [Chicken-users] Bug in canonical-path?
Date: Wed, 29 Oct 2008 13:07:31 -0700 (PDT)

On Wed, 29 Oct 2008, Peter Bex wrote:

On Wed, Oct 29, 2008 at 11:03:30AM +0100, felix winkelmann wrote:
On Wed, Oct 29, 2008 at 9:04 AM, Ivan Raikov <address@hidden> wrote:

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.


That library looks useful - nice port, Ivan.

I would keep these things in extensions, though. There is already too much
stuff in the core (I know I keep repeating this, but I'm really concerned about
it).

I think Ivan is not suggesting _adding_ this to core, but rather
_replacing_ what we have in core with this.  In total, this should
have the net effect of adding nothing (though I don't know how big
both libraries are).



filepath is fairly large.  canonical-path and friends, together, are tiny.
they are not addressing the same set of issues, regardless.

again: canonical-path does not do existence checking. it is not meant to. it is intended to create localised canonical forms of a path in any representation as an aid to installation and naming portability.

-elf





reply via email to

[Prev in Thread] Current Thread [Next in Thread]