Greetings. Back in October, there was a discussion on the System.FilePath module that's currently the hidden module Distribution.Compat.FilePath in Cabal: http://www.haskell.org/pipermail/libraries/2004-October/002591.html It was decided that we should not include it as System.FilePath because it was insufficiently consistent, had some confusing corner cases, and some folks felt that FilePath should be an abstract type. A number of people would like to use the FilePath module as it is, and someone has even packaged it up separately, so I think we should move forward in building a module that performs this task. For those who objected at the time, can someone put together a list of requirements for the FilePath module you believe we need? (Perhaps on the Wiki?) FWIW, the module we have is very similar to the SML and Python modules which perform this task, and most likely very similar to other languages' modules. In short, I think this approach works in practice, but not in theory, as Lemmih said on IRC ;) peace, isaac
In particular I am happy with the current module. It isn't perfect but
it performs much better than many other path manipulation functions
which I have seen in various Haskell tools. I am waiting to see better
approach from people which are feeling uncomfortable with
System.FilePath.
Cheers,
Krasimir
On 7/7/05, Isaac Jones
Greetings.
Back in October, there was a discussion on the System.FilePath module that's currently the hidden module Distribution.Compat.FilePath in Cabal:
http://www.haskell.org/pipermail/libraries/2004-October/002591.html
It was decided that we should not include it as System.FilePath because it was insufficiently consistent, had some confusing corner cases, and some folks felt that FilePath should be an abstract type.
A number of people would like to use the FilePath module as it is, and someone has even packaged it up separately, so I think we should move forward in building a module that performs this task.
For those who objected at the time, can someone put together a list of requirements for the FilePath module you believe we need? (Perhaps on the Wiki?)
FWIW, the module we have is very similar to the SML and Python modules which perform this task, and most likely very similar to other languages' modules. In short, I think this approach works in practice, but not in theory, as Lemmih said on IRC ;)
peace,
isaac _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
Isaac Jones writes:
For those who objected at the time, can someone put together a list of requirements for the FilePath module you believe we need?
As one of those who objected back then, let me say that I've arrived at the conclusion that the module is fine the way it is for now. I would like an abstract data type plus a set of operations to manipulate paths better, but my motivation is that I'd like to have a module for expressing and handling namespaces in general -- not just filesystem paths. That's a more difficult problem, though, so the lack of a solution for that shouldn't hinder a solution for manipulating file system paths to be implemented. Peter
participants (3)
-
Isaac Jones -
Krasimir Angelov -
Peter Simons