Poly/ML

polyml@lists.polyml.org

695 discussions

Interpreter commands?
by dtopham＠ohlone.edu 17 Jul '15

17 Jul '15

Are there commands for the PolyML interpreter to do things list the values in the current environment? e.g. If I have loaded or defined several functions and then want to review them as reference to calling them correctly, is there a way to display their prototypes? (I did look through the documentation and tried to search the "archives" but I don't seem to have a search feature for that purpose) -Dave p.s. I did discover the use of rlwarp (on Linux) to solve the problem of not being able to use arrow keys within the interpreter--that is a nice addition for repeating previous commands. i.e. rlwrap poly

2 1

PolyML on AArch64
by chneukirchen＠gmail.com 13 Jul '15

13 Jul '15

Hi, I have added 64-bit ARM support for PolyML, using the interpreted mode. It seems to be enough to natively compile and run the test suite completely. Tested on Linux voidarm64 3.16.0-37-generic #51-Ubuntu SMP Tue May 5 13:51:19 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux

2 2

polyml 64bit Darwin heap size
by Gerwin.Klein＠nicta.com.au 17 May '15

17 May '15

Hi, I?m running into problems with large heap sizes on 64bit Darwin. The machine I?m running on has 32GB physical memory, and runs out of polyml memory on sessions that take about 12GB on 64bit Linux. The error message is val it = (): unit ML> Exception- SysErr ("Cannot allocate memory", SOME ENOMEM) raised (This is from an Isabelle build of the image CBaseRefine in https://github.com/seL4/l4v/tree/master/proof) The initial heap size was specified as ?-H 2000?. Playing around with that option, I got for instance for ?-H 8000? the message: "Value of -H option is too large" I?m getting the same for trying to increase ?maxheap. The same -H 8000 option on a 64-bit Linux machine works fine. The check that throws this error seems to be: libpolyml/mpoly.cpp:177 // Check that the number of kbytes is less than the address space. // The value could overflow when converted to bytes. if (result >= ((POLYUNSIGNED)1 << (SIZEOF_VOIDP*8 - 10))) Usage("Value of %s option is too large\n", arg); As far as I can see, config sets the value of SIZEOF_VOIDP to 8 on both platforms, so I?m a bit mystified why one works and the other doesn?t. The polyml version is 5.5.2 (-3 in the Isabelle distribution, but same problem for vanilla 5.5.2). Any ideas? Cheers, Gerwin ________________________________ 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.

1 1

polyc and poly --script
by rene.neumann＠in.tum.de 24 Mar '15

24 Mar '15

Hi, two completely orthogonal questions/remarks for PolyML 5.5.1: 1.) When building PolyML with '--with-system-libffi' the '-lffi' part is missing in the linker line in polyc. 2.) Is it somehow possible to see if an ML file is run via 'poly --script' or as a standalone executable? Because for the one the logic has to be wrapped in 'fun main ()', and for the other it should not :). (Ie, what I want: if is_script then main() else () ) Thanks, Ren? -- Ren? Neumann Institut f?r Informatik (I7) Technische Universit?t M?nchen Boltzmannstr. 3 85748 Garching b. M?nchen Tel: +49-89-289-17232 Office: MI 03.11.055

4 9

emacs SML mode
by dm＠prolingua.co.uk 20 Mar '15

20 Mar '15

Peter, I'm copying this to the Poly/ML list as you suggested. It would be nice to have SML emacs mode working with Poly/ML for those who would like to use it but my feeling is that it is rather old-fashioned. Poly/ML now supports a much more extensive interface designed for an IDE. The best example of this is Isabelle's ML mode. See http://sketis.net/2014/isabellepide-as-ide-for-standard-ml which has a nice screen-shot. Lucas Dixon and I both had a go at producing IDEs which were completely independent of Isabelle but we didn't get as far as Makarius has. It all works by having the Poly/ML compiler as a function which takes a large set of parameters most of which have simple defaults. All the interaction with the compiler is through ML functions. The default REPL just calls the compiler with streams connected to the console but it's very easy for a user to replace the REPL with something else. The Isabelle IDE is just using the Poly/ML compiler function but passing in parameters which capture error messages and also allow browsing of the parse-tree to get information about the types. So far the debugger hasn't been fully integrated with this but it's something I have in mind. The format that the default REPL uses for error messages was one that was used by various compilers at one time and it used to be possible to parse it automatically. If there's a more up-to-date format I'm happy to change to it. I don't know if anyone is parsing the current format automatically and would be inconvenienced by a change. David On 03/12/2014 03:26, Peter Gammie wrote: > Dave, > > I?ve been talking to Stefan about the SML mode for emacs that he > maintains. I?m hoping to use it with Poly/ML and it is starting to > come together. > > Stefan observed that it would be super-helpful if Poly/ML generated > errors in a standard format, such as e.g. the one that GCC or clang > use, as far as that makes sense. > > Would you be open to that? I could try to crank out some patches to > Poly/ML if so. > > BTW I am wondering how people interact with Poly/ML?s repl. With more > hacking it is likely to be somewhat emacs-friendly, but I?m still > struggling to understand how people have done it in the past. > > For instance, I presently more-or-less just load all modules into > poly with a series of ?use?s in dependency order. Now I?d like to use > the debugger and it seems I have to hack all this scaffolding to do > so. From the looks of it Isabelle does the same. > > Feel free to reply via the Poly/ML list if you prefer. > > Thanks for the awesome system. I hope I can make some use of the > concurrency! > > thanks, peter >

