Hi Bjorn,
Thank you, that is good to hear. Thank you for giving us the better
API as well.
Frederik
On Thu, Jan 24, 2008 at 11:03:58PM +0100, Bjorn Bringert wrote:
> Hi Frederik,
>
> I agree with your comments about the headaches of Haskell library stability.
> I made the
> change because it
Hi Frederik,
I agree with your comments about the headaches of Haskell library
stability. I made the change because it seemed like the old library
had no users. I should put my money where my mouth is,
Network.CGI.Compat is now back in the cgi package.
/Bjorn
On Jan 22, 2008, at 18:28 ,
Hi Bjorn,
Well, I don't know what the solution is. As I have said, I think it
would be best to keep Network.CGI.Compat. That way, users of the old
module just have to change the module name, plus they don't have to
hack cgi-compat to get it to compile when cgi is already working.
A typical projec
Hi Frederik,
(I'm CC:ing the libraries list, so that anyone who wants to have
Network.CGI.Compat back in the cgi package can shout.)
That exact module actually used to exist in the cgi package as well (it
implemented the complete API of the old Network.CGI), but after a few
releases I remove
Dear Johannes,
Thanks, that works for me.
Bjorn, perhaps it would be easier to put these five lines in a module
(Network.CGI.Compat?) in the new package, rather than having people
maintain and download a separate cgi-compat package? Perhaps the two
other functions in the old CGI interface can be
If you need the old "wrapper" function, then use something like this:
wrapper :: ([(String,String)] -> IO Html) -> IO ()
wrapper f = runCGI $ do
e <- getInputs
a <- lift $ f $ e
output $ renderHtml a
best regards, Johannes Waldmann.
___
Gl
On Mon, 2008-01-21 at 00:14 +, Frederik Eaton wrote:
> Hello all,
>
> About two years ago, I wrote a web page for one of my projects, using
> Network.CGI. I chose that over WASH because it had a simple interface
> and I thought it would be more stable as a result. Now, Bjorn Bringert
> has re
Hello all,
About two years ago, I wrote a web page for one of my projects, using
Network.CGI. I chose that over WASH because it had a simple interface
and I thought it would be more stable as a result. Now, Bjorn Bringert
has replaced the interface with a completely different one. There is a
cgi-c
