- Hugs-Bugs - Haskell.org

[Hugs-bugs] module system/libraries bug
by Iavor S. Diatchki 04 Feb '04

04 Feb '04

hello, i am having the following problem (just tried it with the current cvs version, on linux) > import Array > import ST hiding (bounds) > > test x = bounds x ERROR "test.hs":4 - Ambiguous variable occurrence "bounds" *** Could refer to: Data.Array.Base.bounds Hugs.Array.bounds I am not sure why ST is exporting "bounds" at all, but in any case the "hiding" clause of the import should prevent the conflict. a similar thing occurs with "indices", but then adding the "hiding" clause solves the problem. -iavor -- ================================================== | Iavor S. Diatchki, Ph.D. student | | Department of Computer Science and Engineering | | School of OGI at OHSU | | http://www.cse.ogi.edu/~diatchki | ==================================================

3 2

[Hugs-bugs] type-cheker woes
by Iavor S. Diatchki 04 Feb '04

04 Feb '04

hello, sorry for the many posts, today seems to have turned into a bug reporting day. there seems to be a probelm with the type checker of the current cvs version: > class {-(Monad m, Monad n) =>-} HasBaseMonad m n | m -> n where > mapBase :: (forall a. n a -> n a) -> m a -> m a > > instance HasBaseMonad IO IO where > mapBase f x = f x ERROR "hugs-bug.lhs":10 - Illegal type in class constraint if i comment-in the commented-out part (the Monad constraints) i get the following: ERROR "hugs-bug.lhs":11 - Inferred type is not general enough *** Expression : mapBase *** Expected type : HasBaseMonad IO IO => (forall c. a c -> a c) -> IO b -> IO b *** Inferred type : HasBaseMonad IO IO => (forall b. IO b -> IO b) -> IO a -> IO a if i remove the instance the script loads fine. -iavor -- ================================================== | Iavor S. Diatchki, Ph.D. student | | Department of Computer Science and Engineering | | School of OGI at OHSU | | http://www.cse.ogi.edu/~diatchki | ==================================================

1 0

[Hugs-bugs] RE: the woes of non-cvs haskellers
by Simon Marlow 04 Feb '04

04 Feb '04

