Wed Nov 14 21:57:48 PST 2007 Tim Chevalier <[EMAIL PROTECTED]>
* Documentation only - fix typo in flags reference
M ./docs/users_guide/flags.xml -1 +1
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Build description = STABLE on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/ghc/nightly/STABLE-cam-02-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Wed Nov 14 19:00:01 GMT 2007.
* fix #1839, #1463, by supporting ghc-pkg bulk queries with substring matching
- #1839 asks for a ghc-pkg dump feature, #1463 for the ability
to query the same fields in several packages at once.
- this patch enables substring matching for packages in 'list',
'describe', and 'field'
Tue Nov 13 09:01:13 PST 2007 Pepe Iborra <[EMAIL PROTECTED]>
* Fix Trac 1865: GHCi debugger crashes with :print
M ./compiler/ghci/Debugger.hs -1 +1
M ./compiler/ghci/RtClosureInspect.hs -7 +11
M ./compiler/main/InteractiveEval.hs -1 +1
M ./compiler/types/Type.lhs -11 +13
__
Wed Nov 14 07:30:10 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* FIX #1837: emit deprecated message for unversioned dependencies
M ./utils/ghc-pkg/Main.hs -3 +11
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/
Wed Nov 14 02:47:01 PST 2007 [EMAIL PROTECTED]
* FIX Trac 1888; duplicate INLINE pragmas
There are actually three things here
- INLINE pragmas weren't being pretty-printed properly
- They were being classified into too-narrow boxes by eqHsSig
- They were being printed in to much detai
Wed Nov 14 03:29:30 PST 2007 [EMAIL PROTECTED]
* FIX Trac 1662: actually check for existentials in proc patterns
I'd fixed the bug for code that should be OK, but had forgotten to
make the test for code that should be rejected!
Test is arrowfail004
M ./compiler/typecheck/Tc
Tue Nov 13 07:32:57 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* FIX #1653 (partially): add -X flags to completion for :set
M ./compiler/main/DynFlags.hs -1 +4
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cv
Wed Nov 14 07:14:11 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* Fix #782, #1483, #1649: Unicode GHCi input
GHCi input is now treated universally as UTF-8, except for the Windows
console where we do the correct conversion from the current code
page (see System.Win32.stringToUnicode).
T
Mon Sep 24 03:33:23 PDT 2007 Simon Marlow <[EMAIL PROTECTED]>
* comments only: point to relevant bug reports
M ./compiler/ghci/InteractiveUI.hs -2 +5
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Sun Nov 11 13:36:18 PST 2007 Ian Lynagh <[EMAIL PROTECTED]>
* Remove ex-extralibs from libraries/Makefile
M ./libraries/Makefile -7
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Sun Nov 11 13:34:47 PST 2007 Ian Lynagh <[EMAIL PROTECTED]>
* Remove the X11 and HGL libraries from extralibs
Don Stewart, X11 maintainer, requested we remove X11, and HGL depends on it
on Linux (and we don't try to build HGL on Windows).
M ./libraries/extra-packages -2
___
Wed Nov 7 01:59:52 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* catch up with removal of config.mk in the readline package
M ./compiler/Makefile -4 +1
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Sun Nov 11 08:44:52 PST 2007 Ian Lynagh <[EMAIL PROTECTED]>
tagged 2007-11-11
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
- (unimplemented, but would be nice):haddock would like
to scope comments in the context of their locations
Sorry, I don't know what you mean here. Example?
hmm, as long as haddock is used exclusively for api documentation,
there might not be any examples (because external users don't h
ghci now has the ability to show dynamic flag settings
and language flags, and that is the test for it. as far as
i know, we've accounted for all platform issues, but as
there wasn't any other test of all flags before, only this one will
show up in validate runs after flag changes.
Ok, but tha
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/ghc/nightly/HEAD-cam-02-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Wed Nov 14 19:30:05 GMT 2007.
checki
Wed Nov 14 12:40:50 PST 2007 David Waern <[EMAIL PROTECTED]>
* Avoid making Either String an instance of Monad in the Haddock parser
M ./compiler/main/GHC.hs -1 +4
M ./compiler/parser/HaddockParse.y -13 +18
M ./compiler/parser/HaddockUtils.hs -2 +2
M ./compiler/parser/Parser.y.p
Claus, is this expected to work with 6.8 ?
There is no ':show languages' option there, so the test fails.
i should have said STABLE branch, i guess.
but this raises a question for those tests referring to
features and fixes that have been merged into STABLE
after release: should those tests b
Claus, is this expected to work with 6.8 ?
There is no ':show languages' option there, so the test fails.
It passes fine with HEAD here.
pepe
On 14/11/2007, at 14:48, Claus Reinke wrote:
I'm testing the fix now. Claus, I'm not very fluent with Python,
care if I send you the patch to ghci02
Claus Reinke wrote:
aside: while looking into HaddockParse.y, i noticed an
instance Monad (Either String) where
that will propagate all the way to all users of the ghc api!
Prelude GHC Control.Monad.Error> :i Monad
..
instance (Error e) => Monad (Either e)
-- Defined in Contr
is there no way for haddock to extract any local names
by traversing the AST fragment (in which those local
names have been resolved properly) the comment is attached/next to?
But then it is doing renaming, and it has to understand the complete
scoping rules of HsSyn. It would be duplicating w
Simon wrote:
> I'm thinking that putting the Haddock documentation in the .hi file would
> be a regression with respect to modularity, so it's not something we
> should
> pursue. Re-typechecking all the code doesn't take very long (about a
> minute for the whole of GHC, IIRC). We should store th
Fri Nov 9 08:26:52 PST 2007 [EMAIL PROTECTED]
* FIX 1463 (implement 'ghc-pkg find-module')
- the ticket asks for a module2package lookup in ghc-pkg
(this would be useful to have in cabal, as well)
- we can now ask which packages expose a module we need,
eg, when preparing a ca
Wed Nov 14 07:34:17 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* remove --define-name from the --help usage message (#1596)
M ./utils/ghc-pkg/Main.hs -4 +8
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs
Wed Nov 14 07:30:10 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* FIX #1837: emit deprecated message for unversioned dependencies
M ./utils/ghc-pkg/Main.hs -3 +11
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/
Wed Nov 14 06:11:11 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* Add test for #782
M ./tests/ghc-regress/ghci/scripts/all.T +1
A ./tests/ghc-regress/ghci/scripts/ghci028.script
A ./tests/ghc-regress/ghci/scripts/ghci028.stdout
___
Cvs-ghc
Wed Nov 14 07:14:11 PST 2007 Simon Marlow <[EMAIL PROTECTED]>
* Fix #782, #1483, #1649: Unicode GHCi input
GHCi input is now treated universally as UTF-8, except for the Windows
console where we do the correct conversion from the current code
page (see System.Win32.stringToUnicode).
T
David Waern wrote:
| In the meantime we could consider the less invasive change: put
FastString
| in place of HsDoc in HsSyn. No need to pass functions into GHC to do
the
| renaming: Haddock can do it itself since it only needs the top-level
| GlobalRdrEnv which GHC provides. I don't think Hadd
Claus Reinke wrote:
That'd be quite tricky, because different names are in scope in
different places. E.g. 'a' means two different things in (f a (\a.a)).
I'd forgotten about Names in Haddock comments -- they make a good
reason
not to treat Haddock comments as opaque strings.
Hmm, but in a ha
That'd be quite tricky, because different names are in scope in
different places. E.g. 'a' means two different things in (f a (\a.a)).
I'd forgotten about Names in Haddock comments -- they make a good reason
not to treat Haddock comments as opaque strings.
Hmm, but in a haddock comment, the only
http://hackage.haskell.org/trac/ghc/ticket/1886
I quite like this idea, but it's a substantial upheaval, and therefore more
of a long-term proposition.
In the meantime we could consider the less invasive change: put FastString
in place of HsDoc in HsSyn. No need to pass functions into GH
Wed Nov 14 04:58:42 PST 2007 David Waern <[EMAIL PROTECTED]>
* Fix build
I had forgot to update HaddockLex.hi-boot-6, so the build with 6.2.2
failed. This fixes that.
M ./compiler/parser/HaddockLex.hi-boot-6 +2
___
Cvs-ghc mailing list
Cvs-g
Wed Nov 14 03:37:40 PST 2007 [EMAIL PROTECTED]
* Test for Trac #1662
M ./tests/ghc-regress/arrows/should_fail/all.T +1
A ./tests/ghc-regress/arrows/should_fail/arrowfail004.hs
A ./tests/ghc-regress/arrows/should_fail/arrowfail004.stderr
_
Wed Nov 14 02:44:58 PST 2007 [EMAIL PROTECTED]
* Test for Trac #1888
M ./tests/ghc-regress/rename/should_fail/all.T +1
A ./tests/ghc-regress/rename/should_fail/rnfail048.hs
A ./tests/ghc-regress/rename/should_fail/rnfail048.stderr
___
Cvs
Wed Nov 14 03:29:30 PST 2007 [EMAIL PROTECTED]
* FIX Trac 1662: actually check for existentials in proc patterns
I'd fixed the bug for code that should be OK, but had forgotten to
make the test for code that should be rejected!
Test is arrowfail004
M ./compiler/typecheck/Tc
Wed Nov 14 02:47:01 PST 2007 [EMAIL PROTECTED]
* FIX Trac 1888; duplicate INLINE pragmas
There are actually three things here
- INLINE pragmas weren't being pretty-printed properly
- They were being classified into too-narrow boxes by eqHsSig
- They were being printed in to much detai
Wed Nov 14 02:46:32 PST 2007 [EMAIL PROTECTED]
* Run the -frule-check pass more often (when asked)
M ./compiler/main/DynFlags.hs -2 +7
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
> | In the meantime we could consider the less invasive change: put
> FastString
> | in place of HsDoc in HsSyn. No need to pass functions into GHC to do
> the
> | renaming: Haddock can do it itself since it only needs the top-level
> | GlobalRdrEnv which GHC provides. I don't think Haddock needs
| In the meantime we could consider the less invasive change: put FastString
| in place of HsDoc in HsSyn. No need to pass functions into GHC to do the
| renaming: Haddock can do it itself since it only needs the top-level
| GlobalRdrEnv which GHC provides. I don't think Haddock needs HsSyn with
All I meant was that we should use a more refined notion of "depth limit"
which does a good job of cutting off the output before it grows too large.
That might mean limiting not only the depth, but the width too, for example.
Cheers,
Simon
pepe wrote:
To clarify, this is only when doi
Claus Reinke wrote:
It's a very attractive approach, but comments can appear absolutely
anywhere in the concrete syntax, between any two tokens. How do we
decide where to attach these comments to the AST?
Allowing them anywhere but not ignoring them needs some thought for how
to parse them witho
To clarify, this is only when doing ':show bindings', not when doing
':print'.
Ensuring that the output given never gets too large would mean
arbitrarily cutting it to make it fit, or giving the user some control
over these settings. I remember talking to you about this in ICFP, and
I got t
Pepe Iborra wrote:
Tue Nov 13 09:45:39 PST 2007 Pepe Iborra <[EMAIL PROTECTED]>
* GHCi debugger: added a new flag, -fno-print-binding-contents
The contents of bindings show at breakpoints and by :show bindings
is rendered using the same printer that :print uses.
But sometimes the out
Malcolm Wallace wrote:
Simon Peyton-Jones <[EMAIL PROTECTED]> writes:
| So in this hypothetical system, haddock uses the GHC API to get at the
| comments in the AST, it somehow figures out which comments are in
| locations that are legal for haddock markup, parses them. It extracts
| the names
Simon Peyton-Jones <[EMAIL PROTECTED]> writes:
> | So in this hypothetical system, haddock uses the GHC API to get at the
> | comments in the AST, it somehow figures out which comments are in
> | locations that are legal for haddock markup, parses them. It extracts
> | the names from the markup an
Oops, sorry everybody, I had some patches lying around from the
Hackathon which I had validated already back then. I naively assumed
they would still pass validation.
I'm testing the fix now. Claus, I'm not very fluent with Python, care
if I send you the patch to ghci024.py for revision?
| Unexpected failures:
| ghci024(ghci)
|
| This is probably related to the new debugger-related patches from
| yesterday. It'd be good to keep validate *break free* (or is this an
| OS issue)?
Yes, the protocol is: validate then commit. It's very easy to commit the test
patches but not the
Build results:
gabor stable: pass
kahl G5 Gentoo Linux stable:pass
mnemosyne x86-64 Gentoo stable: pass
tnaur PPC OSX stable: lost
tnaur x86 Linux stable: fail (failed stage1)
x86 Windows stable: pass
x86 Windows stable fast:pass pass pass
Build results:
x86-64 Linux head: pass
x86 Windows head: pass
x86 Windows head fast: pass pass pass pass pass pass
kahl G5 Gentoo Linux head: pass
x86-64 Linux head unreg: pass
New unexpected test passes:
1603 1 x86 Windows head
New unexpected test failures:
160
| So in this hypothetical system, haddock uses the GHC API to get at the
| comments in the AST, it somehow figures out which comments are in
| locations that are legal for haddock markup, parses them. It extracts
| the names from the markup and using the GHC API again (stuff from the
| renamer) tri
51 matches
Mail list logo
