Poly/ML November 2015

polyml@lists.polyml.org

3 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

Inspecting structures
by ramana.kumar＠gmail.com 27 Jan '16

27 Jan '16

Is there a way to look at the contents (i.e. signature) of a structure without opening it? (I suppose you could just open it then call a lot of PolyML.Compiler.forgetXXX, but that's quite tedious) Also, is it possible to retrieve the long path of an identifier in scope? Something that will, for example, take the rev in scope and say that it came from List. Finally, what about searching for an identifier that would come into scope if you opened some structures?

3 5

Various changes
by David.Matthews＠prolingua.co.uk 20 Nov '15

20 Nov '15

There have been a number of changes added to the git repository over the last weeks and months. This an almost certainly incomplete list. I've tried to include changes that have come up as queries on the mailing list. Added loadHierarchy to PolyML.SavedState. This takes a list of the file names of saved states in order from grandparent, parent to child, and loads them. It functions the same way as loadState except that it allows the parent paths to be specified. Types in structures with opaque signatures are now printed as "?" rather than the print function being inherited. In the debugger, pressing control-C to the debug> prompt returns to the top-level. Actually, what happens is that break-points are disabled and the Thread.Thread.Interrupt exception is raised in the debuggee so it has a chance to clear up. If the debuggee actually catches the interrupt exception then it may not actually return to the top level. There's also a "locals" function in PolyML.Debug to display the local variables. When compiling a file with "use", PolyML.getUseFileName returns the current file name. The floating point precision is now set to 64-bits to avoid inconsistencies depending on whether an intermediate floating point value has been kept in a register or saved into memory. The PolyML.NameSpace structure has been reorganised to split out functions related to the various binding classes into separate sub-structures. The aim is to wrap up the current changes into a new release, probably 5.6 rather than 5.5.3 since there are quite a few changes. That will probably be over the next month or two. David

2 1

loadModule
by David.Matthews＠prolingua.co.uk 10 Nov '15

10 Nov '15

Some new functions have been added to PolyML.SaveState to support "modules". A module is a collection of bindings, primarily structures, signatures and functors, that can be saved and later reloaded. It's mainly aimed at those packaging up binary distributions since a module can only be reloaded into the same binary that exported it, much as with saved states. PolyML.SavedState.savedModule takes a file name and names of structures, signature and functors, together with an optional "on-start-up" function and writes them out as a package. PolyML.SavedState.loadModule takes a name and loads the module. When the module is loaded the "on-start-up" function is executed and the structures, signatures and functors are added to the top-level name space. The module name can either be a file path if it contains a directory separator e.g. ./foo or it is looked up in the path given by POLYMODPATH. There are lower level functions in SavedState that can be used to include values, type constructors and even infix bindings in a module and to import a module into a name space other than the default top-level. The idea is to provide a way for extensions to be packaged up for Poly/ML. There are a number of features that it might be nice to provide but aren't part of the core system. An example would be the Windows GUI modules but I'm sure there are others. I hope it would also encourage contributions. David

1 0

compressing heap images
by Japheth.Lim＠nicta.com.au 02 Nov '15

02 Nov '15

On 21/10/15, Gerwin Klein wrote: > It turns out that with our collection of large Isabelle sessions that we > run regularly, polyml heap image space is becoming a noticeable problem > for us. > We found another way to solve this problem. Isabelle uses saveState to save heaps. If we use saveChild instead, we get a substantial reduction in heap sizes. However, this makes the saved states less portable because they contain the pathname of the parent. Then loading will fail if the heaps are moved to a different path. Here it would be nice if Poly/ML could use relative paths for the parent, and look them up relative to the child. There are other ways to fix this (e.g. chdir before loadState) but I'd rather get the above behaviour from Poly/ML directly. Any thoughts? Japheth ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

2 4

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 November 2015