April 2009 - Haskell - Haskell.org

Announcing Djinn, version 2004-12-11, a coding wizard
by Lennart Augustsson 07 Apr '11

07 Apr '11

Howdy, y'all! I've written a small program that takes a (Haskell) type and gives you back a function of that type if one exists. It's kind of fun, so I thought I'd share it. It's probably best explained with a sample session. calvin% djinn Welcome to Djinn version 2005-12-11. Type :h to get help. # Djinn is interactive if not given any arguments. # Let's see if it can find the identity function. Djinn> f ? a->a f :: a -> a f x1 = x1 # Yes, that was easy. Let's try some tuple munging. Djinn> sel ? ((a,b),(c,d)) -> (b,c) sel :: ((a, b), (c, d)) -> (b, c) sel ((_, v5), (v6, _)) = (v5, v6) # We can ask for the impossible, but then we get what we # deserve. Djinn> cast ? a->b -- cast cannot be realized. # OK, let's be bold and try some functions that are tricky to write: # return, bind, and callCC in the continuation monad Djinn> type C a = (a -> r) -> r Djinn> returnC ? a -> C a returnC :: a -> C a returnC x1 x2 = x2 x1 Djinn> bindC ? C a -> (a -> C b) -> C b bindC :: C a -> (a -> C b) -> C b bindC x1 x2 x3 = x1 (\ c15 -> x2 c15 (\ c17 -> x3 c17)) Djinn> callCC ? ((a -> C b) -> C a) -> C a callCC :: ((a -> C b) -> C a) -> C a callCC x1 x2 = x1 (\ c15 _ -> x2 c15) (\ c11 -> x2 c11) # Well, poor Djinn has a sweaty brow after deducing the code # for callCC so we had better quit. Djinn> :q Bye. To play with Djinn do a darcs get http://darcs.augustsson.net/Darcs/Djinn or get http://darcs.augustsson.net/Darcs/Djinn/Djinn.tar.gz Then just type make. (You need a Haskell 98 implementation and some libraries.) And then start djinn. For the curious, Djinn uses a decision procedure for intuitionistic propositional calculus due to Roy Dyckhoff. It's a variation of Gentzen's LJ system. This means that (in theory) Djinn will always find a function if one exists, and if one doesn't exist Djinn will terminate telling you so. This is the very first version, so expect bugs. :) Share and enjoy. -- Lennart

8 13

Call For Papers: APLAS 2009 (Korea, Dec 14-16, 2009)
by Zhenjiang Hu 09 Oct '09

09 Oct '09

=============================================================== FIRST CALL FOR PAPERS The Seventh Asian Symposium on Programming Languages and Systems (APLAS 2009) Seoul, December 14-16, 2009 http://ropas.snu.ac.kr/aplas09/ =============================================================== APLAS aims at stimulating programming language research by providing a forum for the presentation of recent results and the exchange of ideas and experience in topics concerned with programming languages and systems. APLAS is based in Asia, but is an international forum that serves the worldwide programming languages community. The APLAS series is sponsored by the Asian Association for Foundation of Software (AAFS), which has recently been founded by Asian researchers in cooperation with many researchers from Europe and the USA. The past formal APLAS symposiums were successfully held in Bangalore (2008, India), Singapore (2007), Sydney (2006, Australia), Tsukuba (2005, Japan), Taipei (2004, Taiwan) and Beijing (2003, China) after three informal workshops held in Shanghai (2002, China), Daejeon (2001, Korea) and Singapore (2000). Proceedings of the past symposiums were published in Springer-Verlag's LNCS 2895, 3302, 3780, 4279, and 5356. TOPICS: The symposium is devoted to both foundational and practical issues in programming languages and systems. Papers are solicited on, but not limited, to the following topics: * semantics, logics, foundational theory * type systems, language design * program analysis, optimization, transformation * software security, safety, verification * compiler systems, interpreters, abstract machines * domain-specific languages and systems * programming tools and environments INVITED SPEAKERS: TBA IMPORTANT DATES: Abstract Deadline: June 8 (Monday), 2009 Paper Submission Deadline: 24:00 AM (in Samoan Time), June 15 (Monday), 2009 Author Notification: August 17, 2009 Camera Ready: September 14, 2009 Conference: December 14-16, 2009 SUBMISSIONS INFORMATION: Papers should be submitted electronically online via the conference submission web page at URL <http://www.easychair.org/conferences/?conf=aplas2009>. Acceptable formats are PostScript or PDF, viewable by Ghostview or Adobe Reader. Submissions should not exceed 16 pages in LNCS format, including bibliography and figures. Submitted papers will be judged on the basis of significance, relevance, correctness, originality, and clarity. They should clearly identify what has been accomplished and why it is significant. Submitted papers must be unpublished and not submitted for publication elsewhere. The proceedings of the symposium is planned to be published as a volume in Springer-Verlag's Lecture Notes in Computer Science series. Authors of selected papers will be invited after the symposium to submit a full version for publication in a special issue of New Generation Computing. GENERAL CHAIR Kwangkeun Yi (Seoul National University, Korea) PROGRAM CHAIR Zhenjiang Hu (National Institute of Inforamtics, Japan) PROGRAM COMMITTEE Manuel M. T. Chakravarty (University of New South Wales, Australia) Wei-Ngan Chin (National University of Singapore, Singapore) Nate Foster (University of Pennsylvania, USA) Ralf Hinze (Oxford University, United Kingdom) Zhenjiang Hu (National Institute of Informatics, Japan), Chair Ik-Soon Kim (Electronics and Telecommunications Research Institute, Korea) Julia Lawall (DIKU, Denmark) Sebastian Maneth (NICTA and University of New South Wales, Australia) Sungwoo Park (Pohang University of Science and Technology, Korea) G. Ramalingam (Microsoft Research, India) Peter Thiemann (University of Freiburg, Germany) Kazushige Terui (Kyoto University, Japan) Janis Voigtländer (Technical University of Dresden, Germany) Chung-chieh Shan (Rutgers University, USA) Kazunori Ueda (Waseda University, Japan) Bow-Yaw Wang (Academia Sinica, Taiwan) Jianjun Zhao (Shanghai Jiaotong University, China) POSTER CHAIR Kiminori Matsuzaki (University of Tokyo, Japan)

