Poly/ML November 2008

polyml@lists.polyml.org

8 participants
5 discussions

loadState and threads
by pclayton＠taz.qinetiq.com 03 Dec '08

03 Dec '08

Does anyone know what should happen to threads (created with Thread.Thread.fork) when PolyML.SaveState.loadState is performed? It appears that they are no longer reported as active but, despite this, carry on running. Is it up to the user to kill these before doing a loadState? Thanks, Phil The information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). The information in this communication may be confidential and/or legally privileged. Nothing in this e-mail is intended to conclude a contract on behalf of QinetiQ or make QinetiQ subject to any other legally binding commitments, unless the e-mail contains an express statement to the contrary or incorporates a formal Purchase Order. For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful. Emails and other electronic communication with QinetiQ may be monitored and recorded for business purposes including security, audit and archival purposes. Any response to this email indicates consent to this. Telephone calls to QinetiQ may be monitored or recorded for quality control, security and other business purposes. QinetiQ Limited Registered in England & Wales: Company Number:3796233 Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom http://www.qinetiq.com/home/notices/legal.html

3 7

printing out references
by Michael.Norrish＠nicta.com.au 28 Nov '08

28 Nov '08

How can I prettyprint a reference value so that I get some idea from looking at the output whether two such values are the same or not? I have a data type that is littered with various references, and the default pretty-printer only gives me strings with "ref" through them. If I have "ref 1" in one place and "ref 1" in another, I have no idea whether or not these are the same references. If I want to handle this situation in pure SML, it seems as if I'd have to maintain a global list of seen references and look each reference up by doing a linear search through the list. This is pretty awful. Even if there was a Ref.compare function so that I could avoid linear search, the table would still need to be global so that successive pretty-prints would continue to make sense with respect to each other. In Moscow ML there is an Obj.magic function that will turn anything into anything, and in particular seems happy to turn a ref into an integer. Is there something comparable in Poly/ML? (I browsed the poly sources in a very cursory fashion and discovered RunCall.unsafeCast, but this either gave me a segmentation fault, or seemed to be looking at the values at the other ends of the references when I applied it to them.) Michael.

2 1

Unable to allocate immutable area
by thomas.ridge＠cl.cam.ac.uk 18 Nov '08

18 Nov '08

Dear All, I am using polyml to run hol. >From within emacs, I normally use "C-c C-r" to send a region to the hol process. This involves emacs writing out to a tmp file, and the hol process attempting to "use" the file back in. After a lot of proof, I get the following error: "Unable to allocate immutable area" which occurs in the "use" command. Immediately after the above error, I get the following two lines: eg Failed to translate file: /tmp/sml26128UHN Exception- Fail "use" raised The result is that I can no longer use "C-c C-r" to send a file (nor, presumably, "use" any other file). I can still cut and paste into the hol process buffer. What does the error mean? Can I do anything to improve things? Thanks Tom

2 2

obscure segfault
by krauss＠in.tum.de 18 Nov '08

18 Nov '08

Dear list, The following code leads to a segmentation fault when fed into polyml: fun REPEAT t r c = REPEAT t c (t r c); fun I x = x; fun f r c n = if n <= 0 then r n else c n; fun g x = REPEAT f I I x; g 0; The code really doesn't make any sense... but assuming that polyml should never segfault, this must be a bug. Any ideas why this occurs? Does it have to do with the value restriction in some form? Thanks, Alex

3 2

library path-related installation problems with Poly/ML 5.2.1 on Windows XP Professional, Service Pack 2
by DekuDekuplex＠Yahoo.com 12 Nov '08

12 Nov '08

I am trying to install Poly/ML 5.2.1 from source on Windows XP Professional, Service Pack 2, but apparently "make" is having difficulties in finding the library path. Apparently, /usr/local/lib is not in the library search path. I tried overriding this by specifying >./configure --prefix=/usr when running "./configure," but this didn't help. As a result, polyml is unable to build the sample hello program. In the following example of building an application: >$ poly >Poly/ML 5.0 Release >> fun f () = print "Hello World\n"; >val f = fn : unit -> unit >> PolyML.export("hello", f); >val it = () : unit >> ^D >$ cc -o hello hello.o -lpolymain -lpolyml >$ ./hello >Hello World hello.o is built, but there is no file "hello" or "hello.exe" to execute. Apparently, this problem occurs because of the following error messages that appeared while running "make": >*** Warning: linker path does not have real file for library -lgdi32. >*** I have the capability to make that library automatically link in when >*** you link to this library. But I can only do this if you have a >*** shared version of the library, which you do not appear to have >*** because I did check the linker path looking for a file starting >*** with libgdi32 and none of the candidates passed a file format test >*** using a file magic. Last file checked: /lib/w32api/libgdi32.a > >*** Warning: linker path does not have real file for library -lwsock32. >*** I have the capability to make that library automatically link in when >*** you link to this library. But I can only do this if you have a >*** shared version of the library, which you do not appear to have >*** because I did check the linker path looking for a file starting >*** with libwsock32 and none of the candidates passed a file format test >*** using a file magic. Last file checked: /lib/w32api/libwsock32.a > >*** Warning: linker path does not have real file for library -lpthread. >*** I have the capability to make that library automatically link in when >*** you link to this library. But I can only do this if you have a >*** shared version of the library, which you do not appear to have >*** because I did check the linker path looking for a file starting >*** with libpthread and none of the candidates passed a file format test >*** using a file magic. Last file checked: /lib/libpthread.a > >*** Warning: linker path does not have real file for library -ldl. >*** I have the capability to make that library automatically link in when >*** you link to this library. But I can only do this if you have a >*** shared version of the library, which you do not appear to have >*** because I did check the linker path looking for a file starting >*** with libdl and none of the candidates passed a file format test >*** using a file magic. Last file checked: /lib/libdl.a >*** The inter-library dependencies that have been dropped here will be >*** automatically added whenever a program is linked with this library >*** or is declared to -dlopen it. > >*** Since this library must not contain undefined symbols, >*** because either the platform does not support them or >*** it was explicitly requested with -no-undefined, >*** libtool will only create a static version of it. Any ideas on how to overcome this installation problem? -- Benjamin L. Russell

1 0

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 2008