On 05/09/2012 18:07, David Matthews wrote:
On 05/09/2012 14:27, Phil Clayton wrote:
I probably spoke a bit too soon here. After more interactive use, it
appears that records and tuples can be expanded one level in the types
printed back. This can make types much harder to read which may be an
issue for those using an interactive session to e.g. inspect expression
types by evaluating fragments of code. With the example at the end, 5.4
prints back
val nearest = fn: point -> point list1 -> real * point
which is fairly self-explanatory, whereas r1581 prints back
val nearest = fn:
real * real -> (real * real) * (real * real) list -> real * (real
* real)
I can't see a way to fix the bug and still keep the old printing of
types with abbreviations. The problem is that the language definition
does not consider printing at all.
Well, after thinking some more about it overnight I did realise there
was an alternative fix for the bug that kept the old printing. I've
committed this and now the old printing has been restored.
I was actually on the point of releasing 5.5 and I've already rebuilt
the compilers. I can see that it would be preferable to include this
latest change in the 5.5 release especially if you are processing the
output automatically. I might just hold off a little bit longer.
David
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