> To give just one concrete example, what packages do I > recommend to someone wanting to learn a bit of Haskell, and > do some graphics and perhaps windowing, on Windows? > > - Hugs (Winhugs bug in current binary release, so better avoid > that and use plain Hugs?) > - HGL (does it work with latest Hugs/GHC, or do I need older > versions? which ones?) > - GHC (current binary release seems to have serious probs on > some Windows versions; has also seen some rapid > development breakage recently, e.g., TH syntax, forcing > other packages to play catch-up just to get working again) > - wxHaskell (works with ghc-6.0.1, will it work with 6.2? what about > Hugs? what about ghc-6.4?) > - some generic text-editor (but on Windows98, the way that .hs > files are associated with Hugs/GHC cannot be modified in > the standard dialogues, as they can for other associations, > so how do I associate .hs files with an editor? I wouldn't > want to recommend some beginner editing the registry for > that purpose..) > > The issues are usually small, but there are many of them, each > package has its own, and all too often the response is "fixed in > CVS, will be in next release". > > Of course, the next release is a while a away and by that time, > there'll be a different set of small issues plagueing the next set > of binary releases. So, just getting someone started requires > careful investigation/testing and some thinking (instead of: > "just download and install the latest Haskell starters set"). It's been a rough ride in a few ways recently. But let me try to explain our policy and why it's a good compromise, and hopefully this will shed some light on why there might be problems going from GHC 6.0.1 to 6.2, for example. There's always going to be a tension between doing lots of bugfix releases and releasing new development versions so that people can get access to new features quickly. We only have limited resources - and we like to do a bit of development & research too, rather than just fixing bugs and doing releases all the time. So we arrived at the current policy, which is... We start a new *major* release every so often (eg. 6.2 is a major release). It has new features, and might change the interfaces to libraries and tools. At this point we branch the codebase. We then do a number of patchlevel releases (6.2.1, 6.2.2 etc.) that fix bugs *only*: i.e. it's highly unlikely that these releases introduce new bugs, and they definitely don't change interfaces. So those after stable binary releases can follow these patchlevels and get a monotonically improving experience :-) Meanwhile, we can continue development on the main branch (the HEAD). Due to our lack of resources, we can't do releases off both the stable branch and the HEAD (otherwise there would have been a 6.0.2). In due course, the HEAD turns into a new major release (6.4) and so on. We think this is a reasonable compromise and makes good use of the resources we've got. Remember that 6.2 is a new major release, and has had zero time to mature. So it's likely there are going to be bugs in it (eg. the Windows ME problem). 6.2.1 will follow shortly, and fix all/most of the issues that were reported without breaking code that works on 6.2. Also remember that certain features like TH are deemed experimental, and fixing their interfaces too soon would give us an undue maintenance burden. If you use experimental features, be prepared to do some conditional compilation based on compiler versions. Cheers, Simon

2 1

[Hugs-bugs] RE: the woes of non-cvs haskellers
by Simon Peyton-Jones 04 Feb '04

04 Feb '04

| I'm getting more and more worried about Haskell users who | depend on multiple Haskell packages and compilers, but don't | want to follow the cvs developments for all of these packages. You are right to be worried. That is why, with strong encouragement from the last Haskell workshop, Isaac has been running the Haskell Library Infrastructure Project. http://www.haskell.org/libraryInfrastructure/ This is not a little private project of Isaac's. It's a major service to us all, for the reasons Claus describes. The more people that offer to help him, the faster we'll get to the point where Claus's problems will be at least ameliorated. Of course, even with a completed library infrastructure, someone has to do the work to fix bugs, and compile wxhaskell with the next version of GHC etc. But at least the dependency tracking, distribution and installation should be much easier. So, all you would-be library writers and users out there... volunteer to Isaac! Meanwhile, the idea of a set of mutually-consistent core Haskell tools has been mooted before, and a very good idea it is too. All it needs is someone to do the work. Simon | -----Original Message----- | From: glasgow-haskell-bugs-bounces(a)haskell.org [mailto:glasgow-haskell-bugs- | bounces(a)haskell.org] On Behalf Of Claus Reinke | Sent: 04 February 2004 13:38 | To: glasgow-haskell-bugs(a)haskell.org | Cc: hugs-bugs(a)haskell.org | Subject: the woes of non-cvs haskellers | | Dear all, | | I'm getting more and more worried about Haskell users who | depend on multiple Haskell packages and compilers, but don't | want to follow the cvs developments for all of these packages. | I have the feeling that Haskellers who rely on pre-packaged | binaries are not currently getting a good impression of the | state of the art. | | To give just one concrete example, what packages do I | recommend to someone wanting to learn a bit of Haskell, and | do some graphics and perhaps windowing, on Windows? | | - Hugs (Winhugs bug in current binary release, so better avoid | that and use plain Hugs?) | - HGL (does it work with latest Hugs/GHC, or do I need older | versions? which ones?) | - GHC (current binary release seems to have serious probs on | some Windows versions; has also seen some rapid | development breakage recently, e.g., TH syntax, forcing | other packages to play catch-up just to get working again) | - wxHaskell (works with ghc-6.0.1, will it work with 6.2? what about | Hugs? what about ghc-6.4?) | - some generic text-editor (but on Windows98, the way that .hs | files are associated with Hugs/GHC cannot be modified in | the standard dialogues, as they can for other associations, | so how do I associate .hs files with an editor? I wouldn't | want to recommend some beginner editing the registry for | that purpose..) | | The issues are usually small, but there are many of them, each | package has its own, and all too often the response is "fixed in | CVS, will be in next release". | | Of course, the next release is a while a away and by that time, | there'll be a different set of small issues plagueing the next set | of binary releases. So, just getting someone started requires | careful investigation/testing and some thinking (instead of: | "just download and install the latest Haskell starters set"). | | A modular way to fix this would be to have at least once-a-month | patch updates of binary packages, so that one would never be | more than a month away from the fixed versions (instead of having | to wait for the next releases of everything). | | A broader approach would be to try and show a united Haskell | tools front to the general Haskeller: Identify a core set of Haskell | tools (the above four would be my initial suggestion), and make | sure that the latest binary releases for these are always in synch | with each other. In other words, someone could go download | them, make a "Haskell tools, Spring 2004" CD, and be sure that | they actually work together while he/she's trying to learn Haskell. | | Both GHC and Hugs have had release candidate testing in the | past, but experience and mailing list archives show that there's | always a number of issues that are only detected after the | binary releases. On Windows at least, it seems that everyone | is relying on Sigbjorn to do all the packaging - couldn't the | creation of updated installers be automated (or Haskellised), | so that he'd only have to be bothered for the initial packaging, | not for patchlevel updates? | | There are similar issues for Haskellers needing a larger set of | tools and libraries, but those will hopefully be addressed by | the library infrastructure project in the long run, so I'm just | asking about the state of the core tools here. | | Opinions? | Claus | | | _______________________________________________ | Glasgow-haskell-bugs mailing list | Glasgow-haskell-bugs(a)haskell.org | http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

1 0

[Hugs-bugs] Winhugs startup error
by Jim Kerr 28 Jan '04

28 Jan '04

I just installed Hugs from the file hugs98-Nov2003-1.msi. The installation seemed to go just fine, and I can start the command-line version of Hugs without any problem. If I try to run winhugs, however, this error message appears in the main window: ERROR - a closing quote, '"', was expected . and an error dialog appears with this message: FATAL ERROR: Unable to load Prelude I have attached a screenshot of this info in case that's any help. I tried uninstalling and reinstalling the package, but that didn't help. Any assistance you could provide would be much appreciated. Thanks, Jim ============= Jim Kerr Software Engineer Agilent Technologies, Inc. Santa Rosa, CA

3 2

[Hugs-bugs] Re: [Haskell] More on HXML toolbox with Hugs/Windows: matchRegex
by Ross Paterson 26 Jan '04

26 Jan '04

On Mon, Jan 26, 2004 at 06:29:45PM +0000, Graham Klyne wrote: > I think I've managed to create a version of POpen to go with Hugs under > Windows. (It all compiles/links, but I haven't yet got a stand-alone test > case for it). > > So now I'm pushing ahead with trying to get the HXML toolbox running under > Hugs/Windows, and I've hit a snag with the Regex library. > > The oldlibs version of Regex apparently exports a function matchRegex, but > the Text.Regex module which it calls upon to supply that function does not > appear to define it. The problem can be seen by trying to load module > Network.URI that is supplied with Hugs (2003 edition). Unfortunately the Windows version of the Nov 2003 release lacks the compiled version of Text.Regex.Posix, which is used by Text.Regex and hence by Network.URI. I don't think there's any way round this with your setup (compiling with MSVC) -- you can recompile the interpreter, but not FFI libraries (I guess?). (It needs to be linked with the stuff in fptools/base/cbits/regex)

