February 2001 - Hugs-Bugs

Feb 2001 MSI available
by Sigbjorn Finne 15 Feb '01

15 Feb '01

Hi, I've packaged up a Windows Installer (.msi) for people that want to easily set up and use Hugs98 February 2001 on a Win32 platform. The MSI can be downloaded from http://www.dcs.gla.ac.uk/~sof/hugs98.msi (1.4M) It contains executables (hugs,runhugs and winhugs), libs (std + win32), docs (html, hlp and pdf) and the demos. The only thing that's (intentionally) missing is the Hugs98 source code. In the unlikely event that your machine doesn't already have the Windows Installer engine/runtime installed, runtime redistributables can be downloaded from http://www.microsoft.com/msdownload/platformsdk/instmsi.htm --sigbjorn

1 0

ANNOUNCE: Hugs98 Feb 2001
by Johan Nordlander 15 Feb '01

15 Feb '01

====================================================================== __ __ __ __ ____ ___ || || || || || || ||__ ||___|| ||__|| ||__|| __|| ||---|| ___|| || || || || Version: Feb 2001 ====================================================================== Dear all, I'm pleased to announce the availability of a new release of Hugs98. This is a major release that incorporates bug fixes as well as several new features and enhancements that have been developed for Hugs over the last year. It is announced with the intentions that it will remain a stable and lightweight implementation of Haskell 98 + extensions for some considerable time. A list of the most important new features looks as follows: - A Foreign Function Interface closely modelled after the one provided by GHC. - Built-in, Hood-like debugging support. - Parallel list comprehensions, a.k.a. zip-comprehensions. - A new syntax for recursive monad bindings. - A new GUI under Windows that doesn't consume all CPU time. - Support for the MacOS platform integrated into the main distriution. - Corrections of all bugs reported for the January 2001 beta release. See the release notes in the "docs" directory of the distribution for more information on the new language features. Send email to hugs-users-request(a)haskell.org to join the hugs-users mailing list. Bug reports should be sent to hugs-bugs(a)haskell.org. Send email to hugs-bugs-request(a)haskell.org to subscribe to the hugs-bugs list. The home page and download site for Hugs is at http://www.haskell.org/hugs/ Enjoy, Johan Nordlander [Hugs maintainer]

1 0

re-exporting imported modules
by Peter Thiemann 14 Feb '01

14 Feb '01

I have the following problem: I would like to define a non-standard prelude that redefines only a few names of the standard prelude. The Haskell report suggests that the following combination should do the job (BUG2A defines the non-standard prelude and BUG2B tries to use it): ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ module BUG2A (module BUG2A, module Prelude) where import Prelude hiding (head) head = "HEAD" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ module BUG2B where import qualified Prelude import BUG2A ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Unfortunately, loading BUG2B into the Jan2001 beta release gives the following error message: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ERROR BUG2B.hs - Entity "head" imported from module "BUG2A" already defined in module "Prelude" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >From my understanding of the report, the following BUG2C user module should also do the job, but it gives the same error message: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ module BUG2C where import Prelude () import BUG2A ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Is this a known problem? Cheers -Peter

1 0

Re: AW: What does "Compiled code too complex" error message of Hugs mean?
by Jan Kort 12 Feb '01

12 Feb '01

