June 2002 - Hugs-Bugs

toner cartridges
by jorjFn5Tz＠hotmail.com 05 Jun '02

05 Jun '02

1 0

Segfault
by Michal Safranek 04 Jun '02

04 Jun '02

{- Story: I had 'Functional programming' exam today ... (which I totally screwed up) After returning to campus I tried to verify some of my results in hugs-Dec2001 The goal was implementing 'cons' parser to parse either '[1,2,3,...]' or '1:2:3:...:[...]' My example didn't worked (what a surprise :( ). I tried to play with hugs ... and made little mistake in my code ... instead of 'cons = numbers >>= (\x -> enumlist >>= (\y -> return (x ++ y)))' I wrote: 'cons = numbers >>= (\x -> listterm >>= (\y -> return (x ++ y)))' ... complete program and result can be found below ... (I'm sending this here because it seems strange getting segfault to me ...) Sincerely, Wejn PS: Please keep in mind this code was written by total beginner (=me) ... -- Michal Safranek <wejn(at)svamberk.net> (svamberk.net's Linux section, fi.muni.cz student, linuxfan) >>> Bored? Want hours of entertainment? <<< >>> Just set the initdefault to 6! <<< -} import ParseLib listterm :: Parser [Int] listterm = cons `chainr1` ops [(symbol "++", (++))] enumlist :: Parser [Int] enumlist = bracket (symbol "[") (sepby int (symbol ",")) (symbol "]") cons :: Parser [Int] -- cons = ...??... numbers :: Parser [Int] numbers = sepby int (symbol ":") cons = numbers >>= (\x -> listterm >>= (\y -> return (x ++ y))) {- -- it really should be: cons = enumlist +++ (numbers >>= (\x -> symbol ":" >> listterm >>= (\y -> return (x ++ y)))) -- (just in case you're interested) -} {- Hugs session for: /usr/local/share/hugs/lib/Prelude.hs /usr/local/share/hugs/lib/Char.hs /usr/local/share/hugs/lib/Monad.hs /usr/local/share/hugs/lib/hugs/ParseLib.hs a.hs Type :? for help Main> papply listterm "1:2:3:[]" Segmentation fault -}

1 0

Next Hugs release?
by Alastair Reid 03 Jun '02

03 Jun '02

Fellow Hugs Hackers, When do we think the next Hugs release will be? We've accumulated a bunch of small but useful bugfixes (mostly due to Sigbjorn I think), I see some moves towards the new hierarchial libraries and (partly in support of that), I hope to have the full/current ffi spec implemented soon (I got started on it but got distracted by family stuff). It seems like this would be worth formally releasing. IIRC, the preferred time for a release is about a month before classes start up again in the US - or late July/ early August. Does this feel like a date we can realistically push for (i.e., finish current projects and get enough people to play with a prerelease that we find any major showstoppers)? -- Alastair Reid reid(a)cs.utah.edu http://www.cs.utah.edu/~reid/

3 2

RE: Here goes nothing..
by Simon Marlow 03 Jun '02

03 Jun '02

> "C.Reinke" <C.Reinke(a)ukc.ac.uk> writes: > > > > > Thanks for reporting this; now fixed. > > > > > > --sigbjorn > > > > Thanks for fixing; > > as usual, I'm impressed by this efficiency!-) > > > > fyi, the fix implements what the Report prescribes, but I > don't agree with it -- getLine ought not raise an exception > on EOF when having read in a partial line. As is, you will lose > input if it isn't terminated by a newline. Not too cool. FWIW, GHC implements the "sensible" semantics for getLine, i.e. it returns the partial line first, then raises EOF if getLine is called again. I guess I didn't read the report carefully enough :-) Cheers, Simon

1 0

WARNING. You tried to send a potential virus or unauthorised code
by alert＠notification.messagelabs.com 03 Jun '02

03 Jun '02

The MessageLabs SkyScan Anti-Virus service discovered a possible virus or unauthorised code (such as a joke program or trojan) in an email sent by you. The email has now been quarantined and was not delivered. Please read the whole of this email carefully. It explains what has happened to your email, which suspected virus has been caught and what to do if you need help addressing the problem. To help identify the quarantined email: The message sender was mail(a)fur-alle.com hugs-bugs(a)haskell.org The message recipients were beckyr(a)risoftsystems.com The message title was Celebrities The message date was (empty) The virus or unauthorised code identified in the email is ##==>>>> VIRUS POSSIBLE IN FILE: "./718166_2MAUDIO-X-WAV_CTGallery.pif" ##==>>>> VIRUS ID: CVDL W32/Klez-G ##==>>>> Number of files read: 2 ##==>>>> Number of possible virus infections: 1 Some viruses forge the sender address. For more information please visit the link to the virus FAQ's at the bottom of this page. The message was diverted into the virus holding pen on mail server server-2.tower-15.messagelabs.com (pen id 718166_1023101480) and will be held for 30 days before being destroyed Corporate Users: If you sent the email from a corporate network, you should first contact your local IT Helpdesk or System Administrator for advice. They will be able to help you disinfect your workstation. If you would like further information on how to subscribe to MessageLabs SkyScan AV service, a proactive anti-virus service working around the clock, around the globe, please complete our enquiry form. Personal or Home users: If you sent the email from a personal or home account, you will need to disinfect your computer yourself. Please contact your anti-virus software vendor for support. You may like to read the virus FAQ's at: http://www.messagelabs.com/page.asp?id=628 which will answer most virus related questions. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________

1 0