[Hugs-users] Network.CGI missing in Hugs

[Lihn, Steve]

Neil,
My interest is learning Haskell. Not much to do with Pugs at this point.

My OS is redhat linux. There is no binary build for it. So I pulled the
linux source release.
Did a "make" with prefix $HOME/hugs. Then "make install". Runhugs is
under $HOME/hugs/bin. 

I also installed WinHugs. I checked under packages/network/Network.
There are only BSD.hs, Socket.hs, URI.hs, but no CGI.hs? In fact,
keyword search CGI on *.hs under packages/ yields nothing on both linux
and Windows.

Steve

-----Original Message-----
From: Neil Mitchell [mailto:ndmitchell at gmail.com] 

> I am new to the Hugs community. I am drawn to hugs due to perl6's
> success of bootstrapping from hugs.

I think what you are probably thinking of is GHC, which is what Pugs
is written using. Pugs cannot be run under Hugs, it uses some GHC
extensions. However, if you are just going to do "normal" haskell
development, learning the language etc, Hugs is a fine choice to get
started with.

> I am coming from the web development side, so the first thing I am
> thinking doing is of course, doing some cgi stuff with hugs. It seems
> that Network.CGI is missing from Hugs Sep 2006 release. I wonder if
> there is any reason?

Windows/Linux? If Windows did you pick WinHugs or MinHugs? My copy of
WinHugs has it installed, not sure what other options/packages have it
though.

Thanks

Neil




------------------------------------------------------------------------------
Notice:  This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is 
available at http://www.merck.com/contact/contacts.html) that may be 
confidential, proprietary copyrighted and/or legally privileged. It is 
intended solely for the use of the individual or entity named on this 
message. If you are not the intended recipient, and have received this 
message in error, please notify us immediately by reply e-mail and then 
delete it from your system.

------------------------------------------------------------------------------