- Hugs-Users - Haskell.org

Kontakt Lenste yeni yil firsati 1 Kutu Lens 35 Milyon USTELIK ADRESE TESLIM KACIRMAYIN_______6357474__
by hugs-users 09 Mar '03

09 Mar '03

En ucuz lensler icin lutfen tiklayin. Bir telefonla adrese teslim. http://www.akdenizgoz.com Akdeniz Goz Merkezi Fevzipaþa No:73 Fatih 0 212 635 74 74 Listeden cikmak icin remove(a)akdenizgoz.com adresine bos mail gonderiniz

1 0

RE: Problem with hierarchical libraries in Hugs compared to ghc/nhc98
by Simon Marlow 07 Mar '03

07 Mar '03

> Currently the hierarchical library proposal > http://www.haskell.org/~simonmar/libraries/libraries.html > does not say much about the semantics of the hierarchical > module names. > It really should. I'm open to suggestions - in fact I thought the semantics were fairly clear, but perhaps not? Or do you mean that the document should say more about file names and searching policies? (that would be difficult without getting compiler-specific). Cheers, Simon

1 0

Re: Parsec: GHC /= Hugs?
by Ross Paterson 06 Mar '03

06 Mar '03

[moving from haskell to hugs-users] On Wed, Mar 05, 2003 at 02:31:35PM +0100, Markus.Schnell(a)infineon.com wrote: > > Try the November release of Hugs with the +N option. > > Well, now Hugs and ghc show the same behaviour for my program: > they don't parse my doc, even with the same error. You did ask for compatibility :-) Johannes Waldmann's suggestion may be relevant: : "brackets is now called angles, while squares is now called brackets." : see http://www.cs.uu.nl/~daan/parsec.html > But the +N does not work: it says > "New hierarchical libraries not found along search path; ignoring +N > toggle." I'm guessing that you're explicitly overriding the -P parameter. The trick here is to say ";newdir", so it adds your new directory to the standard ones (which are different between -N and +N). (I think -- I don't know about the Windows interface.) You want the search path to be something like {Hugs}\libraries;{Hugs}\oldlib;{Hugs}\lib\win32 with any other directories added on the end.

4 4

end-of-input signal
by Hamilton Richards 24 Feb '03

24 Feb '03

In the November 2002 release of Hugs for Mac OS X, Control-D apparently no longer signals end of keyboard input. Is there some other signal that causes hugsHIsEOF to return True? Thanks, --Ham -- ------------------------------------------------------------------ Hamilton Richards Department of Computer Sciences Senior Lecturer The University of Texas at Austin 512-471-9525 1 University Station C0500 Taylor Hall 5.138 Austin, Texas 78712-1188 ham(a)cs.utexas.edu hrichrds(a)swbell.net ------------------------------------------------------------------

2 1

Alastair Reid
by John Peterson 21 Feb '03

21 Feb '03

Some of you may have noticed that Alastair hasn't been posting recently. There's a good reason: tomorrow is Alastair's wedding. So best wishes to Alastair and Edie! And please get back to work!! John

1 0

Hugs, Mac OS X 10.1.5, and pathnames
by Hamilton Richards 20 Feb '03

20 Feb '03

In OS X, pathnames have two distinct syntaxes. The GUI uses the pre-X syntax, in which a pathname begins with a volume name and the separator is `:', as in Macintosh HD:Users:ham:Documents:whatever.hs In the Darwin (i.e., unix) command-line "underworld", a pathname begins with /Volumes, spaces are escaped with `\', and the separator is `/', as in /Volumes/Macintosh\ HD/Users/ham/Documents/whatever.hs When you drag a file icon onto the command line, Terminal does the right thing-- it converts the pathname from the GUI syntax to the Darwin syntax, and utilities such as more work just as they should. Hugs, however, doesn't do so well. For example, Prelude> :l /Volumes/Macintosh\ HD/Users/ham/Documents/whatever.hs Reading file "/Volumes/Macintosh\": ERROR "/Volumes/Macintosh\" - Unable to open file "/Volumes/Macintosh\" Quoting the pathname changes the problem, but doesn't cure it: Prelude> :l "/Volumes/Macintosh\ HD/Users/ham/Documents/whatever.hs" ERROR - Missing `\' terminating string literal gap Apparently what's confusing Hugs is the `\', because removing it cures the problem: Prelude> :l "/Volumes/Macintosh HD/Users/ham/Documents/whatever.hs" Reading file "/Volumes/Macintosh HD/Users/ham/Documents/whatever.hs": Is this problem unavoidable, or is it just an oversight? Thanks, --Ham -- ------------------------------------------------------------------ Hamilton Richards Department of Computer Sciences Senior Lecturer Mail Code C0500 512-471-9525 The University of Texas at Austin Taylor Hall 5.138 Austin, Texas 78712-1188 ham(a)cs.utexas.edu hrichrds(a)swbell.net ------------------------------------------------------------------

4 4

Technical suport please !!!
by Hugo Gon�alves 15 Feb '03

15 Feb '03

Hi there... Could i be able to install any version of Hugs in my Palmtop Pc which runs Microsoft Windows CE 1.0 ?? Thank you very much for your atention Best regards, Hugo Gonçalves, Braga Portugal hugor6(a)bragatel.pt

2 1

Installing Hugs
by Katie Messerly 08 Feb '03

08 Feb '03

Hello, I'm trying to get Hugs installed on my Macintosh and the link on the homepage for: Sources and libraries: hugs98-Nov2002.tar.gz is broken. I think I probably need the sources and libraries to get hugs to run. Any suggestions on what I should do? Thanks! Katie Messerly

2 1

On the fly Haskell programming?
by Jeremy Gore 07 Feb '03

07 Feb '03

I've been poking around with Hugs, and at the same time also python's interactive interpreter. They are similar in a number of respects. After playing around with both I thought of some features t In python, you can type in things at the command line and they will stay in memory (for instance, x = 13+4 outputs 21; type x again and it outputs 21, etc.) You can type in a whole program in this way. Unfortunately there is no way to save it afterwards AFAIK, a feature that should be implemented. In the case of Hugs, this seems a natural approach for a Haskell interpreter. Why not be able to type in functions and their type data at the command line to experiment with them? At the end of the session, the results of your experimentation could be saved to a file in the proper format (type info first, then function defs) to clean up and document. Or alternatively it would be saved to a preferences file of sorts, with the option of loading it automatically the next time hugs is started. I suppose using :edit and :reload is pretty close to this, but building programs on the fly in this manner seems to me to be an extremely powerful approach with great potential usefulness in the real world. Is there any sort of Haskell (or other functional programming) shell out there? -- Jeremy Gore 1515 State St New Haven, CT 06511 203-776-4911

3 2

Question about Reductions.
by e2041800＠luna.escuelaing.edu.co 07 Feb '03

07 Feb '03

Hello: I am a student of computer science and a user of Hugs, I am interested to know How hugs calculate the number of reductions when evaluating an expression. I dont understand for example why evaluating the expression 9 gives 12 reductions. Main> 9 9 (12 reductions, 18 cells) Main> I would appreciate if someone can help me with my question ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 1