Poly/ML

polyml@lists.polyml.org

1 participants
698 discussions

fork/exec woes
by Michael.Norrish＠data61.csiro.au 06 Jun '17

06 Jun '17

Both this (with Posix.Process open): case fork() of NONE => (exece(proc,proc::args,env') handle _ => die ("Exece of "^proc^" failed")) | SOME cpid => let val (_, result) = waitpid(W_CHILD cpid, []) in result end and this: case fork() of NONE => let val () = dup2 {old = outoutfd, new = Posix.FileSys.stdout} val () = dup2 {old = erroutfd, new = Posix.FileSys.stderr} val () = dup2 {old = ininfd, new = Posix.FileSys.stdin} val () = List.app close [errinfd, erroutfd, outinfd, outoutfd, ininfd, inoutfd] in exece(executable,nm_args,env) end | SOME pid => let val out = mkTIO_instream outinfd val err = mkTIO_instream errinfd val () = List.app close [outoutfd, erroutfd, ininfd, inoutfd] in ? end seem to be causing us grief, particularly on a recent Linux, PolyML 5.7 and under conditions of some memory load. The Linux is: Linux gemma 4.9.1-gnu-1 #1 SMP PREEMPT Sun Jan 8 16:17:57 UYT 2017 x86_64 GNU/Linux When strace-d, we get a lot of futex calls and interruptions from SIGCHLD. This is with --gcthreads=1, but pages like http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-usi… make me a bit nervous about how we might be falling prey to horrible problems. Is there a better idiom we might use? Thanks, Michael

3 3

Final CFP: ML Family Workshop 2017
by Sam.Lindley＠ed.ac.uk 28 May '17

28 May '17

---------------------------------------------------------------------- CALL FOR PAPERS ML Family Workshop 2017 7 September 2017, Oxford, UK http://www.mlworkshop.org/ml2017/ (co-located with ICFP) ---------------------------------------------------------------------- ML is a family of programming languages that includes Standard ML, OCaml, F#, SML#, Manticore, MetaOCaml, JoCaml, Alice ML, Dependent ML, Flow Caml, and many others. All ML languages share several fundamental traits, besides a good deal of syntax. They are higher-order, strict, mostly pure, and typed, with algebraic and other data types. Their type systems are derived from Hindley-Milner. The development of these languages has inspired a significant body of computer science research and influenced the design of many other programming languages, including Haskell, Rust, and Scala. ML workshops have been held in affiliation with ICFP continuously since 2005. This workshop specifically aims to recognise the entire extended ML family and to provide a forum for presenting and discussing common issues, both practical (compilation techniques, implementations of concurrency and parallelism, programming for the Web) and theoretical (fancy types, module systems, metaprogramming). The scope of the workshop includes all aspects of the design, semantics, theory, application, implementation, and teaching of the members of the ML family. We also encourage presentations from related languages (such as ATS, Eff, F*, Koka, Links, Rust, Scala, Swift, etc.), to exchange experience of further developing ML ideas. Last year's ML Family workshop included talks covering eight different ML dialects and related languages: Eff, F#, F*, Links, Manticore, OCaml, SML, and SML#. The ML family workshop will be held in close coordination with the OCaml Users and Developers Workshop. Invited speaker --------------- Edwin Brady (University of St Andrews, UK) State machines all the way down A useful pattern in dependently typed programming is to define a state transition system, for example the states and operations in a network protocol, as an indexed monad. We index each operation by its input and output states, thus guaranteeing that operations satisfy pre- and post-conditions, by typechecking. However, what if we want to write a program using several systems at once? What if we want to define a high level state transition system, such as a network application protocol, in terms of lower level states, such as network sockets and mutable variables? In this talk, I will present an architecture for dependently typed applications based on a hierarchy of state transition systems, implemented in a generic data type ST. This is based on a monad indexed by contexts of resources, allowing us to reason about multiple state transition systems in the type of a function. Using ST, we show: how to implement a state transition system as a dependent type, with type level guarantees on its operations; how to account for operations which could fail; how to combine state transition systems into a larger system; and, how to implement larger systems as a hierarchy of state transition systems. I will illustrate the system with a high level network application protocol, implemented in terms of POSIX network sockets. Scope ----- We acknowledge the whole breadth of the ML family and aim to include languages that are closely related, such as Rust and Scala. Those languages have implemented and investigated run-time and type system choices that may be worth considering for OCaml, F# and other ML languages. We also hope that the exposure to state of the art ML might favourably influence those related languages. Specifically, we seek research presentations on topics including (but not limited to): * Language design: abstraction, higher forms of polymorphism, concurrency, distribution and mobility, staging, extensions for semi-structured data, generic programming, object systems, etc. * Implementation: compilers, interpreters, type checkers, partial evaluators, runtime systems, garbage collectors, foreign function interfaces, etc. * Type systems: inference, effects, modules, contracts, specifications and assertions, dynamic typing, error reporting, etc. * Applications: case studies, experience reports, pearls, etc. * Environments: libraries, tools, editors, debuggers, cross-language interoperability, functional data structures, etc. * Semantics: operational and denotational semantics, program equivalence, parametricity, mechanization, etc. Four kinds of submissions will be accepted: Research Presentations, Experience Reports, Demos and Informed Positions. * Research Presentations: Research presentations should describe new ideas, experimental results, or significant advances in ML-related projects. We especially encourage presentations that describe work in progress, that outline a future research agenda, or that encourage lively discussion. These presentations should be structured in a way which can be, at least in part, of interest to (advanced) users. * Experience Reports: Users are invited to submit Experience Reports about their use of ML and related languages. These presentations do not need to contain original research but they should tell an interesting story to researchers or other advanced users, such as an innovative or unexpected use of advanced features or a description of the challenges they are facing or attempting to solve. * Demos: Live demonstrations or short tutorials should show new developments, interesting prototypes, or work in progress, in the form of tools, libraries, or applications built on or related to ML and related languages. (You will need to provide all the hardware and software required for your demo; the workshop organisers are only able to provide a projector.) * Informed Positions: A justified argument for or against a language feature. The argument must be substantiated, either theoretically (e.g. by a demonstration of (un)soundness, an inference algorithm, a complexity analysis), empirically or by substantial experience. Personal experience is accepted as justification so long as it is extensive and illustrated with concrete examples. Format ------ The ML 2017 workshop will continue the informal approach followed since 2010. Presentations are selected from submitted abstracts. There are no published proceedings, so contributions may be submitted for publication elsewhere. We hope that this format will encourage the presentation of exciting (if unpolished) research and deliver a lively workshop atmosphere. Each presentation should take 20-25 minutes, except demos, which should take 10-15 minutes. The exact time will be decided based on the number of accepted submissions. The presentations will likely be recorded. Post-proceedings ---------------- ML 2017 is an informal workshop without proceedings. We are planning to publish a post-proceedings and to invite interested authors of selected presentations to expand their abstracts for inclusion. Coordination with the OCaml Users and Developers Workshop --------------------------------------------------------- The OCaml workshop is seen as more practical and is dedicated in significant part to OCaml community building and the development of the OCaml system. In contrast, the ML family workshop is not focused on any language in particular, is more research-oriented, and deals with general issues of ML-style programming and type systems. Yet there is an overlap, which we are keen to explore in various ways. The authors who feel their submission fits both workshops are encouraged to mention it at submission time or contact the programme chairs. Submission details ------------------ Submissions should be at most two pages, in PDF format, and printable on US Letter or A4 sized paper. A submission should have a synopsis (2--3 lines) and a body between 1 and 2 pages, in one- or two-column layout. The synopsis should be suitable for inclusion in the workshop programme. The bibliography will not be counted against the page limit. Submissions must be uploaded to the workshop submission website https://icfp-mlworkshop17.hotcrp.com/ before the submission deadline (Wednesday 31st May). If you have a question concerning the scope of the workshop or the submission process, please contact the programme chair. Important dates --------------- Wednesday 31st May (any time zone) Abstract submission deadline Wednesday 28th June Author notification Thursday 7th September 2017 ML Family Workshop Programme committee ------------------- Nick Benton (Facebook, UK) Ma?gorzata Biernacka (University of Wroclaw, Poland) Stephen Dolan (University of Cambridge, UK) Shin-ya Katsumata (Kyoto University, Japan) Julia Lawall (LIP6 Paris, France) Sam Lindley (The University of Edinburgh, UK) (PC chair) Andreas Rossberg (Google, Germany) Sukyoung Ryu (KAIST, South Korea) Gabriel Scherer (Northeastern University, US) Alley Stoughton (Boston University, US) Niki Vazou (University of Maryland, US)

1 0

Is there a Windows build that can run at the command prompt?
by cannam＠all-day-breakfast.com 11 May '17

11 May '17

That's good to know, thanks. I'm guessing this has a runtime dependency on other Cygwin or WSL libraries and can't easily be distributed standalone? I'm primarily wondering what is the most minimal possible installation that I can ask a Windows user (who probably starts without either Cygwin or WSL installed) to make, in order to make use of a script that happens to involve running an SML program. For this purpose it doesn't actually have to be a REPL, though that would be nice to have generally. Just running a program and presenting the output would be enough. Chris On Mon, 1 May 2017, at 19:12, Michael.Norrish at data61.csiro.au wrote: > Building under Cygwin or with the official Linux subsystem gives you > this. > > Michael > > On 1/5/17, 19:49, "polyml-bounces at inf.ed.ac.uk on behalf of Chris Cannam" > <polyml-bounces at inf.ed.ac.uk on behalf of cannam at all-day-breakfast.com> > wrote: > > Hello -- I'm wondering whether there is a Windows build of Poly/ML > available that can be used from a within command prompt or executed > from > a Powershell script, in the same sort of way as SML/NJ can be on > Windows, or as Poly/ML can on other platforms. > > As far as I can see the Windows distribution contains an executable > that > always opens its own window and provides its own interactive prompt, > which (although nice enough) is not quite what I want at the moment. > > Is there such a thing out there? > > Thanks, > > > Chris > _______________________________________________ > polyml mailing list > polyml at inf.ed.ac.uk > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml > >

4 13

What's the difference between "Release" and "IntRelease" ("Debug" and "IntDebug")?
by binghe.lisp＠gmail.com 08 May '17

08 May '17

Hi, May I ask, what?s the difference between "Release" and "IntRelease" ("Debug" and ?IntDebug?) configurations, in PolyML?s Visual Studio solution? I guess ?Int? means ?Internal?, but I couldn?t find any differences from the Properties of each sub-projects in Visual Studio... Regards, Chun Tian

2 2

Second CFP: ML Family Workshop 2017
by Sam.Lindley＠ed.ac.uk 08 May '17

08 May '17

---------------------------------------------------------------------- CALL FOR PAPERS ML Family Workshop 2017 7 September 2017, Oxford, UK http://www.mlworkshop.org/ml2017/ (co-located with ICFP) ---------------------------------------------------------------------- ML is a family of programming languages that includes Standard ML, OCaml, F#, SML#, Manticore, MetaOCaml, JoCaml, Alice ML, Dependent ML, Flow Caml, and many others. All ML languages share several fundamental traits, besides a good deal of syntax. They are higher-order, strict, mostly pure, and typed, with algebraic and other data types. Their type systems are derived from Hindley-Milner. The development of these languages has inspired a significant body of computer science research and influenced the design of many other programming languages, including Haskell, Rust, and Scala. ML workshops have been held in affiliation with ICFP continuously since 2005. This workshop specifically aims to recognise the entire extended ML family and to provide a forum for presenting and discussing common issues, both practical (compilation techniques, implementations of concurrency and parallelism, programming for the Web) and theoretical (fancy types, module systems, metaprogramming). The scope of the workshop includes all aspects of the design, semantics, theory, application, implementation, and teaching of the members of the ML family. We also encourage presentations from related languages (such as ATS, Eff, F*, Koka, Links, Rust, Scala, Swift, etc.), to exchange experience of further developing ML ideas. Last year's ML Family workshop included talks covering eight different ML dialects and related languages: Eff, F#, F*, Links, Manticore, OCaml, SML, and SML#. The ML family workshop will be held in close coordination with the OCaml Users and Developers Workshop. Invited speaker --------------- Edwin Brady (University of St Andrews, UK) Scope ----- We acknowledge the whole breadth of the ML family and aim to include languages that are closely related, such as Rust and Scala. Those languages have implemented and investigated run-time and type system choices that may be worth considering for OCaml, F# and other ML languages. We also hope that the exposure to state of the art ML might favourably influence those related languages. Specifically, we seek research presentations on topics including (but not limited to): * Language design: abstraction, higher forms of polymorphism, concurrency, distribution and mobility, staging, extensions for semi-structured data, generic programming, object systems, etc. * Implementation: compilers, interpreters, type checkers, partial evaluators, runtime systems, garbage collectors, foreign function interfaces, etc. * Type systems: inference, effects, modules, contracts, specifications and assertions, dynamic typing, error reporting, etc. * Applications: case studies, experience reports, pearls, etc. * Environments: libraries, tools, editors, debuggers, cross-language interoperability, functional data structures, etc. * Semantics: operational and denotational semantics, program equivalence, parametricity, mechanization, etc. Four kinds of submissions will be accepted: Research Presentations, Experience Reports, Demos and Informed Positions. * Research Presentations: Research presentations should describe new ideas, experimental results, or significant advances in ML-related projects. We especially encourage presentations that describe work in progress, that outline a future research agenda, or that encourage lively discussion. These presentations should be structured in a way which can be, at least in part, of interest to (advanced) users. * Experience Reports: Users are invited to submit Experience Reports about their use of ML and related languages. These presentations do not need to contain original research but they should tell an interesting story to researchers or other advanced users, such as an innovative or unexpected use of advanced features or a description of the challenges they are facing or attempting to solve. * Demos: Live demonstrations or short tutorials should show new developments, interesting prototypes, or work in progress, in the form of tools, libraries, or applications built on or related to ML and related languages. (You will need to provide all the hardware and software required for your demo; the workshop organisers are only able to provide a projector.) * Informed Positions: A justified argument for or against a language feature. The argument must be substantiated, either theoretically (e.g. by a demonstration of (un)soundness, an inference algorithm, a complexity analysis), empirically or by substantial experience. Personal experience is accepted as justification so long as it is extensive and illustrated with concrete examples. Format ------ The ML 2017 workshop will continue the informal approach followed since 2010. Presentations are selected from submitted abstracts. There are no published proceedings, so contributions may be submitted for publication elsewhere. We hope that this format will encourage the presentation of exciting (if unpolished) research and deliver a lively workshop atmosphere. Each presentation should take 20-25 minutes, except demos, which should take 10-15 minutes. The exact time will be decided based on the number of accepted submissions. The presentations will likely be recorded. Post-proceedings ---------------- ML 2017 is an informal workshop without proceedings. We are planning to publish a post-proceedings and to invite interested authors of selected presentations to expand their abstracts for inclusion. Coordination with the OCaml Users and Developers Workshop --------------------------------------------------------- The OCaml workshop is seen as more practical and is dedicated in significant part to OCaml community building and the development of the OCaml system. In contrast, the ML family workshop is not focused on any language in particular, is more research-oriented, and deals with general issues of ML-style programming and type systems. Yet there is an overlap, which we are keen to explore in various ways. The authors who feel their submission fits both workshops are encouraged to mention it at submission time or contact the programme chairs. Submission details ------------------ Submissions should be at most two pages, in PDF format, and printable on US Letter or A4 sized paper. A submission should have a synopsis (2--3 lines) and a body between 1 and 2 pages, in one- or two-column layout. The synopsis should be suitable for inclusion in the workshop programme. The bibliography will not be counted against the page limit. Submissions must be uploaded to the workshop submission website https://icfp-mlworkshop17.hotcrp.com/ before the submission deadline (Wednesday 31st May). If you have a question concerning the scope of the workshop or the submission process, please contact the programme chair. Important dates --------------- Wednesday 31st May (any time zone) Abstract submission deadline Wednesday 28th June Author notification Thursday 7th September 2017 ML Family Workshop Programme committee ------------------- Nick Benton (Facebook, UK) Ma?gorzata Biernacka (University of Wroclaw, Poland) Stephen Dolan (University of Cambridge, UK) Shin-ya Katsumata (Kyoto University, Japan) Julia Lawall (LIP6 Paris, France) Sam Lindley (The University of Edinburgh, UK) (PC chair) Andreas Rossberg (Google, Germany) Sukyoung Ryu (KAIST, South Korea) Gabriel Scherer (Northeastern University, US) Alley Stoughton (Boston University, US) Niki Vazou (University of Maryland, US)

1 0

Origins of Poly
by yves.cloutier＠gmail.com 03 May '17

03 May '17

Hello, I'm wondering if the language Poly had any relation to the language Poly described in the book* Polymorphic Programming Languages* by David Harland? Regards,

2 1

Is there a Windows build that can run at the command prompt?
by cannam＠all-day-breakfast.com 02 May '17

02 May '17

Hello -- I'm wondering whether there is a Windows build of Poly/ML available that can be used from a within command prompt or executed from a Powershell script, in the same sort of way as SML/NJ can be on Windows, or as Poly/ML can on other platforms. As far as I can see the Windows distribution contains an executable that always opens its own window and provides its own interactive prompt, which (although nice enough) is not quite what I want at the moment. Is there such a thing out there? Thanks, Chris

4 4

configure fails
by lp15＠cam.ac.uk 18 Apr '17

18 Apr '17

Is anybody able to build the development version of Poly/ML on a Mac? I can?t even get past the configure stage: * WARNING: Don't know the best CFLAGS for this system * * Use ./configure CFLAGS=... to specify your own flags * * (otherwise, a default of CFLAGS=-O3 will be used) * clang: error: unsupported option '-print-multi-os-directory' clang: error: no input files I would prefer to configure using --with-gmp=yes, but even a plain configure produces the messages above. Larry

2 2

5.7 Release
by David.Matthews＠prolingua.co.uk 21 Mar '17

21 Mar '17

The latest version, provisionally called 5.6.1, has had very little change for several months. I'm not aware of any show-stoppers so I think it would be a good time to make a release. Because there have been some major changes I was planning to call it 5.7. This is the last chance to do any last tests before the release. David

5 23

5.7 Release
by jrtc27＠jrtc27.com 22 Feb '17

22 Feb '17

Seems I forgot to include the mailing list; adding it back in. James > On 21 Feb 2017, at 19:14, James Clarke <jrtc27 at jrtc27.com> wrote: > > Hi David, > I just uploaded the latest version to Debian's experimental suite[1], and it seems all the interpreted versions are failing when running "make compiler". The error itself is: > >> ./polyimport polytemp.txt -I . < ./exportPoly.sml >> Use: basis/build.sml >> Use: basis/RuntimeCalls.ML >> Use: basis/InitialBasis.ML >> Exception- Match unexpectedly raised while compiling > > Further up in the build logs there is: > >> Making INTGCODE >> mlsource/MLCompiler/CodeTree/ByteCode/INTGCODE.ML:167: warning: Matches are not exhaustive. >> Found near >> case pt of >> BICEval evl => genEval (evl, tailKind) | >> BICExtract ext => if whereto = NoResult then () else locaddr ext | >> BICField {...} => (... ...; ...) | >> ... ... => ... ... | >> ... => ... | >> ... > > > Looking at the source, BICArbitrary is not handled (though there may be others). > > Regards, > James > > [1] Logs at https://buildd.debian.org/status/package.php?p=polyml&suite=experimental > >> On 21 Feb 2017, at 12:48, David Matthews <David.Matthews at prolingua.co.uk> wrote: >> >> The latest version, provisionally called 5.6.1, has had very little change for several months. I'm not aware of any show-stoppers so I think it would be a good time to make a release. Because there have been some major changes I was planning to call it 5.7. This is the last chance to do any last tests before the release. >> >> David >> _______________________________________________ >> polyml mailing list >> polyml at inf.ed.ac.uk >> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml >

2 1

← Newer
1
...
11
12
13
14
15
16
17
...
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