Poly/ML February 2017

polyml@lists.polyml.org

6 participants
7 discussions

linking polyML modules to C
by dtopham＠gmail.com 09 Nov '18

09 Nov '18

After more experimenting with GUI in SML, I would like to now try calling an SML module from a C program. That way, the GUI could be built using traditional imperative techniques and the program logic could be written in SML. I see how to call a C function from SML, but and not so clear on how to call an SML function from a C program. I want to build code using polyc and then link with a C main program, but could anyone show me a simple example of calling that function and getting its return value? for example, I have defined: fun sum i n f = if i > n then 0.0 else f i + sum (i+1) n f ; fun int2real x = real x ; in linkToC.sml and #include <iostream> #include <fstream> std::ofstream ofs; int main() { std::cout << sum(1,10,int2real) << std::endl; ofs.open("table.dat"); for(int i = 0; i < 20; i++) ofs << i << '\t' << sum(1,i,int2real) << std::endl; } in linkToC.cpp Looking in the polyc script, I thought adding the -c option might allow me to build the object code which I could then link to the sml functions, but it complains about not having a main. Could someone point me in the right direction? Thanks, Dave On Mon, Dec 15, 2014 at 11:44 AM, David Topham <dtopham at gmail.com> wrote: > David, Thank you so much! I really appreciate your help with this. Your > sample below builds fine with polyc on my system (PolyML 5.5.2). I am using > a minimal Linux distribution named TinyCore ( > http://distro.ibiblio.org/tinycorelinux/) which comes with OpenMotif > 2.3.3 It runs in a virtual machine within another computer only taking up > a few hundred MBs! > > I am going to use it to help my students explore Discrete Math next > semester (this textbook uses SML for that purpose: > http://cs.wheaton.edu/~tvandrun/dmfp/). > > I also found a reasonably current project using PolyML and Motif here: > http://www.lemma-one.com/ProofPower/index/ > > ...however it was built on PolyML 4 and has not yet been ported to the > newer version (e.g. depends on PolyML.commit which no longer seems to be > supported). > > Happy Holidays to everyone in the PolyML community! > > -David Topham > > >> Re: GUI Interface (David Matthews) >> >> I've experimented with building a stand-alone executable with Motif and >> succeeded in getting it to work for me using polyc. (It required >> building Poly/ML with --with-x). I took the example from >> http://www.polyml.org/docs/Motif.html and wrapped it up in a function. >> I did find a problem, though. It looks as though the function has to >> suspend itself with something like Posix.Process.pause otherwise nothing >> happens. I seem to recall that the Motif stuff is handled on a separate >> thread to allow the REPL to continue to accept commands. With a >> stand-alone application there isn't a REPL so without the "pause" it >> terminates immediately. >> >> David >> >> open XWindows ; >> open Motif ; >> >> fun main() = >> let >> val shell = >> XtAppInitialise "" "xed" "Editor" [] [XmNwidth 400, XmNheight 400] ; >> >> val main = XmCreateMainWindow shell "main" [] ; >> >> val bar = XmCreateMenuBar main "bar" [] ; >> >> val fileMenu = XmCreateCascadeButton bar "file" [XmNlabelString "File"] ; >> val editMenu = XmCreateCascadeButton bar "edit" [XmNlabelString "Edit"] ; >> val viewMenu = XmCreateCascadeButton bar "view" [XmNlabelString "View"] ; >> val helpMenu = XmCreateCascadeButton bar "help" [XmNlabelString "Help"] ; >> >> val command = XmCreateText main "command" [XmNeditMode >> XmSINGLE_LINE_EDIT] ; >> >> val hscroll = XmCreateScrollBar main "hscroll" [XmNorientation >> XmHORIZONTAL] ; >> val vscroll = XmCreateScrollBar main "vscroll" [XmNorientation >> XmVERTICAL] ; >> >> val work = XmCreateDrawingArea main "work" [] ; >> in >> >> XtManageChildren [fileMenu, editMenu, viewMenu, helpMenu] ; >> XtManageChildren [bar, command, hscroll, vscroll, work] ; >> >> XmMainWindowSetAreas main bar command hscroll vscroll work ; >> >> XtManageChild main ; >> XtRealizeWidget shell; >> Posix.Process.pause() >> end; >> >> >> ------------------------------ >> >> _______________________________________________ >> polyml mailing list >> polyml at inf.ed.ac.uk >> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml >> >> End of polyml Digest, Vol 110, Issue 12 >> *************************************** >> >> -- >> The University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> >>

2 3

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

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 February 2017