RE: wondering about -ddump-parsed, rn

2007-08-09 Thread Simon Peyton-Jones
-ddump-parsed shows the program after parsing.  All operator application are 
parsed *left-associative* with one precedence. Then the renamer re-associates 
them to respect precedence and associativity.

So, no, -ddump-parsed will definitely not give syntactically valid Haskell. 
-ddump-rn probably will though.

Simon

| -Original Message-
| From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
| Behalf Of Isaac Dupree
| Sent: 09 August 2007 00:44
| To: GHC Users
| Subject: wondering about -ddump-parsed, rn
|
| Is ghc -ddump-parsed supposed to give parse-syntactically valid Haskell?
| It nearly does - the only way I've seen it not do so is infix
| type-signatures and some infix definitions.  Answer: no, look at what it
| does to the operators with fixities.  But, -ddump-rn seems better...
|
| file:
|
| (@@@) :: a
| a @@@ b = a + b : a + b
|
|  Parser 
| @@@ :: a
| @@@ a b = ((a + b) : a) + b
|
|  Renamer 
| @@@ :: a
| @@@ a b = (a + b) : (a + b)
|
|
| It would be interesting if that was a source-to-source transformation on
| Haskell: a way to delete all the comments and formatting of the original
| file.  Putting parentheses around infix used as prefix would be nice.
| Of course... the renamer output depends on other modules, and must for
| the precise reason of imported fixity declarations!  GHC isn't trying to
| do this so I really have no reason to ask it to :)
|
| P.S. this (-ddump-) is a nice way to see how some stages of GHC's
| processing are done, to get to know them a little, I think, after also
| looking through some code and Commentary
|
| Isaac
| ___
| Glasgow-haskell-users mailing list
| Glasgow-haskell-users@haskell.org
| http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: wondering about -ddump-parsed, rn

2007-08-09 Thread Isaac Dupree

Simon Peyton-Jones wrote:

-ddump-parsed shows the program after parsing.  All operator application are 
parsed *left-associative* with one precedence. Then the renamer re-associates 
them to respect precedence and associativity.

So, no, -ddump-parsed will definitely not give syntactically valid Haskell. 
-ddump-rn probably will though.


yes, in that case, would anyone mind if I find an easy way to change GHC 
to parenthesize those non-infix uses of operators? :)  hmm... maybe _I_ 
would mind, since it makes what GHC is doing just a tiny bit less 
transparent to the user of -ddump-{rn,parsed}. :-)


Isaac
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: wondering about -ddump-parsed, rn

2007-08-09 Thread Christian Maeder
Isaac Dupree wrote:
 Is ghc -ddump-parsed supposed to give parse-syntactically valid Haskell?
 It nearly does - the only way I've seen it not do so is infix
 type-signatures and some infix definitions.  Answer: no, look at what it
 does to the operators with fixities.  But, -ddump-rn seems better...
 
 file:
 
 (@@@) :: a
 a @@@ b = a + b : a + b
 
  Parser 
 @@@ :: a
 @@@ a b = ((a + b) : a) + b

Could -ddump-parsed not simply omit these (wrong) left-associative
parentheses? What information would be lost?

Cheers Christian

___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


GHC 6.8 release plans

2007-08-09 Thread Ian Lynagh

Hi all,

This is just to let you know our plans for the first release of the
up-coming 6.8 branch (which will be called 6.8.1).

We are aiming to have a release candidate by the end of August, with all
the high priority bugs milestoned for 6.8 fixed:

http://hackage.haskell.org/trac/ghc/query?status=newstatus=assignedstatus=reopenedpriority=highmilestone=6.8order=priority

If there are any other bugs that you think are critical for 6.8.1, then
please make your case and add yourself to the bug's CC list now!

We intend to drop support for Win9x, as we are unable to test it. I
understand that the OS itself is no longer supported, and the small
number of Win9x users remaining can continue to use the older GHC
releases. However, if anyone feels strongly that Win9x support should be
continued, and is willing to lead the effort to maintain and test it,
then we will of course be willing to help out with any problems that
arise.


We expect that the release of 6.8.1 will follow, around the end of
September.


Thanks
Ian

___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: wondering about -ddump-parsed, rn

2007-08-09 Thread Stefan O'Rear
On Thu, Aug 09, 2007 at 06:51:12AM -0300, Isaac Dupree wrote:
 Simon Peyton-Jones wrote:
 -ddump-parsed shows the program after parsing.  All operator application 
 are parsed *left-associative* with one precedence. Then the renamer 
 re-associates them to respect precedence and associativity.
 So, no, -ddump-parsed will definitely not give syntactically valid 
 Haskell. -ddump-rn probably will though.

 yes, in that case, would anyone mind if I find an easy way to change GHC to 
 parenthesize those non-infix uses of operators? :)  hmm... maybe _I_ would 
 mind, since it makes what GHC is doing just a tiny bit less transparent 
 to the user of -ddump-{rn,parsed}. :-)

I fixed an identical bug in a copy of the code a few months ago.

http://haskell.org/pipermail/libraries/2007-April/007317.html

Unfortunately, I think TH was forked off from the in-compiler syntax
tree too long ago for my fix to be useful...

Stefan


signature.asc
Description: Digital signature
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users