[Haskell] PLAN-X 2008 Deadline approaching
Call for Papers and Demos = ** Abstract deadline: Oct. 17, 2007 ** Paper deadline: Oct. 22, 2007 PLAN-X 2008 --- Programming Language Techniques for XML ACM SIGPLAN Workshop colocated with POPL 2008 San Francisco, California, USA - 9 January 2008 http://gemo.futurs.inria.fr/events/PLANX2008/ The PLAN-X 2008 workshop is the forum to present and discuss bleeding-edge research at the intersection of programming language and data base technology with an emphasis on tree-shaped data structures and their XML representation. Topics of interest are all aspects of XML processing and querying: theories, methodologies, paradigms, language designs, types, analyses, runtime aspects, implementations, tools, applications. This edition of PLAN-X is particularly interested in blending the XML processing approaches developed by the programming languages and data management communities. Expressive power and high performance are among the common goals that these communities pursue. We encourage the submission of crosscutting contributions that apply techniques from one community to problems from the other. The primary criteria for paper selection are originality, relevance, and timeliness to ensure that we can enjoy reports on ongoing and unfinished work with high potential in the workshop. Submissions === We seek submissions in two categories * regular papers (10 pages, 30 minutes presentation) * demo papers (4 pages, 10 minutes plenary presentation + 30 minutes slot for individual discussions shared with other demos) For details see the submission instructions on http://gemo.futurs.inria.fr/events/PLANX2008/?page=subm Important Dates === Abstract deadline *** 17 October 2007 Submission deadline *** 22 October 2007 Notification30 November 2007 Final papers due14 December 2007 Program Committee = Veronique Benzaken Université de Paris-Sud 11, France Alin DeutschUniversity of California, San Diego, USA Wenfei Fan University of Edinburgh, UK Mary Fernandez ATT Research, USA Haruo HosoyaUniversity of Tokyo, Japan Ralf Lämmel Universität Koblenz, Germany Sebastian ManethNational ICT and UNSW, Sydney, Australia Jim Melton Oracle Corporation, USA Michael SchwartzbachUniversity of Aarhus, Denmark Jérôme Vouillon CNRS, France Ioana Manolescu (general chair) Gemo group, INRIA Futurs, France Peter Thiemann (program chair) University of Freiburg, Germany ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
[Haskell] pretty-printing Haskell with automatic parens?
The haskell-src package contains a pretty-printer for Haskell syntax that requires parentheses to be explicitly placed in the (abstract) syntax representation. I have some code for automatically inserting parentheses where necessary (for use before pretty-printing), but I'm guessing someone else has done so better than I. Does anyone have pointers? I'm glad to share my version as well. Cheers, - Conal ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Trying to install binary-0.4
- Provide a replacement configuration for GHC 6.6 and 6.4 (yes, that one is still alive!) that removes the conflict between 'base' and 'bytestring' and pretends to provide bytestring, containers, array, etc. People interested in making it easy to use new versions of packages with old compiler releases can make a small script that installs empty Cabal packages called bytestring, containers, array, etc. there are implicit assumptions in most package managers: - unless you ask for a specific package version, any version will do - if you need a minimum feature set, giving a *lower* bound for the package version will do unless you want to keep updating your package spec every time a new version of a dependency comes out, you really do not want to give *upper* bounds on package versions. haskell software frequently violates both assumptions, deprecating features for one or two a minor versions, then abandoning them in the next. but calling "split-base" "base" goes directly against all basic assumptions of all packages depending on "base". i don't know whether the first intel ai should really still be expected to run the original excel code without change, but suggesting that people keep going back to make old software compatible with continuosly changing new assumptions does not sound right at all. claus ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Trying to install binary-0.4
On Oct 14, 2007, at 12:48 , Ian Lynagh wrote: On Sun, Oct 14, 2007 at 05:19:31PM +0200, Udo Stenzel wrote: Ian Lynagh wrote: People interested in making it easy to use new versions of packages with old compiler releases can make a small script that installs empty Cabal packages called bytestring, containers, array, etc. That completely misses the fact that bytestring cannot be upgraded, no matter how many fake packages are available. Ah, you mean the problem is that it really does depend on some change in bytestring (the internal API?), rather than just having a dependency on the bytestring package? I think dons has said that the latest bytestring depends on some GHC 6.8 internals that can't reasonably be backported, so if you need the new bytestring API, you're kinda stuck. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED] electrical and computer engineering, carnegie mellon universityKF8NH ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Trying to install binary-0.4
On Sun, Oct 14, 2007 at 05:19:31PM +0200, Udo Stenzel wrote: > Ian Lynagh wrote: > > People interested in making it easy to use new versions of packages with > > old compiler releases can make a small script that installs empty Cabal > > packages called bytestring, containers, array, etc. > > That completely misses the fact that bytestring cannot be upgraded, no > matter how many fake packages are available. Ah, you mean the problem is that it really does depend on some change in bytestring (the internal API?), rather than just having a dependency on the bytestring package? Then yes, things are not so easy. Part of the motivation for splitting up base is so that this sort of thing is easier in the future. Thanks Ian ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Trying to install binary-0.4
Ian Lynagh wrote: > People interested in making it easy to use new versions of packages with > old compiler releases can make a small script that installs empty Cabal > packages called bytestring, containers, array, etc. That completely misses the fact that bytestring cannot be upgraded, no matter how many fake packages are available. -Udo signature.asc Description: Digital signature ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Trying to install binary-0.4
Hi Udo, On Fri, Oct 12, 2007 at 01:27:11AM +0200, Udo Stenzel wrote: > > - Provide a replacement configuration for GHC 6.6 and 6.4 (yes, that one > is still alive!) that removes the conflict between 'base' and > 'bytestring' and pretends to provide bytestring, containers, array, > etc. People interested in making it easy to use new versions of packages with old compiler releases can make a small script that installs empty Cabal packages called bytestring, containers, array, etc. Then link to it from appropriate places on the wikis, and everyone can benefit from it. Thanks Ian ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Re: [Haskell] Re: Trying to install binary-0.4
Bjorn Bringert wrote: > The tar package uses System.PosixCompat from the unix-compat package > to also work under non-posix systems (read Windows). This dependency > is listed in the tar.cabal file (see http://hackage.haskell.org/ > packages/archive/tar/0.1/tar.cabal). System.Posix was never renamed. > [...] > Why not just install unix-compat? It is listed as a dependency after > all. Actually Windows claims to be a Posix system, too (not that I really believe it or care much). Iirc, unix-compat blew up on GHC 6.4, too, again by picking up the wrong Cabal. I'll check this again tomorrow (don't have access to that machine right now). Anyway, I don't see why something that provides the same functionality as something else needs a different name. With the mechanism of something like apt (Provides, Conflicts, Replaces, ...) I'd have no problem, but Cabal doesn't do that stuff. Maybe it should, though. > I seem to be able to build the tar package against binary-0.3. What > exactly is the error that you are getting? No "instance MonadFix Get" (from memory, I can check this again once I calm down...) > By the way, I don't think that users of open source software have a > right to be pissed off, or at least authors don't have an obligation > to care about them being pissed off. What users do have is a right to > submit patches. No sir, I always have a right to be pissed off. What I don't have is a right to demand anything from you. The problem with patches is how do you patch something as thoroughly messed up as 'base-2.0' vs. 'base-2.1' vs. 'base-2.1.1'? If I saw a way to fix it, you'd already have a patch, but all I have right now is a GHC with an afroengineered package configuration and a mutilated tar package... > That said, I agree that the constantly changing packages make it hard > to keep dependencies up to date. Moreover, the conical place to find packages is Hackage, right? Tar is there, unix-compat is and binary is, too. But bytestring is missing. Which means you have to hunt down bytestring separately, and cabal-get will fail, too. It also means that some of these packages cannot work on any released version of GHC. > I guess that this is price we pay for moving quickly. Is it impossible to move quickly on GHC 6.4? -Udo signature.asc Description: Digital signature ___ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
