Ivan Lazar Miljenovic schrieb:
We considered giving it a new name (fgl', etc.) but figured that in the
long term this wouldn't be advantagous. We feel that the situation is
analogous to QuickCheck: when the new version came out most people kept
using the old one until slowly the momentum
Christian Maeder christian.mae...@dfki.de writes:
Ivan Lazar Miljenovic schrieb:
We considered giving it a new name (fgl', etc.) but figured that in the
long term this wouldn't be advantagous. We feel that the situation is
analogous to QuickCheck: when the new version came out most people
Ivan Lazar Miljenovic schrieb:
[...]
we don't need to repeat a parsec-2 vs parsec-3 discussion.
There are obviously different opinions that cannot be easily changed.
Well, I've created a custom instance:
http://trac.informatik.uni-bremen.de:8080/hets/browser/trunk/Common/Lib/Graph.hs
and our
Ivan Lazar Miljenovic schrieb:
Although parsec-3 can be used as an replacement for parsec-2 it would
have been better, they had different names (as argued elsewhere for the
haskell platform).
I'm sorry, I don't recall this discussion: care to summarise?
Christian Maeder christian.mae...@dfki.de writes:
Ivan Lazar Miljenovic schrieb:
Although parsec-3 can be used as an replacement for parsec-2 it would
have been better, they had different names (as argued elsewhere for the
haskell platform).
I'm sorry, I don't recall this discussion: care
ivan.miljenovic:
Christian Maeder christian.mae...@dfki.de writes:
Ivan Lazar Miljenovic schrieb:
Although parsec-3 can be used as an replacement for parsec-2 it would
have been better, they had different names (as argued elsewhere for the
haskell platform).
I'm sorry, I don't
Hey Robby,
Yeah, two documents:
The PVP
http://www.haskell.org/haskellwiki/Package_versioning_policy
The Package Addition Policy for the Haskell Platform
http://trac.haskell.org/haskell-platform/wiki/AddingPackages
robby:
Hi all. Just thought I'd poke my head in here
