Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Mon Jul 20 18:00:01 BST 2009.
checking out
Build description = HEAD on x86_64-unknown-linux
(cam-04-unx.europe.corp.microsoft.com)
Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx
Nightly build started on cam-04-unx at Mon Jul 20 19:00:01 BST 2009.
**
Do we make any attempt to keep the GHC API consistent between major
releases, or is the policy generally just to make any naming changes
that we find fitting for GHC's purposes?
-Isaac
Thomas Schilling wrote:
I think the inconsistencies are mostly because SrcSpan was added
later. Patches to
I think the inconsistencies are mostly because SrcSpan was added
later. Patches to improve the problematic cases would (most likely)
be welcome.
2009/7/20 Isaac Dupree :
> is a confusing mess!
> The most important module is named SrcLoc, which is acceptable.
> It contains three types,
> SrcLoc,
>
is a confusing mess!
The most important module is named SrcLoc, which is acceptable.
It contains three types,
SrcLoc,
SrcSpan, which approximately is two SrcLocs (begin and end),
and Located, which combines a SrcSpan (not a SrcLoc!) with an arbitrary
other type.
In practice (well, in my case at
On 18/07/2009 19:49, Ian Lynagh wrote:
Sat Jul 18 08:56:18 PDT 2009 Ian Lynagh
* Follow the split directory rename in the GHC build system rules
Does Cabal need to know about this too?
Cheers,
Simon
___
Cvs-ghc mailing list
Cvs-ghc@haske
