Poly/ML

polyml@lists.polyml.org

720 discussions

5.7 Release
by David.Matthews＠prolingua.co.uk 21 Mar '17

21 Mar '17

The latest version, provisionally called 5.6.1, has had very little change for several months. I'm not aware of any show-stoppers so I think it would be a good time to make a release. Because there have been some major changes I was planning to call it 5.7. This is the last chance to do any last tests before the release. David

5 23

5.7 Release
by jrtc27＠jrtc27.com 22 Feb '17

22 Feb '17

Seems I forgot to include the mailing list; adding it back in. James > On 21 Feb 2017, at 19:14, James Clarke <jrtc27 at jrtc27.com> wrote: > > Hi David, > I just uploaded the latest version to Debian's experimental suite[1], and it seems all the interpreted versions are failing when running "make compiler". The error itself is: > >> ./polyimport polytemp.txt -I . < ./exportPoly.sml >> Use: basis/build.sml >> Use: basis/RuntimeCalls.ML >> Use: basis/InitialBasis.ML >> Exception- Match unexpectedly raised while compiling > > Further up in the build logs there is: > >> Making INTGCODE >> mlsource/MLCompiler/CodeTree/ByteCode/INTGCODE.ML:167: warning: Matches are not exhaustive. >> Found near >> case pt of >> BICEval evl => genEval (evl, tailKind) | >> BICExtract ext => if whereto = NoResult then () else locaddr ext | >> BICField {...} => (... ...; ...) | >> ... ... => ... ... | >> ... => ... | >> ... > > > Looking at the source, BICArbitrary is not handled (though there may be others). > > Regards, > James > > [1] Logs at https://buildd.debian.org/status/package.php?p=polyml&suite=experimental > >> On 21 Feb 2017, at 12:48, David Matthews <David.Matthews at prolingua.co.uk> wrote: >> >> The latest version, provisionally called 5.6.1, has had very little change for several months. I'm not aware of any show-stoppers so I think it would be a good time to make a release. Because there have been some major changes I was planning to call it 5.7. This is the last chance to do any last tests before the release. >> >> David >> _______________________________________________ >> polyml mailing list >> polyml at inf.ed.ac.uk >> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml >

2 1

Benchmarks: Poly/ML 5.6.1 vs 5.6.0
by kostirya＠gmail.com 21 Feb '17

21 Feb '17

Many thanks! Poly/ML 5.6.1 FFI is faster than in 5.6.0! So my server (redis-sharding) fasted on 30-80% on Poly/ML 5.6.1. I am also thinking to add kevent and epoll calls into libpolyml :-) But I also noticed that Int32 is very slower in 5.6.1. Int32 is slower than LargeInt. But I don't understand why is it. :-(

2 1

interfacing object oriented libraries
by buday.gergely＠uni-eszterhazy.hu 17 Feb '17

17 Feb '17

Hi, there are known theoretical difficulties bridging SML code to object oriented interfaces. What can be done practically? mGTK has a description here https://www.usenix.org/legacy/event/usenix04/tech/freenix/full_papers/larsen /larsen.pdf Is there any other way? - Gergely

2 1

Poly/ML 5.6.1 Testing and exception_trace
by kostirya＠gmail.com 10 Feb '17

10 Feb '17

Hello. Maybe exception_trace do not work in "Poly/ML 5.6.1 Testing". > poly Poly/ML 5.6.1 Testing > exception Ex; val () = PolyML.exception_trace (fn () => ( raise Ex; () )); exception Ex Exception- Ex raised > > poly Poly/ML 5.6 Release > exception Ex; val () = PolyML.exception_trace (fn () => ( raise Ex; () )); exception Ex Exception trace for exception - Ex End of trace Exception- Ex raised >

2 1

Post-RTS and nonblocking socket functions
by kostirya＠gmail.com 09 Feb '17

09 Feb '17

Hello. I found that the behavior of non-blocking socket functions has changed after upgrading PolyML to Post-RTS version. For example connectNB. If system call connect return -1 and errno is 36 (Operation now in progress), that SML exception occur in Socket.connectNB. Everything worked fine before the upgrade. Nick.

2 1

QUse.use and exceptions
by Ramana.Kumar＠cl.cam.ac.uk 14 Dec '16

14 Dec '16

Hi all, I've noticed that the Vim mode for HOL, in particular this code: https://github.com/HOL-Theorem-Prover/HOL/blob/master/tools/vim/vimhol.src#… has occasionally stopped passing back raised exceptions to the REPL. >From the UI perspective, this means the user gets no feedback when a command fails (it appears as if nothing happened). I believe this change probably happened after the switch from Poly/ML's native use to QUse.use. Looking at QUse, I notice that it calls the Poly/ML compiler function like this: https://github.com/HOL-Theorem-Prover/HOL/blob/master/tools-poly/poly/quse.… Does anyone know whether this is going to have the same exception-raising behaviour as the native use function, or if it is indeed the culprit? Are there compiler flags or something else that could be passed to get the correct handling of exceptions? Cheers, Ramana

1 0

Get errno
by kostirya＠gmail.com 07 Dec '16

07 Dec '16

Hello. Could you please advise a good way to obtain the errno value. I use the following way but I don't like it: > cat errno.c #include <errno.h> int get_errno (void) { return errno; } > cat errno.sml open Foreign val errnolib = loadLibrary "errno.so" val get_errno = buildCall0 ((getSymbol errnolib "get_errno"), (), cInt) fun main () = print ("errno=" ^ (Int.toString (get_errno())) ^ "\n") > cc -shared -o errno.so errno.c > polyc -o errno errno.sml > env LD_LIBRARY_PATH=. ./errno errno=0

3 5

Thank you very much
by kostirya＠gmail.com 18 Nov '16

18 Nov '16

Hello. Thank you very much to everyone who helped me. I finally completed the Standard ML version of my server (with event-driven architecture). I made sure in practice that high-performance asynchronous servers can be done using PolyML and MLton. The performance of PolyML also surprised me pleasantly... For MLton I used memmove for string concatination. I also found out that PolyML FFI is a bit slow. In general, my impression is very positive. Thank you for PolyML and MLton. Nick.

1 0

ConditionVar
by kostirya＠gmail.com 24 Oct '16

24 Oct '16

Hello. Tell me, please, how to use the Thread and ConditionVar. The following code unpredictably hangs up... open Thread open Thread Mutex ConditionVar val cv = conditionVar() and m = mutex(); fun foo() = ( print "OK\n"; signal cv ); fork(foo, [EnableBroadcastInterrupt true, InterruptState InterruptSynch]); wait(cv, m); print "The End\n"; Nick. P.S. I use fixes-5.6 git version PolyML.

2 1

← Newer
1
...
14
15
16
17
18
19
20
...
72
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Poly/ML