1 0

New moderation policy and
by Byron Hale 25 Jan '04

25 Jan '04

I have had two email outages this week and may have been dropped from your list. I have been receiving as many as 1000 SPAM's/day. I notice that the Hugs-users/Hugs-bugs lists do not have any identifying header. I would like to see one, so that I know where an email belongs, without having to open it immediately. If I can get all my lists to do the same, then I can trash SPAM much more easily, and without opening it. Secondarily, I have put restrictive filters on domain name recipients. Later I plan to remove my current email address. Before I do that, I want to see my lists do something like make it difficult to harvest email addresses from lists. That could be by mangling the return address so that human intervention was needed. Any list that does not adopt these measures will ultimately be dropped. I just can't take so much SPAM, 4 or 5 times the volume of email that can efficiently be handled.. Best Regards, Byron Hale

2 1

[Hugs-bugs] problem with winhugs
by K, W, Armstrong 25 Jan '04

25 Jan '04

I am using Windows ME. When I attempt to start WinHugs the window opens and gives an error message of " ERROR - a closing quote, ' " ' , was expected". Also a windows dialog box appears and says "Fatal error: unable to load prelude". Hugs itself works fine. I have tried reinstalling (and with new downloads) but it makes no diference. Ken Armstrong

1 0

[hugs-bugs]Re: New moderation policy
by John Peterson 25 Jan '04

25 Jan '04

Oops - looks like we didn't have list name tags on any of the Haskell lists. I've fixed haskell, haskell-cafe, hugs-bugs, and hugs-users. You'll see [Hugs-bugs] at the start of all subjects to this list now. John

1 0

How define "types.h" on 10.3.2
by Damian Ibarra 20 Jan '04

20 Jan '04

