* Simon Marlow:
>> What about handles from System.Process? Do they count as well?
>
> Sure - we hopefully don't consider System.Process to be unsafe.
Here's a demonstration that lazy input has an observable effect. It
needs the Perl helper script included below.
Of course, this example is cons
* 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 Ol
* Nicolas Pouillard:
> Excerpts from Florian Weimer's message of Wed Sep 16 22:17:08 +0200 2009:
>> 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
* 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 b
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.)
___
* 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
