On Nov 7, 2007 4:44 PM, David Benbennick [EMAIL PROTECTED] wrote:
And
once you do hGetContents, you have read all the data that will ever
exist on that handle, so there's nothing to read from it later on.
I completely misunderstood how hGetContents works. This now makes
sense. I first
On Nov 6, 2007 10:15 PM, David Benbennick [EMAIL PROTECTED] wrote:
What about using hGetContents to just read ALL of the input, as a lazy
string? Then you look through that string for success or failure. In
other words,
readACL2Answer pout = do
s - hGetContents pout
parse s here
On Nov 7, 2007 5:12 AM, Denis Bueno [EMAIL PROTECTED] wrote:
Ironically, this was my first problem. First of all, I don't think I
want the semi-closed state -- I want to be able to read and write
freely later on (I may be misunderstanding semi-closed, however).
I don't think that makes sense.
Hi all,
I'm writing some code to interact with an ACL2 [0] process. I'd like
to be able to write a function
test :: String - IO Bool
that will attempt to prove something by forking an ACL2 process and
screen scraping its output, to see whether the conjecture was proved.
The code below [1]
What about using hGetContents to just read ALL of the input, as a lazy
string? Then you look through that string for success or failure. In
other words,
readACL2Answer pout = do
s - hGetContents pout
parse s here
___
Haskell-Cafe mailing list