Hi, i have following problem by compiling my self source: " Making all in net source='InetAddress.cc' object='InetAddress.lo' libtool=yes \ depfile='.deps/InetAddress.Plo' tmpdepfile='.deps/InetAddress.TPlo' \ depmode=gcc3 /bin/sh ../../../depcomp \ /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I../../../src -I../../../src -I../ ./.. -g -O2 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -c -o InetAddress.lo `test -f 'InetAddress.cc' || echo './'`InetAddress.cc g++ -DHAVE_CONFIG_H -I../../../src -I../../../src -I../../.. -g -O2 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -c InetAddress.cc -MT InetAddress.lo -MD -MP -MF .deps/InetAddress.TPlo -o InetAddress.o In file included from ../../../src/ipp/net/socket_inc.h:4, from ../../../src/ipp/net/SocketAPI.h:44, from ../../../src/ipp/net/InetAddress.h:44, from InetAddress.cc:35: /usr/include/netinet/in.h:255: error: 'in_addr_t' is used as a type, but is not defined as a type. /usr/include/netinet/in.h:312: error: 'u_char' is used as a type, but is not defined as a type. /usr/include/netinet/in.h:313: error: 'u_char' is used as a type, but is not defined as a type. /usr/include/netinet/in.h:314: error: 'u_short' is used as a type, but is not defined as a type. In file included from /usr/include/netinet/in.h:518, from ../../../src/ipp/net/socket_inc.h:4, from ../../../src/ipp/net/SocketAPI.h:44, from ../../../src/ipp/net/InetAddress.h:44, from InetAddress.cc:35: /usr/include/netinet6/in6.h:123: error: parse error before `[' token /usr/include/netinet6/in6.h:124: error: parse error before `[' token /usr/include/netinet6/in6.h:125: error: parse error before `[' token /usr/include/netinet6/in6.h:145: error: 'u_int8_t' is used as a type, but is not defined as a type. /usr/include/netinet6/in6.h:146: error: 'u_int8_t' is used as a type, but is not defined as a type. /usr/include/netinet6/in6.h:147: error: 'u_int16_t' is used as a type, but is not defined as a type. /usr/include/netinet6/in6.h:148: error: 'u_int32_t' is used as a type, but is not defined as a type. /usr/include/netinet6/in6.h:150: error: 'u_int32_t' is used as a type, but is not defined as a type. /usr/include/netinet6/in6.h:615: error: syntax error before `;' token /usr/include/netinet6/in6.h:617: error: syntax error before `(' token /usr/include/netinet6/in6.h:618: error: syntax error before `(' token /usr/include/netinet6/in6.h:619: error: syntax error before `(' token /usr/include/netinet6/in6.h:621: error: syntax error before `*' token /usr/include/netinet6/in6.h:622: error: syntax error before `(' token /usr/include/netinet6/in6.h:623: error: syntax error before `(' token /usr/include/netinet6/in6.h:625: error: syntax error before `__P' /usr/include/netinet6/in6.h:626: error: syntax error before `(' token /usr/include/netinet6/in6.h:627: error: syntax error before `(' token /usr/include/netinet6/in6.h:629: error: syntax error before `(' token /usr/include/netinet6/in6.h:633: error: syntax error before `(' token /usr/include/netinet6/in6.h:634: error: syntax error before `(' token /usr/include/netinet6/in6.h:635: error: syntax error before `(' token /usr/include/netinet6/in6.h:637: error: syntax error before `(' token /usr/include/netinet6/in6.h:638: error: syntax error before `(' token /usr/include/netinet6/in6.h:640: error: syntax error before `(' token /usr/include/netinet6/in6.h:641: error: syntax error before `(' token /usr/include/netinet6/in6.h:643: error: syntax error before `(' token /usr/include/netinet6/in6.h:645: error: syntax error before `(' token /usr/include/netinet6/in6.h:647: error: syntax error before `(' token /usr/include/netinet6/in6.h:648: error: syntax error before `__P' /usr/include/netinet6/in6.h:649: error: syntax error before `(' token /usr/include/netinet6/in6.h:650: error: syntax error before `(' token /usr/include/netinet6/in6.h:651: error: syntax error before `(' token /usr/include/netinet6/in6.h:652: error: syntax error before `(' token /usr/include/netinet6/in6.h:653: error: syntax error before `(' token In file included from /usr/include/machine/types.h:30, from /usr/include/sys/types.h:72, from ../../../src/ipp/net/socket_inc.h:5, from ../../../src/ipp/net/SocketAPI.h:44, from ../../../src/ipp/net/InetAddress.h:44, from InetAddress.cc:35: /usr/include/ppc/types.h:69: error: syntax error before `typedef' In file included from /usr/include/mach/mach_types.h:64, from /usr/include/pthread.h:66, from ../../../src/ipp/concurrent/pthread_inc.h:4, from ../../../src/ipp/concurrent/AtomicCount.h:39, from ../../../src/ipp/Object.h:42, from ../../../src/ipp/Throwable.h:39, from ../../../src/ipp/Exception.h:39, from ../../../src/ipp/net/SocketException.h:39, from ../../../src/ipp/net/InetAddress.h:47, from InetAddress.cc:35: /usr/include/gcc/darwin/3.3/stdint.h:41: error: syntax error before `;' token /usr/include/gcc/darwin/3.3/stdint.h:52: error: syntax error before `;' token make[4]: *** [InetAddress.lo] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2." th eproblem is the definition of types.h. when i include it in "in6.6" don't make more problem, but i know that isn't the way. i try including it in configure.in but nothing happen. what i wrong do? thx for any helps. best regeards, Damin

1 0