Poly/ML April 2009

polyml@lists.polyml.org

7 participants
4 discussions

regular expression support?
by luzhao＠cs.utah.edu 22 Apr '09

22 Apr '09

Hi, Does PolyML support regular expression matching? I looked through the source code tree $PolyML/basis and didn't find something like Reg*. I'd like to confirm that this is true. Thanks. Lu

2 1

Binary compatibility and static linking
by rda＠lemma-one.com 09 Apr '09

09 Apr '09

I am trying to understand what level of binary compatibility I can expect if I use Poly/ML to create an executable by exporting a function which calls PolyML.rootFunction to give the users a Poly/ML interactive session. The users will then update the Poly/ML state, save it and reload it in later sessions using the functions in PolyML.SaveState. They will also load state files prebuilt for them. If I build the executable on system A and create some saved state files there, how like A does some other system B have to be for the executable and the saved state files to work on B? I am concerned both about the compatibility for the saved state files and for the shared object files libpolyml.so and libpolymain.so. I understand QinetiQ have no problems moving between systems with Intel hardware and recent-ish slackware and Fedora operating systems. Would the same files work on my Intel Mac? On a related topic: I have had no success trying to link polyml statically. I I use -Wl,-Bstatic -lpolymain -lpolyml -Wl,-Bdynamic on the command line, I get screeds of undefined reference messages. Is static linking an option to build a binary that can be run without installing Poly/ML? If so, how do I do it? Regards, Rob.

3 5

structure/signature matching regression in SVN
by fluet＠tti-c.org 09 Apr '09

09 Apr '09

>From recent SVN commit messages, I see that there has been some reorganization of structure/signature matching; apologies if the reorganization is incomplete (i.e., not ready for testing) and/or the following is a known issue. This program type checks under PolyML 5.2.1 (and SML/NJ 110.68 and MLton 20070826), but reports type errors under PolyML SVN HEAD. ===== signature UNIQUE_SET_STRUCTS = sig structure Element: sig type t end end signature UNIQUE_SET = sig include UNIQUE_SET_STRUCTS type t val toList: t -> Element.t list end structure UniqueSetRep = struct datatype 'a t = T of {elements: 'a list} end functor UniqueSet (S: UNIQUE_SET_STRUCTS): UNIQUE_SET = struct open S type elements = Element.t list structure Tree: sig structure Set: sig type t val toList: t -> elements end end = struct structure Set = struct open UniqueSetRep type t = Element.t t fun new elements = T {elements = elements} fun elements (T {elements, ...}) = elements val toList = elements end end open Tree.Set end =====

3 3

Segmentation fault when saving state
by pclayton＠taz.qinetiq.com 03 Apr '09

03 Apr '09

David, We have noticed some interesting behaviour with the state saving in Poly/ML 5.2/5.2.1--- possibly a sign that something isn't quite as intended. If poly is started and the command PolyML.SaveState.saveState "test"; is repeatedly entered, a segmentation fault eventually occurs. On my machine it always happens after 22 times. With the debug level set to 2 or 3, we get: Bad pointer 0x0d479050 found Aborted If we enter PolyML.fullGC (); just before the 22nd go, there is no segmentation fault. However, continuing to enter the original save state command results in the exception Exception- SysErr ("Out of Memory", SOME ENOMEM) raised after 8 more goes. We found this example more by chance. We have had a few other repeatable segmentation faults when saving the state but on very large examples and these are hard to reduce down. (They may be related to the above issue.) In each case, the segmentation fault could be avoided by executing PolyML.fullGC first. Generally, if we cannot create an SML script that generates an error, what is the best way to track down an issue? 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

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 April 2009