Re: [Chicken-users] pathname-extension strikes again

[felix winkelmann]

On 11/4/06, Dan <address@hidden> wrote:
> Hi,
>
> (pathname-extension) sometimes returns #f. string=?
> doesn't like #f as an operand. Every single instance
> of
>
> (string=? ... (pathname-extension ...) ...)
>
> is an error and should be taken out and shot.
> Alternately, pathname-extension should be taken out
> and shot.

I have changed chicken-setup to use "equal?",
but basically you are quite right. I'm reluctant to change
this behaviour, though, as this would introduce too much
compatibility-issues, and I'm right now mainly interested
in getting some stability into chicken.

> Which instances would these be? Today I expose the
> ones in chicken-setup.scm, inside (install-extension).
> Because of those instances, you can't list a directory
> in the install-extension FILELIST component (either by
> itself, or as part of a (SOURCE DEST) pair).

Well, you can list the complete list of files (i.e. including the
full pathname), but I understand this is annoying.

> I seem to remember pathname-extension was at the root
> of some other problem, a long time ago. Why can't it
> just return "" instead of #f? You may think it's
> because "file." and "file" should be treated
> differently. But
>
> (pathname-extension "file.")
>
> also returns #f.

Backwards compatibility, but again: you are quite right.

> -- Dan (pretty frustrated, trying to package an egg)

Sorry for that, but many people will be even more frustrated
when I change the behaviour of "pathname-extension".


cheers,
felix

--
http://galinha.ucpel.tche.br:8081/blog/blog.ssp