September 2006 - Hat - Haskell.org

Parsing issue with 1e12
by Neil Mitchell 29 Sep '06

29 Sep '06

Hi Hat and Yhc people (and I guess nhc people as well), Both GHC and Hugs parse 1e12 as a number, but Hat and Yhc don't. For example, test = print 1e12 gives: yhc: -- during when renaming Error: Identifier e12 used at 7:15-7:17 is not defined. I have also been told that Hat leads to an error. So: 1) Is this an error, what does the Haskell spec say? 2) Should the parser be fixed in all the right places? (does this impact Colin's hpc as well?) Thanks Neil

2 1

Re: [Hat] Documentation on trace file format?
by malcolm＠cs.york.ac.uk 15 Sep '06

15 Sep '06

> My biggest problem (at the moment) is that the trace file format is > under-documented. I've written my new back-end by reverse-engineering > existing back-ends, but that's too error-prone for comfort. Is there any > unpublished documentation on the trace file format and its correct > interpretation that might help me ensure I'm not missing anything crucial? Indeed, there is a lot of unpublished documentation about Hat. We had a series of internal memos covering lots of design issues including the file format. Up until now, these have been private, but I can't think of a good reason for them to remain that way, especially if other people are developing on top of Hat and need to understand such issues. So have a look at http://www.cs.york.ac.uk/fp/hat/Memos Bearing in mind that many of the memos may now be superseded or out of date, I hope that nevertheless you manage to find something useful here. (There are two separate memos about the file format, one by me, another by Olaf.) Regards, Malcolm

1 0

Documentation on trace file format?
by John DeTreville 15 Sep '06

15 Sep '06

Hello, I'm in the middle of a small research project that analyzes execution traces of large Haskell programs. I'm currently using Hat as an infrastructure for generating traces (same hat-trans, same libraries, same trace files, custom back-end). I'd first like to thanks the Hat authors and maintainers for their fine work. I've tried or considered a few other ways to generate such traces, and Hat provides a great combination of broad language and library coverage with accurate traces and the ability to trace long executions. Thank you! My biggest problem (at the moment) is that the trace file format is under-documented. I've written my new back-end by reverse-engineering existing back-ends, but that's too error-prone for comfort. Is there any unpublished documentation on the trace file format and its correct interpretation that might help me ensure I'm not missing anything crucial? Cheers, John

1 0

building hat with ghc 6.4.2 under debian testing/unstable
by cb224＠cs.york.ac.uk 11 Sep '06

11 Sep '06

hello, cpp from gcc 4.1.2 appears to output more whitespace than expected when generating ghcsym.out. this results in the following error during build: ~/src/other/hat-2.04.orig$ make src/other/hat-2.04.orig/lib/ix86-Linux/config:11: *** missing separator. Stop. the attached patch appears to fix this.

2 1

Feature request/wish list - library support
by patc＠cse.unsw.edu.au 11 Sep '06

11 Sep '06

Hi, I don't know how you update your web pages and so on, but I'd like to make a feature request (wish!) for support of all the standard haskell libraries. The couple of times I've tried using Hat this has been an issue. ST related libraries are the ones I really want. Also the first time I tried using Hat (this was about a week after I started using Haskell) I got desparately confused by its lack of library support. If I recall, I had a little bit of toy code which used Data.Queue, and tried re-installing Hat several times with different options, each time getting an erro message like "Data.Queue: Does not exist". Could you change the error message to read? Data.Queue: Does not exist; check http://<something> for a list of supported libraries. Thanks all the same for all your work! Regards, Patrick.

2 1