Re: Unsafe hGetContents

2009-10-11 Thread Florian Weimer
* Simon Marlow: Oleg's example is quite close, don't you think? URL: http://www.haskell.org/pipermail/haskell/2009-March/021064.html Ah yes, if you have two lazy input streams both referring to the same underlying stream, that is enough to demonstrate a problem. As for whether Oleg's

Unsafe hGetContents

2009-09-16 Thread Florian Weimer
Are there any plans to get rid of hGetContents and the semi-closed handle state for Haskell Prime? (I call hGetContents unsafe because it adds side effects to pattern matching, stricly speaking invalidating most of the transformations which are expected to be valid in a pure language.)

Re: Unsafe hGetContents

2009-09-16 Thread Florian Weimer
* Don Stewart: fw: Are there any plans to get rid of hGetContents and the semi-closed handle state for Haskell Prime? (I call hGetContents unsafe because it adds side effects to pattern matching, stricly speaking invalidating most of the transformations which are expected to be valid in a

Re: Here-docs in Haskell source

2006-09-24 Thread Florian Weimer
* Ian Zimmerman: Here's a quick test: put the cursor in front of a triple-quoted string, then hit Control-Alt-F (forward-sexp). It should move just after the whole string. Does it? As long as there are no embedded double quotes in the string, it does. Version 4.78 mishandles the embedded