1 1

ANNOUNCE: ChristmasTree 0.1 (excuses for second attempt)
by S.Doaitse Swierstra 07 Jul '09

07 Jul '09

We are pleased to announce the availability of the package "ChristmasTree", which contains the code associated with our paper at the last Haskell symposium: @inproceedings{1411296, author = {Marcos Viera and S. Doaitse Swierstra and Eelco Lempsink}, title = {Haskell, do you read me?: constructing and composing efficient top-down parsers at runtime}, booktitle = {Haskell '08: Proceedings of the first ACM SIGPLAN symposium on Haskell}, year = {2008}, isbn = {978-1-60558-064-7}, pages = {63--74}, location = {Victoria, BC, Canada}, doi = {http://doi.acm.org/10.1145/1411286.1411296}, publisher = {ACM}, address = {New York, NY, USA}, } The name of the package stands for: "Changing Haskell's Read Implementation Such That by Manipulating Abstract Syntax Trees it Reads Expressions Efficiently" which, given the time of year, seems appropriate. Feel free to download and unpack this "present" at what for the Dutch is called "Sinterklaasavond" (http://en.wikipedia.org/wiki/Sinterklaas) Arthur Baars Marcos Viera Eelco Lempsink Doaitse Swierstra PS: the package uses our library supporting transformation of typed abstract syntax, which we placed in a separate package TTTAS

2 1

[ANN] Safe Lazy IO in Haskell
by Nicolas Pouillard 18 May '09

18 May '09

Hi folks, We have good news (nevertheless we hope) for all the lazy guys standing there. Since their birth, lazy IOs have been a great way to modularly leverage all the good things we have with *pure*, *lazy*, *Haskell* functions to the real world of files. We are happy to present the safe-lazy-io package [1] that does exactly this and is going to be explained and motivated in the rest of this post. === The context === Although these times were hard with the Lazy/IO technique, some people continue to defend them arguing that all discovered problems about it was not that harmful and that taking care was sufficient. Indeed some issues have been discovered about Lazy/IOs, some have been fixed in the underlying machinery, some have just been hidden and some others are still around. == An alternative == An alternative design has been proposed --and is still evolving--, it is called "Iteratee" [2] and has been designed by Oleg Kiselyov. This new design has tons of advantages over standard imperative IOs, and shares some of the goals of Lazy/IOs. Iteratee provides a way to do incremental processing in a high-level style. Indeed both processed data (via enumerators) and processing code (called iteratee) can be modularly composed. The handling of file-system resources is precise and safe. Catching errors can be done precisely and can be interleaved with the processing. In spite of all this, there is an important drawback: a lot of code has to be re-written and thought in another way. Processing becomes explicitly chunked which is not always needed and, even worse, exceptions handling also becomes very explicit. While this makes sense in a wide range of applications it makes things less natural than the general case of pure functions. We think that Iteratee have too be studied more, and we recommend them when you have incrementally react to IO errors. == Issues of Standard Lazy/IO == We think that we can save Lazy/IO cheaply, but before explaining the way we solve such and such issue, let's first expose Lazy/IO and its issues. One of the main Lazy/IO functions is 'readFile': it takes a file path opens it and returns the list of characters until the end of the file is reached. The characteristic of 'readFile' is that only the opening is done strictly, while the reading is performed lazily as much as the output list is processed. Cousins of 'readFile' are 'hGetContents' that takes a file handle and 'getContents' that reads on the standard input. This technique enables to process a file as if the file was completely stored in memory. Because it is read lazily one knows that only the required part of the file will be read. Even better, if the input is consumed to produce a small output or the output is emitted incrementally, then the processing can be done in constant memory space. Examples: -- Prints the number of words read on stdin > countWords = print . length . words =<< getContents -- Prints the length of the longest line > maxLineLen = print . maximum . map length . lines =<< getContents -- Prints in lower case the text read on stdin > lowerText = interact (map toLower) -- Alternatively > lowerText = putStr . map toLower =<< getContents All these examples are pretty idiomatic Haskell code and make a simple use of Lazy/IOs. Each of them runs in constant memory space even if they are declared as if the whole contents were available at once. By using stream fusion or 'ByteString''s one can get even faster code while keeping the code almost the same. Here we will stay with the default list of 'Char''s data type. However one goal of our approach is to be trivially adaptable to those data types. Using our library will be rougly a matter of namespace switch plus a running function: > lowerText = LI.run' (SIO.putStr . map toLower <$> LI.getContents) However we will introducing this library as one goes along. Here is another example where the Lazy/IO are still easy to use but no longer scales well. This program counts the lines of all the files given in arguments: > countLines = print . length . lines . concat =<< mapM readFile =<< getArgs Here the problem is the limitation of simultaneous opened files. Indeed, all the files are opened at the beginning therefore reaching the limit easily. It's time to recall when the files are closed. With standard Lazy/IOs the handle is closed when you reach the end of the file, and so when you've explored the whole list returned by 'readFile'. Note also that if you manually open the file and get a handle, then you can manually close the file, however if by misfortune you close the file and then still consume the lazy list you will get a truncated list, observing how much of the file has been read. This last point is due to the fact that 'readFile' considers the reading error as the end of the file. In particular one can fix this program, by simply counting the number of lines of each file separately and then compute the sum to get the final result. > countLines = print . sum =<< mapM (fmap (length . lines) . readFile) =<< getArgs However once again this program exhausts the handle resources. Trying to close the files will not save us either, one just risks getting truncated files. Indeed the list of intermediate results is produced eagerly but each intermediate result is lazy and then each file is opened but not immediately closed since the computation is delayed. Hopefully adding a bit of strictness cures the problem: > countLines = print . sum =<< mapM ((return' . length . lines =<<) . readFile) =<< getArgs > where return' x = x `seq` return x Until there, we have disclosed three problems: * while reading is lazy, opening is strict, which leads to a less natural processing of multiple files * the closing of files is hard to predict * the errors during reading are silently discarded The last one is a bit trickier and has recently been exposed by Oleg Kiselyov [3]. The problem appears when one gets twice the contents of the same stream---or some kind of inter-dependent streams. Because reading is implicitly driven by the consumer, the interleaving of reading may then depend on the reduction strategy employed. This is the case even if the consumer is a pure function. Basically in this example one can observe different values when using one of these functions: > f1 x y = x `seq` y `seq` x - y > f2 x y = y `seq` x `seq` x - y In this example one reads stdin twice and relies on the error handling to end one stream while keeping the other opened. Moreover there are other ways to achieve this like the use of unix fifo files, or using 'getChanContents' from the "Control.Concurrent.Chan" module. === Our solution === Here we will present another design, based on a very simple idea. Our goal is to provide IO processing in a style very similar to standard Lazy/IO with the following differences: - preservation of the determinism; - a simple control exceptions; - and a precise management of resources. Our solution is made of three key ingredients: a bit of strictness, some predefined schemas to interleave inputs, some scopes and abstract types to delimit lazy input operations from strict IO operations. == Dealing with a single input == Let's present the first ingredient alone through a first example: > mapHandleContents :: NFData sa => Handle -> (String -> sa) -> IO sa > mapHandleContents h f = do > s <- hGetContents h > return' (f s) `finally` hClose h > return' :: (Monad m, NFData sa) => sa -> m sa > return' x = rnf x `seq` return x It implements some combination of 'fmap' and 'hGetContents'. Actually some of our examples fit nicely in that model: > countWords = print =<< mapHandleContents stdin (length . words) > maxLineLen = print =<< mapHandleContents stdin (maximum . map length . lines) > lowerText = putStr =<< mapHandleContents stdin (map toLower) However while the two first examples work well in this setting, the third one tries to allocate the whole result in memory before printing it. Here the ingredient that is used is strictness: the purpose in forcing the result is to be sure that all the needed input is read, before the file is closed. So here we rely on 'NFData' instances to really perform deep forcing---this kind of assumption is a bit like 'Typeable' instances. In particular functions must not be an instance of 'NFData': indeed, we have no way to force lazy values that are stored in the closure of a function. The same remark applies to the 'IO' monad for at least three reasons: 'IO' if often represented by functions; lazy 'IORef''s could be used to hide one input for later use; exceptions with a lazy contents could also be used to make a lazy value escape. Let's now add some more strictness into the meal: the 'SIO' monad! == The 'SIO' monad == The 'SIO' monad is a thin layer over the 'IO' monad, populated only by strict 'IO' operations. In particular these operations are strict in the output, which means that once the output is produced then we know that the given arguments cannot be further evaluated/forced. Here is an example of strict IO using the 'SIO' monad: > import qualified System.IO.Strict as SIO > import System.IO.Strict (SIO) > countWords = SIO.run (SIO.print . length . words =<< SIO.getContents) Of course this function does not scale well since it reads the whole contents in memory before processing it. For now the strict-io [4] package contains wrappers for functions in "System.IO", and strict 'IORef''s. One can now introduce a function in lines of 'mapHandleContents': > withHandleContents :: NFData sa => Handle -> (String -> SIO sa) -> IO sa > withHandleContents h f = do > s <- hGetContents h > SIO.run (f s) `finally` hClose h One can then rewrite 'lowerText' as follow: > lowerText = withHandleContents stdin (SIO.putStr . map toLower) Until there one can deal quite nicely with single input, many outputs processing. Currently the only requirement is to delimit a scope where the resource will be used to return a strict value. Dealing with multiple inputs will lead us to our final design of lazy inputs. == Introducing 'LI', Lazy Inputs == We first introduce a type for these lazy inputs namely 'LI'. This type is abstract and we will progressively introduce functions to build, combine and run them. The 'LI' type is a pointed functor, but not necessarily a monad nor an applicative functor. Therefore one exports the 'pure' function as 'pureLI'. Building primitives allow to read files or handles: > LI.pureLI :: a -> LI a > LI.hGetContents :: Handle -> LI String > LI.getContents :: LI String > LI.readFile :: FilePath -> LI String > LI.getChanContents :: Chan a -> LI [a] Being a functor is important: it allows to wholly transform the underlying input lazily using standard functions about lists for instance: > length <$> LI.readFile "foo" > words <$> LI.readFile "foo" Extracting a final value of a lazy input ('LI' type) is a matter of using: > LI.run :: (NFData sa) => LI sa -> IO sa Or > LI.run' :: (NFData sa) => LI (SIO a) -> IO sa One can therefore re-write our examples using lazy inputs: > -- embedded printing > countWords = LI.run' (SIO.print . length . words <$> LI.getContents) > -- external printing > maxLineLen = print =<< LI.run (maximum . map length . lines <$> LI.getContents) > lowerText = LI.run' (SIO.putStr . map toLower <$> LI.getContents) == Combining inputs == Finally we come to managing multiple inputs. To get both laziness and precise resource management we will provide dedicated combinators. The first one is as simple as appending. > LI.append :: NFData sa => LI [sa] -> LI [sa] -> LI [sa] This one produces a single stream out that sequences the two given streams. It also sequences the usage of resources: the first resource is closed and then the second one is opened. Note that this combinator is still quite general since one can process each input beforehand: > -- one can drop parts of the inputs > (take 100 <$> i1) `LI.append` (drop 100 <$> i2) > -- one can tag each input to know where they come from > Left <$> i1 `LI.append` Right <$> i2 The second one is 'LI.zipWith' which opens the two resources and joins the items into a single stream. Again, since 'LI' is a functor one can join not only characters but also words, lines, chunks... A problem with zipping is that it stops on the shorter input (loosing a part of the other), hopefully one can prolongate them: > zipMaybesWith :: (NFData sa, NFData sb) -> (Maybe sa -> Maybe sb -> c) -> LI [sa] -> LI [sb] -> LI [c] > zipMaybesWith f xs ys = > map (uncurry f) . takeWhile someJust <$> zip (prolongate <$> xs) (prolongate <$> ys) > where someJust (Nothing, Nothing) = False > someJust _ = True > prolongate :: [a] -> [Maybe a] > prolongate zs = map Just zs ++ repeat Nothing The last one is 'LI.interleave': > LI.interleave :: (NFData sa) -> LI [sa] -> LI [sa] -> LI [sa] This function is currently left biased, moreover each resource is closed as soon as we reach its end. However since the inputs are mixed up together one generally prefers a tagged version trivially build upon this one: > interleaveEither :: (NFData sa, NFData sb) => LI [sa] -> LI [sb] -> LI [Either sa sb] > interleaveEither a b = interleave (map Left <$> a) (map Right <$> b) Here are some final programs that scale well with the number of files. > -- number of words in the given files > main = print =<< LI.run . fmap (length . words) . LI.concat . map LI.readFile =<< getArgs > -- almost the same thing but counts words independently in each file > main = print > =<< LI.run . fmap sum . LI.sequence . map (fmap (length . words) . LI.readFile) > =<< getArgs > -- prints to stdout swap-cased concatenation of all input files > main = LI.run' . (fmap (SIO.putStr . fmap swapCase) . LI.concat . map LI.readFile) =<< getArgs > where swapCase c | isUpper c = toLower c > | otherwise = toUpper c > -- sums character code points of inputs > main = print =<< LI.run . fmap (sum . map (toInteger . ord)) . LI.concat . map LI.readFile =<< getArgs Our solution is from now widely available as an Hackage package named "safe-lazy-io" [4]. We hope you will freely enjoy using Lazy/IO again! As usual, criticisms, comments, and help are expected! Finally, I would like to thank Benoit Montagu and Francois Pottier for helping me out to polish this work! [1]: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/safe-lazy-io [2]: http://okmij.org/ftp/Streams.html [3]: http://www.haskell.org/pipermail/haskell/2009-March/021064.html [4]: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/strict-io -- Nicolas Pouillard

2 2

CFT: Haskell Implementers' Workshop 2009 (co-located with ICFP)
by Simon Marlow 18 May '09

18 May '09

Call for Talks ACM SIGPLAN Haskell Implementers' Workshop http://haskell.org/haskellwiki/HaskellImplementorsWorkshop Edinburgh, Scotland, September 3, 2009 The workshop will be held in conjunction with ICFP 2009 http://www.cs.nott.ac.uk/~gmh/icfp09.html Important dates Proposal Deadline: 15 June 2009 Notification: 3 July 2009 The Haskell Implementers Workshop is a new workshop to be held alongside ICFP 2009 this year in Edinburgh, Scotland. There will be no proceedings; it is an informal gathering of people involved in the design and development of Haskell implementations, tools, libraries, and supporting infrastructure. This new workshop reflects the growth of the user community: there is a clear need for a well-supported tool chain for the development, distribution, deployment, and configuration of Haskell software. The aim is for this workshop to give the people involved with building the infrastructure behind this ecosystem an opportunity to bat around ideas, share experiences, and ask for feedback from fellow experts. We intend the workshop to have an informal and interactive feel, with a flexible timetable and plenty of room for ad-hoc discussion, demos, and impromptu short talks. Scope and target audience ------------------------- We feel it's important to clearly distinguish the Haskell Implementers Workshop from the other Haskell-related workshops co-located with ICFP 2009. The Haskell Symposium is for the publication of Haskell-related research. In contrast, the Haskell Implementers' Workshop will have no proceedings - although we will aim to make slides and talk videos available with the consent of the speakers. DEFUN aims to teach how functional programming techniques can be applied in practice. In the Haskell Implementors' Workshop we hope to study the underlying technology that drives this application development. We want to bring together anyone interested in the nitty gritty details necessary to turn a text file into a deployed product. Having said that, members of the wider Haskell community are more than welcome to attend the workshop - we need your feedback to keep the Haskell ecosystem thriving. The scope covers any of the following topics (but there may be some we've missed, so by all means submit a proposal even if it doesn't fit exactly into one of these buckets): * Compilation techniques * Language features and extensions * Type system implementation * Concurrency and parallelism: language design and implementation * Performance, optimisation and benchmarking * Virtual machines and run-time systems * Libraries and Tools for development or deployment Talks ----- At this stage we'd like to invite proposals from potential speakers for a relatively short (20-30 min) talk. Please submit a talk title and abstract of no more than 200 words to simonmar(a)microsoft.com. We want to hear from people writing compilers, tools, or libraries, people with cool ideas for directions in which we should take the platform, proposals for new features to be implemented, and half-baked crazy ideas. We also plan to invite a number of speakers from the community. Organizers ---------- * Duncan Coutts - co-chair (Well-Typed LLP) * Atze Dijkstra (Utrecht University) * Roman Leshchinskiy (University of New South Wales) * Simon Marlow - co-chair (Microsoft Research) * Bryan O'Sullivan (Linden Lab) * Wouter Swierstra (Chalmers University of Technology)

1 1

Haskell Symposium Submission site now open
by Stephanie Weirich 30 Apr '09

30 Apr '09

Submission to the Haskell Symposium is now open at: http://www.easychair.org/conferences/?conf=haskell09 Please do submit! The deadline is a week from tomorrow. (There will be NO EXTENSIONS of this deadline, so do get your paper in on time.) Cheers, Stephanie --------------------------------------------------------------- Haskell 09 ACM SIGPLAN Haskell Symposium 2009 Edinburgh, Scotland, UK September 3, 2009 CALL FOR PAPERS http://haskell.org/haskell-symposium/2009/ The ACM SIGPLAN Haskell Symposium 2009 will be co-located with the 2009 International Conference on Functional Programming (ICFP). The purpose of the Haskell Symposium is to discuss experiences with Haskell and future developments for the language. The scope of the symposium includes all aspects of the design, semantics, theory, application, implementation, and teaching of Haskell. Topics of interest include, but are not limited to, the following: * Language Design, with a focus on possible extensions and modifications of Haskell as well as critical discussions of the status quo; * Theory, in the form of a formal treatment of the semantics of the present language or future extensions, type systems, and foundations for program analysis and transformation; * Implementations, including program analysis and transformation, static and dynamic compilation for sequential, parallel, and distributed architectures, memory management as well as foreign function and component interfaces; * Tools, in the form of profilers, tracers, debuggers, pre-processors, and so forth; * Applications, Practice, and Experience, with Haskell for scientific and symbolic computing, database, multimedia and Web applications, and so forth as well as general experience with Haskell in education and industry; * Functional Pearls, being elegant, instructive examples of using Haskell. Papers in the latter two categories need not necessarily report original research results; they may instead, for example, report practical experience that will be useful to others, re-usable programming idioms, or elegant new ways of approaching a problem. The key criterion for such a paper is that it makes a contribution from which other Haskellers can benefit. It is not enough simply to describe a program! Before 2008, the Haskell Symposium was known as the Haskell Workshop. The name change reflects both the steady increase of influence of the Haskell Workshop on the wider community as well as the increasing number of high quality submissions. The acceptance process is highly competitive. After eleven Haskell Workshops between 1995 and 2007, the first Haskell Symposium was held in Victoria in 2008. Submission Details * Submission Deadline: Friday, May 8th 2009 (3:00 pm, Eastern US Time) * Author Notification: Monday, June 1st 2009 * Final Papers Due : Monday, June 15th 2009 Submitted papers should be in portable document format (PDF), formatted using the ACM SIGPLAN style guidelines (http://www.acm.org/sigs/sigplan/authorInformation.htm) The length is restricted to 12 pages, and the font size 9pt. Each submission must adhere to SIGPLAN's republication policy, as explained on the web. Violation risks summary rejection of the offending submission. Accepted papers will be published by the ACM and will appear in the ACM Digital Library. If there is sufficient demand, we will try to organize a time slot for system or tool demonstrations. If you are interested in demonstrating a Haskell related tool or application, please send a brief demo proposal to Stephanie Weirich, sweirich(a)cis.upenn.edu. Links * http://haskell.org/haskell-symposium, the permanent homepage of the Haskell Symposium. * http://haskell.org/haskell-symposium/2009/, the 2009 Haskell Symposium web page. * http://www.icfpconference.org/icfp2009, the ICFP 2009 web page. Program Committee * Jeremy Gibbons, Oxford University * Bastiaan Heeren, Open Universiteit Nederland * John Hughes, Chalmers/Quviq * Mark Jones, Portland State University * Simon Marlow, Microsoft Research * Ulf Norell, Chalmers * Chris Okasaki, United States Military Academy * Ross Paterson, City University London * Alexey Rodriguez Yakushev, Vector Fabrics * Don Stewart, Galois * Janis Voigtlaender, TU Dresden * Stephanie Weirich, University of Pennsylvania (Chair)

1 0

INAP 2009: 1st CFP
by Pedro Salgueiro 29 Apr '09

29 Apr '09

[apologies for multiple posts; please distribute] ------------------------------------------------- First Call for Papers INAP 2009 18th International Conference on Applications of Declarative Programming and Knowledge Management November 5-7, 2009 Evora, Portugal http://www.di.uevora.pt/inap2009/ http://inap.dialogengines.com/ Organized by the Portuguese AI Society (APPIA), the INAP Committee and the Society of Logic Programming (GLP e.V.) == Overview == Declarative Programming is a family of advanced paradigms for the modeling and solving of complex problems. These specification and implementation methods have attracted more and more attention over the past years, e.g. in the domains of databases and natural language processing, for modeling and the processing of combinatorial problems, and for establishing systems for the web. == INAP 2009 == INAP is a communicative and dense forum for intensive discussion of applications of important technologies related to Prolog, Logic and Constraint Programming as well as closely related advanced software. It comprehensively covers the impact of programmable logic solvers in the Internet Society, its underlying technologies, and leading edge applications in industry, commerce, government, and societal services. INAP 2009 continues a tradition of successful workshops cast around the applications of declarative programming, which were held in Kobe (1997), Tokyo (1995, 1996, 1998 - 2001), Potsdam (2004), Fukuoka (2005) and Wuerzburg (2007). We invite the submission of high quality papers on the described topics, especially, but not exclusively, on different aspects of Declarative Programming, Constraint Processing and Knowledge Management as well as their use for Distributed Systems and the Web: - Knowledge Management, e.g. Data Mining, Decision Support, Deductive Databases - Distributed Systems and the Web, e.g. Agents and Concurrent Engineering, Semantic Web - Constraints, e.g. Constraint Systems, Extensions of Constraint (Logic) Programming - Theoretical Foundations, e.g. Deductive Databases, Nonmonotonic Reasoning - Systems and Tools for Academic and Industrial Use - Knowledge-based Web Services - Logic Solvers and Applications == Workshop Format == The technical program of the workshop will include invited presentations (to be announced), regular technical sessions with presentations of the accepted papers, system demonstrations and a panel discussion. == Conference Venue == The conference will be held at the University of Evora, Portugal in November 5-7, 2009. Evora is a nice and quiet historical city located in the south of Portugal that can be reached from Lisbon by train or coach in under 2 hours. It is a small city of 60.000 inhabitants, 120 km inland from Lisbon and classified by Unesco as World Heritage. The University of Evora was established in the 16th Century and is the 2nd oldest Portuguese University. The social program is promising since the region is very rich in historical sites (Stone Age, Roman, Medieval and Renaissance remains) and also offers a very special gastronomy. See http://en.wikipedia.org/wiki/%C3%89vora for more information. == Important Dates == Paper Submission Deadline: June 29, 2009 Notifications to Authors: August 17, 2009 Camera-ready Version Deadline: September 14, 2009 INAP 2009 Workshop: November 5-7, 2009 == Submission Guidelines == Participants should submit a paper (maximum 15 pages, PDF format), describing their work in topics relevant to the workshop. Accepted papers will be presented during the workshop. At least one author of an accepted contribution is expected to register for the workshop, and present the paper. All submissions should include the author's name(s), affiliation, complete mailing address, and email address. Authors are requested to prepare their submissions, following the LNCS/LNAI Springer format. Please see: http://www.springer.de/comp/lncs/authors.html for further details. The submission should be submitted through the electronic submission site: http://www.easychair.org/inap2009/ The deadline for receipt of submissions is June 29, 2009. Papers received after this date will not be reviewed. Eligible papers will be peer-reviewed by at least three members of the Program Committee. Authors will be notified via email of the results by August 17, 2009. Authors of accepted papers are expected to improve their paper based on reviewers' comments and to send a camera ready version of their manuscripts by September 14, 2009. Accepted papers will be included in the workshop proceedings, which will be distributed to the participants. As in previous editions, we plan to publish selected papers in a proceedings volume in the Springer Lecture Notes in Artificial Intelligence (LNAI) series. == Organizing Committee == Vitor Nogueira vbn AT di.uevora.pt Salvador Abreu spa AT di.uevora.pt Pedro Salgueiro pds AT di.uevora.pt Universidade de Evora Portugal == Program Committee == Salvador Abreu, University of Evora, Portugal (co-chair) Sergio Alvarez, Boston College, USA Philippe Codognet, CNRS/JFLI, Tokyo, Japan Vitor Santos Costa, University of Porto, Portugal Daniel Diaz, University of Paris I, France Ulrich Geske, University of Potsdam, Germany Gopal Gupta, UT Dallas, USA Petra Hofstedt, Technical University of Berlin, Germany Ulrich Neumerkel, Technical University of Vienna, Austria Vitor Nogueira, University of Evora, Portugal Enrico Pontelli, New Mexico State University, USA Irene Rodrigues, University of Evora, Portugal Carolina Ruiz, Worcester Polytechnic Institute, USA Dietmar Seipel, University of Wuerzburg, Germany (co-chair) Terrance Swift, CENTRIA, Portugal Hans Tompits, Technical University of Vienna, Austria Masanobu Umeda, Kyushu Institute of Technology, Japan Armin Wolf, Fraunhofer FIRST, Berlin, Germany Osamu Yoshie, Waseda University, Japan == Contact Information == inap2009 AT di.uevora.pt Universidade de Evora Departamento de Informatica Largo dos Colegiais, 2 7004-516 Evora - PORTUGAL

1 0

International Summer School on Advances in Programming Languages
by voigt＠tcs.inf.tu-dresden.de 29 Apr '09

29 Apr '09

International Summer School on Advances in Programming Languages 25th-28th August, 2009 Heriot-Watt University, Edinburgh, Scotland http://www.macs.hw.ac.uk/~greg/ISS-AiPL Overview This four-day residential International Summer School on Advances in Programming Languages has a major theme of Concurrency, Distribution, and Multicore. Intended primarily for postgraduate research students, the School offers lectures and practical sessions on an engaging blend of cutting edge theoretical and practical techniques from international experts. The Summer School is supported by the Scottish Informatics and Computer Science Alliance (http://www.sicsa.ac.uk/) a Scottish Funding Council Research Pool. Participants from SICSA member institutions may attend at no cost. Confirmed Topics/Speakers - Static and dynamic languages, Prof Phillip Wadler, University of Edinburgh - Compiler technology for data-parallel languages, Dr Sven-Bodo Scholz, University of Hertfordshire - New applications of parametricity, Dr Janis Voigtlaender, Technical University of Dresden - Automatic vectorising compilation, Dr Paul Cockshott, University of Glasgow - Foundational aspects of size analysis, Prof Marko van Eekelen/Dr Olha Shakaravska, Radboud University Nijmegen - Context oriented programming, Dr Pascal Costanza, Vrije Universiteit Brussel - Multi-core programming, Dr Phil Trinder, Heriot-Watt University - Multi-core compilation, Dr Alastair Donaldson, Codeplay Software Ltd - Principles and Applications of Refinement Types, Dr Andrew D. Gordon, Microsoft Research, Cambridge - Resource aware programming in Hume, Prof Greg Michaelson, Heriot-Watt University/ Prof Kevin Hammond, University of St Andrews - Haskell concurrency & parallelism, Dr Satnam Singh, Microsoft Research, Cambridge Location The Summer School is based at Heriot-Watt University's Riccarton campus, set in pleasant parkland to the west of Edinburgh, with easy access to the airport, city and central Scotland: http://www.hw.ac.uk/welcome/directions.htm. The Summer School immediately precedes the 2009 International Conference on Functional Programming (http://www.cs.nott.ac.uk/~gmh/icfp09.html) and takes place during the Edinburgh International Festival (http://www.eif.co.uk/) and the associated Edinburgh Festival Fringe (http://www.edfringe.com/) and Edinburgh International Book Festival (http://www.edbookfest.co.uk/) Steering Committee Prof Greg Michaelson, Heriot-Watt University (Convenor) (mailto:G.Michaelson@hw.ac.uk) Prof Kevin Hammond, University of St Andrews Dr Patricia Johann, University of Strathclyde Prof Phillip Wadler, University of Edinburgh

1 0

[Haskell] HaL4: Local Haskell meeting, Halle/Saale, Germany, June 12
by Henning Thielemann 29 Apr '09

29 Apr '09

Hi all, we like to remind the potential participants of our Local Haskell meeting HaL4 to submit proposals for talks. See the recent announcement in German: http://www.haskell.org/pipermail/haskell/2009-April/021220.html --------------------------------------------- HaL4 : Haskell - Tutorial + Workshop + Party am Freitag, dem 12. Juni 2009, in Halle/Saale --------------------------------------------- Das traditionsreiche HaL-Treffen bietet eine gute Mischung von Haskell-bezogenen Themen aus Forschung, Anwendung und Lehre mit vielen Möglichkeiten zu Diskussion und Unterhaltung bei der anschließenden Party. Der Workshop wird in diesem Jahr ergänzt durch Tutorien für Haskell-Ein- und Umsteiger. Diesmal findet das Treffen in Halle/Saale im Institut für Informatik der Martin-Luther-Universität Halle-Wittenberg statt. Wir planen: 10 - 13 Uhr: Tutorien 15 - 19 Uhr: Fachvorträge 19 - 22 Uhr: Grillparty Wir freuen uns auf rege Teilnahme sowie spannende Vorträge mit heißen Diskussionen und bitten um Vortragsanmeldungen bis zum 8. Mai. Gedacht sind 4 mal je 30 min Vortrag + 30 min Diskussion. Weitere Informationen auf http://www.iba-cg.de/hal4.html Beste Gruesse Henning Thielemann

1 0

ANNOUNCE: ALUT 2.1.0.1
by Sven Panne 28 Apr '09

28 Apr '09

A new version of the ALUT package has been uploaded to Hackage. This is a bug fix only release, containing only tiny changes: * Minor tweaks for recent Cabal versions * Removal of old GHC build system relics. Cheers, S.

2 1