Laaser Christian wrote: > > I never built Hugs on Windows before :-( ... > and a trial to do so with cygwin/gcc was unsuccessful. > Have you got a precompiled binary for Win (hugs.exe) with these settings, > which you could send me / I could download from somewhere? > > Christian > > > -----Urspr> üngliche Nachricht----- > > Von: Jan Kort [SMTP:kort@wins.uva.nl] > > Gesendet am: Mittwoch, 31. Januar 2001 13:34 > > An: Laaser Christian > > Cc: 'haskell(a)haskell.org' > > Betreff: Re: What does "Compiled code too complex" error message of Hugs mean? > > > > Laaser Christian wrote: > > > > > > When loading some Haskell files with Hugs, I get the error message "Compiled code too complex". However, the compilation with GHC 4.08.1 succeeds. > > > What does this message mean? What can I do about it? > > > > > > > You can grep for that sentence in "hugs98/src", it will point to the > > file "machine.c". There you will see it says "if (nextLab>=NUM_FIXUPS) ...". > > So grep for "NUM_FIXUPS" it will point to the file "prelude.h". I > > think the default value is 400, you should increase it to 1000 or so. > > I have it at 10000, but that's probably not necesary in your case > > and if you increase constants too much starting up Hugs will become > > slower. > > > > Jan You need one of: msc: Microsoft Visual C++ bcc32: 32 bit Borland C win32: 32 bit Borland C, Hugs for Windows djgpp2: DJGPP2 according to hugs98/Install, but I don't have any of them. I use Windows for playing games mostly. Maybe NUM_FIXUPS can be increased a little to say 1000 in the normal distribution, I don't know how much this would slow Hugs down ? Jan

2 1

Corrupted files in winhugs\resource
by Pepe Gallardo 12 Feb '01

12 Feb '01

Some of the files in src\winhugs\resources, in particular, classesd.bmp exitbutt.bmp relobutt.bmp on the cvs repository are corrupted ! . They were fine in the beta release. (¯`·.¸¸.-> pepeg <-.¸¸.·´¯)

3 2

Problem with the new beta
by Paul Moore 10 Feb '01

10 Feb '01

I have just downloaded the new Hugs beta. There is a problem with the supplied ST module - :load ST gives an error, ... Reading file "C:\Data\HugsBeta\Hugs98\lib\exts\ST.hs": Parsing ERROR C:\Data\HugsBeta\Hugs98\lib\exts\ST.hs:48 - Syntax error in type expression (unexpected `.') Paul Moore

2 1

Word64 patch
by Ian Lynagh 09 Feb '01

09 Feb '01

Hi all The Word64 type distributed with hugs (including the latest beta (Jan 2001) against which this patch was created) appears to be somewhat lacking in features that might make it useful. The attached patch makes it an instance of Num, Bits, Integral, Real and Enum. I haven't looked at the hugs internals where this would probably be better done, but this is probably the easier fix in the meantime. There are a few places it goes via Integer - if I get a minute I'll try to think if any of them can be easily removed. Warning: This is pretty much untested, but it parsed OK... Thanks Ian

1 0

Re: Editor Configuration.
by Sigbjorn Finne 07 Feb '01

07 Feb '01

Badrulhisyam Fauzi <bf100(a)doc.ic.ac.uk> writes: > > hi there, > this is not a bug really. i just wanna ask how to configure editor for > hugs version jan 2001 beta. i'm running it using ms dos prompt under > windows me. > > when i type: > > :edit intro.hs > > the result is: > > ERROR - Hugs is not configured to use an editor > > so, how do i configure 'edit' as my editor? Hi, from within Hugs, you can set the editor you want to use via the :set -E option, e.g., if you want to use 'notepad', do Prelude> :s -Enotepad Prelude> :edit intro.hs For more info on the -E option and others, see http://www.cse.ogi.edu/PacSoft/projects/Hugs/pages/hugsman/started.html hth, --sigbjorn I'll really appreciate any help. Thanks. Badrulhisyam Fauzi, Imperial College, London.

1 0

Editor Configuration.
by Badrulhisyam Fauzi 07 Feb '01

07 Feb '01

hi there, this is not a bug really. i just wanna ask how to configure editor for hugs version jan 2001 beta. i'm running it using ms dos prompt under windows me. when i type: :edit intro.hs the result is: ERROR - Hugs is not configured to use an editor so, how do i configure 'edit' as my editor? I'll really appreciate any help. Thanks. Badrulhisyam Fauzi, Imperial College, London.

1 0

ffi patch
by Sigbjorn Finne 07 Feb '01

07 Feb '01

The FFI C code generator (enabled via :set +G) emits code that's not ANSI C compliant (causes problems with MSVC and 'gcc -pedantic') - attached is a patch that fixes this. --sigbjorn

1 0