It turned out that there was a problem with building with --with-x
specified. I've fixed this and uploaded a replacement for the tar.gz
download. It would probably have been better practice to have used a
different name to avoid confusion but since it's only been a couple of
days since the or
Thanks for reporting that. I've committed a fix and included your
example as a regression test.
David
Makarius wrote:
Here is another thing that looks like a regression from Poly/ML 5.3.0.
datatype ('a, 'b) foo = Foo of 'a * 'b;
val _ =
PolyML.addPrettyPrinter (fn depth => fn (pretty1, pr
On Mon, 23 Aug 2010, Makarius wrote:
This crashes the RTS when trying to print Foo (1, "a") for example.
Just for the record: this is SVN version 1193.
Makarius
___
polyml mailing list
polyml@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/l
Here is another thing that looks like a regression from Poly/ML 5.3.0.
datatype ('a, 'b) foo = Foo of 'a * 'b;
val _ =
PolyML.addPrettyPrinter (fn depth => fn (pretty1, pretty2) =>
fn Foo (x, y) =>
PolyML.PrettyBlock (2, false, [],
[PolyML.PrettyString "Foo", PolyML.PrettyBre
Rob Arthan wrote:
Thanks for the clarification. In fact, I didn't explain myself very
well. What I meant was that as I have had problems of the sort
linking Poly/ML programs because I used cc rather than c++, I thought
it might be better to use c++ in the documentation throughout.
I think it d
David,
On 20 Aug 2010, at 12:33, David Matthews wrote:
> Rob Arthan wrote:
>>> Matthew,
>>> That looks suspiciously like the "execute bit" problem. Did you include
>>> -segprot POLY rwx rwx
>>> to the linker? See the last line of (the updated)
>>> http://www.polyml.org/FAQ.html#standalone
>> On
Rob Arthan wrote:
Matthew,
That looks suspiciously like the "execute bit" problem. Did you include
-segprot POLY rwx rwx
to the linker? See the last line of (the updated)
http://www.polyml.org/FAQ.html#standalone
On that point, I recall having some problems caused by using "cc" rather than
"
The "-segprog POLY rwx rwx" was the problem with 64-bit MacOS X.
On Thu, Aug 19, 2010 at 1:59 PM, David Matthews
wrote:
> Matthew,
> That looks suspiciously like the "execute bit" problem. Did you include
> -segprot POLY rwx rwx
> to the linker? See the last line of (the updated)
> http://www.po
David,
On 19 Aug 2010, at 18:59, David Matthews wrote:
> Matthew,
> That looks suspiciously like the "execute bit" problem. Did you include
> -segprot POLY rwx rwx
> to the linker? See the last line of (the updated)
> http://www.polyml.org/FAQ.html#standalone
On that point, I recall having som
Matthew,
That looks suspiciously like the "execute bit" problem. Did you include
-segprot POLY rwx rwx
to the linker? See the last line of (the updated)
http://www.polyml.org/FAQ.html#standalone
David
Matthew Fluet wrote:
David,
With that change, I was able to successfully compile MLton with
MacOSX (Leopard) does not exhibit the same issue. Perhaps that
indicates a 32-bit vs. 64-bit issue?
-Matthew
On Thu, Aug 19, 2010 at 9:21 AM, Matthew Fluet wrote:
> David,
> With that change, I was able to successfully compile MLton with
> Poly/ML; unfortunately, the PolyML.export-ed executable
David,
With that change, I was able to successfully compile MLton with
Poly/ML; unfortunately, the PolyML.export-ed executable gives a "Bus
error" (on MacOSX (Snow Leopard)). I'll see if I get a different
result on Linux and if I can reduce the issue.
-Matthew
On Thu, Aug 19, 2010 at 6:00 AM, Dav
Matthew,
Thanks for reporting that. I've installed a fix; well more of a
work-around really and your example now compiles. I managed to reduce
it a few lines which are now in the regression test suite.
Regards,
David
Matthew Fluet wrote:
David,
Poly/ML 5.4 (SVN r1192) gives an InternalErr
David,
Poly/ML 5.4 (SVN r1192) gives an InternalError exception on the
attached program.
[...@graywolf mlton-polyml-bug]$ cat mlton-polyml.use | poly
Poly/ML 5.4 Experimental
...
> Exception- InternalError: getPolyVars: Unable to get type vars raised while
> compiling
Exception-
Fail
"Exce
There was an error in the default handler that is supposed to kill a
thread that raises an uncaught exception. Now fixed.
David
Ramana Kumar wrote:
This code segfaults in 5.4 but runs fine in 5.3:
open Thread Unix
val tail = ref (execute("/usr/bin/env",["sleep","0"]))
fun stopTail () = (kill
I've updated the version number. Thanks for pointing it out.
Regards,
David
Rob Arthan wrote:
David,
I tried building ProofPower svn rev 1189 of Poly/ML on Fedora 12 and it worked
fine.
One question: is it intended that poly -v reports RTS version: I386-5.3.0?
Regards,
Rob.
On 12 Aug 201
David,
I tried building ProofPower svn rev 1189 of Poly/ML on Fedora 12 and it worked
fine.
One question: is it intended that poly -v reports RTS version: I386-5.3.0?
Regards,
Rob.
On 12 Aug 2010, at 16:36, David Matthews wrote:
> I'm planning to release Poly/ML 5.4 by the end of this month
17 matches
Mail list logo