9 17

forgetVal(ue)
by peteg42＠gmail.com 15 Mar '15

15 Mar '15

David, I?ve been trying to repurpose your Poly/ML test harness, that encapsulates the tests in private namespaces. With some head scratching I got it to somewhat work, so thanks for that. One remaining nit is that the treatment of forgetVal(ue) does not take into account the current namespace. Did you have a reason for leaving it out of the PolyML.NameSpace.nameSpace record? cheers, peter

2 1

Typo in Socket.select
by hiroya.ebine1＠gmail.com 11 Mar '15

11 Mar '15

In Poly/ML source code, polyml/basis/Socket.sml, Socket.select function declared like this: val select: { rds: sock_desc list, wrs : sock_desc list, exs : sock_desc list, timeOut: Time.time option } -> { rds: sock_desc list, wrs : sock_desc list, exs : sock_desc list } But, basis library says: select {rds, wrs, exs, timeout} (http://sml-family.org/Basis/socket.html#SIG:SOCKET.select:VAL) It seems a typo. Argument "timeOut" shoud be "timeout". Please fix it or tell me where post a patch. Sorry for poor english. Thank you.

2 1

Debugging the debugger
by Brian.Campbell＠ed.ac.uk 07 Mar '15

07 Mar '15

Hi, I've encountered a few bugs when using the debugger, and I've managed to distill them down into a useful form. The first is that the compiler is too keen to avoid multiple calls to the debugger in one line. For example, if I debug the function below, 1 fun f n = 2 let val l = [1,2,3,4] 3 val x = map (fn y => y+n) l 4 in x 5 end then stepOver() will skip line 3, because the compiler places the only call to the debugger inside the anonymous function. I've been working around this by adding an extra newline after map. The second is that when support was added to stop execution when an exception is raised, it used the same code as when an exception exits a function, and pops an extra entry off the debug stack. The stepOver and stepOut functions get very confused as a result. I've hacked my copy to check whether the name ends in -raise before popping the stack, but there's probably a more elegant solution. Finally, the tracing doesn't seem to like datatypes declared inside structures: structure S = struct datatype t = A of int fun f (x:t) = x; end; > PolyML.Debug.trace true; val it = (): unit > S.f (S.A 5); S.f Exception- Subscript raised I can examine the value of x in the debugger, though, but my attempts to make the way tracing prints values more like the debugger toplevel haven't been successful. Best regards, Brian

2 1

extremely bad performance on some mllex generated code
by michael.norrish＠nicta.com.au 03 Mar '15

03 Mar '15

(I'll attempt to attach the tgz file to this message, but if 817KB is too big and this bounces or the attachment is dropped, I'll make it available separately.) If compiled with Poly/ML, the attached program performs abysmally on the provided testcase.sml input file. Within seconds of beginning, it attempts to allocate more memory than my machine has (16GB), and basically brings it to its knees. If compiled with mlton, the testcase doesn't seem to cause any obvious memory allocation, and finishes in less than a second. You can also compile with Moscow ML, though I haven?t included the build instructions in the Makefile. The execution of the mosml executable doesn't seem to allocate any memory either, and it terminates cleanly (after 17s). Though slow this is still preferable to Poly/ML's behaviour. This is with Poly/ML 5.5.2 on > Linux telemachus 3.2.0-75-generic #110-Ubuntu SMP Tue Dec 16 19:11:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The Makefile generates two executables (if you have mlton and poly in your PATH): pholdeptool and mholdeptool. You can run them on the testcase, e.g.: pholdeptool testcase.sml The lexer code looks to me to be tail-recursive, and the program only accumulates a binary tree containing 15 strings. So it really does seem as if Poly/ML is doing something buggy. (The program is lexing the test-case (which uncompresses to a 30MB file) in an extremely simple way, but performing a useful analysis.) Michael

2 3

Lexical analyser bug?
by rda＠lemma-one.com 24 Feb '15

24 Feb '15

I mistyped a word constant and was a bit surprised by the error message. rda]- poly Poly/ML 5.5.2 Release > 0xw9; Error-malformed integer constant: 0w Static Errors Contrast this with SML/NJ: rda]- sml Standard ML of New Jersey v110.76 [built: Mon Mar 3 16:26:20 2014] - 0xw9; stdIn:3.2-3.5 Error: unbound variable or constructor: xw9 stdIn:3.1-3.5 Error: operator is not a function [literal] operator: int in expression: 0 <errorvar> With the following contrived example: fun f x y = print "Boo!" val xw9 = "xw9"; f 0xw9; Poly/ML reports a syntax error while SML/NJ and mlton both print Boo! I am not sure who is right about this. Regards, Rob.

4 4

← Newer
1
...
21
22
23
24
25
26
27
...
70
Older →

Jump to page:

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