Poly/ML September 2017

polyml@lists.polyml.org

4 participants
5 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 11 Nov '17

11 Nov '17

I've finally got round to releasing version 5.7. The source code was actually tagged as 5.7 on Github a while ago and Github considered that a release. There are Windows installers for 32-bit and 64-bit as well as the normal source code for everything else. I'm aware that there are still some unresolved issues with this version but it seems to be stable enough for release. David

3 8

brew install polyml
by lp15＠cam.ac.uk 14 Sep '17

14 Sep '17

As I?ve mentioned before, attempts to build Poly/ML on my machine (OS X 10.12.6) don?t get very far (see errors below). I do have success with "brew install polyml?. But this presumably does not use the --with-gmp option. Is there a way of getting that using homebrew? Larry Paulson -darwin13.1.0/libstdc++-v3/libsupc++/.libs' ld: warning: could not create compact unwind for _ffi_call_unix64: does not use RBP or RSP based frame Undefined symbols for architecture x86_64: "std::__1::__vector_base_common<true>::__throw_length_error() const", referenced from: std::__1::vector<LocalMemSpace*, std::__1::allocator<LocalMemSpace*> >::insert(std::__1::__wrap_iter<LocalMemSpace* const*>, LocalMemSpace* const&) in libpolyml.a(memmgr.o) void std::__1::vector<LocalMemSpace*, std::__1::allocator<LocalMemSpace*> >::__push_back_slow_path<LocalMemSpace* const>(LocalMemSpace* const&) in libpolyml.a(memmgr.o) void std::__1::vector<PermanentMemSpace*, std::__1::allocator<PermanentMemSpace*> >::__push_back_slow_path<PermanentMemSpace* const>(PermanentMemSpace* const&) in libpolyml.a(memmgr.o) void std::__1::vector<CodeSpace*, std::__1::allocator<CodeSpace*> >::__push_back_slow_path<CodeSpace* const>(CodeSpace* const&) in libpolyml.a(memmgr.o) void std::__1::vector<StackSpace*, std::__1::allocator<StackSpace*> >::__push_back_slow_path<StackSpace* const>(StackSpace* const&) in libpolyml.a(memmgr.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [polyimport] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2

3 2

determining link options
by Michael.Norrish＠data61.csiro.au 13 Sep '17

13 Sep '17

I was wondering if there was any way (short of trying to parse the polyc shell-script) of programmatically knowing what the right options might be when calling the linker to link object files dumped by PolyML.export. Thanks, Michael

2 2

calling PolyML.shell from inside another executable
by Michael.Norrish＠data61.csiro.au 06 Sep '17

06 Sep '17

If I write foo.ML: ```` fun main() = PolyML.shell() ```` and compile this with polyc: ```` $ polyc foo.ML -o foo ```` the resulting executable doesn?t give me the usual acknowledgements of my declarations: ```` $ ./foo > 3; > 4; > print "hello\n"; hello > 3 + true; poly: : error: Type error in function application. Function: + : int * int -> int Argument: (3, true) : int * bool Reason: Can't unify int (*In Basis*) with bool (*In Basis*) (Different type constructors) Found near 3 + true Static Errors ```` Here I?d have expected to see lines like `val it = 3 : int`. The behaviour after the compilation of the print call suggests that stdout is live, and that things really are being compiled. The error message after the last interaction is similarly reassuring. If I call PolyML.main() inside a standard poly shell (a funny thing to do), it does work as expected. I also tried to write code like that behind PolyML.shell by hand, and though I was providing a CPOutStream TextIO.print, I also failed to see any output from the compiler. Is there something I should be doing differently? Michael

2 3

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