Reply on 6-2-2-branch

Simon Marlow <simonmar@xxxxxxxxxxxxx> writes on 19 Jul 2004 
about  release plans:

> We are currently planning two new releases around the end of August:
> one from the STABLE branch and one from the HEAD.
>
> STABLE: 6.2.2
> -------------
> 
> This will be the final release from the 6.2 branch, containing bugfixes
> only relative to 6.2.1.
> 
> Please if you have any outstanding bugs in 6.2.1, drop us a note. 
> 
> [..]


On  July 20
I have downloaded by  cvs co -r ghc-6-2-branch ghc hslibs libraries
the version of     
                      CVSROOT :pserver:anoncvs@xxxxxxxxxxxxxxxxx:/cvs
and tested it.
It this for future  ghc-6.2.2 ?

I have seen only one minor bug.
Here follow the reports and questions.


1. A bug of a negative number of bytes.

  ghci ...
  > :set +s
  > test "log"
  ...
  (58.68 secs, -989876700 bytes)
  >

Probably this is due to using Int instead of Integer.
And as I recall, it was said fixed (!?)  


2. It identifies itself as  ghc-6.2.1.
   
How to distingush it from the official ghc-6.2.1, by what messages?
Could the CVS versions aiming at some  ghc-XXX,  respond, 
for example, with 
                   " ... GHC, pre-release XXX-pre of July 20, 2004 "

when called        ghc --version  
?


3. `make' produces several warnings about the data fields not 
   initialised: 
  ------------------------------- 
  typecheck/TcRnTypes.lhs:235:
    Warning: Fields of `TopEnv' not initialised: top_nc
             In the record construction: TopEnv
                                             {top_mode = mode,
                                              top_dflags = dflags,
                                              top_hpt = hpt,
                                              top_eps = ref,
                                              top_us = us,
                                              top_errs = top_errs top}
             In the definition of `top'':
                 top' = TopEnv
  ....
  ------------------------------- 
 

With kind regards,

-----------------
Serge Mechveliani
mechvel@xxxxxxxx