I've been away for the last week or so since releasing version 5.2 and
there have been a few emails about various issues. Rather than deal
with each individually I'm responding to all of them together.
I have installed polyml 5.2 (sources) under
MacOSX 10.4.* and 10.5.*. Both times I had
to m
Matthew Fluet wrote:
* One bug with the implementation of Real.fromDecimal (which also affects
Real.scan and Real.fromString) in PolyML 5.2. The string_buffer[30] in
Real_convc in /libpolyml/reals.cpp limits the length of the string
seen by strtod to 29 characters. However, the constructi
Michael Norrish wrote:
The error is not in the ML. Each time any of these is run, I see the
final "Done". However, a high proportion of the time (33% perhaps),
my shell (standard Debian bash) aborts the execution of the process.
For example, with the echo "use" piped to poly, I get
...output
Lucas Dixon wrote:
Perhaps this is something to do with my failure to understand unix
pipes, but the following confuses me...
However, the following misbehaves:
echo 'fun loopy () =
let val sopt = TextIO.inputLine(TextIO.stdIn);
in case sopt of SOME s => (print s; loopy ())
Timothy Bourke wrote:
I've just had some time to test the new version on FreeBSD (6.3-RELEASE).
On Jun 3 at 15:14 +0100, David Matthews wrote:
Changes to handling of signals by the Signal structure. Rather than
forking a new thread to process each signal there is a single thread
Rob Arthan wrote:
David,
However, while I agree that my "fix" is a hack because it's working around
what looks like a bug in the old glibc, I am a little concerned that your
signal handling design is not POSIX-conformant. The POSIX specification of
sigaction includes the following statement:
Achim D. Brucker wrote:
using a recent g++ version for compiling Poly/ML results in several
warnings of the following form:
xwindows.cpp: warning: deprecated conversion from string constant to 'char*'
The warning is caused by implicit conversion from string constants
(i.e., "foo") to non-cons
Rob Arthan wrote:
I am working on porting ProofPower to Poly/ML 5.2. I get the following
assertion failure when I run one of the tests for my parser generator. I can
reproduce the problem deterministically, but the circumstances in which it
occurs are obscure: at first glance it seems to depend
Lionel Elie Mamane wrote:
Background: Achim Brucker and myself are packaging Poly/ML for Debian.
That's good. Thank you both for doing that.
I noticed that:
1) Compilation of file libpolyml/xwindows.cpp with gcc 4.2.3 gives
several instances of:
warning: dereferencing type-punned poi
Philip Clayton wrote:
I have found a performance issue when using TextIO.StreamIO.input1 to
read a functional stream. Looking at gc/non-gc times and using
PolyML.profiling, it appears that garbage collection accounts for most
of the time. There is some code below to demonstrate with stats tha
Makarius wrote:
I am working with named pipes to output large amounts of text to an
external process. Looking at the sources of basis/TextIO.sml etc. I've
got the impression that pipes are always line-buffered. Is there an easy
way to get block-buffering?
Currently TextIO.openOut sets lin
Philip Clayton wrote:
I have found a performance issue when using TextIO.StreamIO.input1 to
read a functional stream. Looking at gc/non-gc times and using
PolyML.profiling, it appears that garbage collection accounts for most
of the time. There is some code below to demonstrate with stats tha
I've now released version 5.2.1 of Poly/ML on the SourceForge site.
This is largely a bug-fix release of 5.2 and incorporates various fixes
to the run-time system and basis library. I'll update the release notes
on the web site with details of the bug fixes. The functional IO
library has been
Philip Clayton wrote:
Thanks for the new version. Just in case it was unintentional, I
thought I should let you know that the .tar.gz file contains a directory
'polyml', rather than 'polyml.5.2.1' as has been the convention for
previous releases.
Thanks for pointing that out. It was uninten
Philip Clayton wrote:
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
lo
Alexander Krauss wrote:
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
shou
Tom Ridge wrote:
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
Phil,
The idea of loadState is to be able to load information saved in a
previous session and it doesn't always work as expected when you reload
the state into the session that saved it. That isn't something I
imagined someone wanting to do.
loadState restores the values of references in the
Michael Norrish wrote:
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 would suggest using PolyML.showSize. This displays the actual
contents of an arbitrary data structure in hex and includes the
addre
Phil,
Philip Clayton wrote:
My understanding of loading a state is that new objects are created
whether or not the same object is already loaded. That seems the right
thing to do, as you say. When loading a child state however, I would
expect only objects in the child state to be created and
Rob,
The current saveState/loadState saves and restores the whole "state".
It works at the level of the memory and has no knowledge of what the
values represent. When you load "test2.polydb" this simply restores all
global references to the values they had when you saved the state. In
partic
Thanks, Phil. I've fixed it in CVS and added these tests to my
regression tests.
David
Philip Clayton wrote:
In my ignorance I wrote my own exponentiation function for infinite
integers, only to find IntInf.pow exists in the basis. Anyway, I ran my
test cases on IntInf.pow but they didn't al
Phil,
I've now looked into this and hopefully fixed it in CVS.
saveState gets a new segment of memory from the system each time it is
called and copies everything that is reachable from the root into that.
As well being written out the segment needs to be retained as a whole
since if a child
There have been a couple of updates to the Poly/ML CVS repository
recently apart from those already mentioned on the list. They are both
in the C++ run-time system.
The mechanism for waiting for external events has been improved which
mainly affects Windows pipes and processes. In particular
Lucas Dixon wrote:
is the code for the substructure n1 literally getting copied each time?
Even with this I find it hard to imagine how I'd generate 120 MB of
machine code from 7500 lines of ML...
I noticed some forget functions in the PolyML compiler; is there some
clever way to say all I care
Lucas Dixon wrote:
Some answers to my own questions...
saves only 1MB, despite the fact that I have many deeply nested functors
in my code. Changing the max inline depth also seems to have pretty much
no change on the size of generated code so now I still wonder how I
got 20MB of compiled co
Rob Arthan wrote:
I have just learnt a few things installing Poly/ML on a Ubuntu 8.04 system
freshly built from the Desktop CD:
1) Ubuntu comes out of the CD with 3/4 of a C compiler. You get gcc, but not
libc, so you can compile hello-world.c but not link or run it. The configure
script noti
CVS is getting rather old now and most projects seem to have moved on.
I've now moved Poly/ML's CVS repository to subversion and taken the
opportunity to enable Trac on the SourceForge site.
To download the development version you need
svn co https://polyml.svn.sourceforge.net/svnroot/polyml/tr
Basile STARYNKEVITCH wrote:
David Matthews wrote:
CVS is getting rather old now and most projects seem to have moved on.
I've now moved Poly/ML's CVS repository to subversion and taken the
opportunity to enable Trac on the SourceForge site.
To download the development version you n
nitralime wrote:
I am trying to compile PolyML 5.2.1 on AIX 5L. After executing configure
script "./configure --prefix=/usr/local/polyml"
and "gmake" I got the following error message:
g++ -DHAVE_CONFIG
nitralime wrote:
On Mon, Mar 23, 2009 at 6:55 PM, David Matthews <
I don't know how time consuming the implementation of XCOFF support would
be.
Excuse me my naive question: Is there any plan to implement it?
None at the moment. It shouldn't be a great deal of work especiall
Philip Clayton wrote:
I must say that when I was setting up the test running 5.2.1 and the
latest version side by side, I found it particularly difficult to know
what version of Poly/ML I was actually running! I currently work with
5.2, 5.2.1 and, now, the latest but all three report '5.2' on
Rob Arthan wrote:
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
Matthew Fluet wrote:
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.
I'm doing quite a bit on the compiler at the
Makarius wrote:
Anyway, now that you have the tracker enabled at the sourceforge site,
do you prefer that channel, or shall we continue with plain email?
(Right now there is only a single open/unassigned item on the tracker by
myself.)
Phil Clayton asked the same question in a private email a
Rob,
Rob Arthan wrote:
Thanks for that. I wasn't seriously expecting to get portabiliity between
Linux and MacOS. If I understand you aright, all calls out from compiled ML
code go in the saved state go via the ABI offered by libpolyml.so, so if the
OS is prepared to load my executable it will
Robert,
Thanks for your comments. I'm replying to your comments about memory
size separately since that applies as much to Unix as to Windows.
Robert Roessler wrote:
The 2 errors are just from using the newer dev environment: the _osver
variable is no longer available. So, the 2 usages (line
Robert Roessler wrote:
The execution issue happens early in the "Custom Build Step" use of
PolyImport.exe: during startup, the polymain(...) function obtains the
size of installed physical memory, and then defaults to using half of it.
IMHO, this logic could use a new look, given modern system
Robert Roessler wrote:
I am the author of the OCaml plugin for the Scintilla editing component,
and would like to adapt it for Poly/ML (ML97)... while the changes
needed are largely obvious (different keywords, changed/added token
types, etc), I have two really basic questions:
That sounds re
Makarius wrote:
On Fri, 19 Jun 2009, David Matthews wrote:
We're not yet at the point of releasing this although much of the code
is in SVN so it is possible to try it out. A major issue we're
struggling with is exactly what constitutes a "project". For other
language
David Matthews wrote:
Robert Roessler wrote:
The execution issue happens early in the "Custom Build Step" use of
PolyImport.exe: during startup, the polymain(...) function obtains the
size of installed physical memory, and then defaults to using half of it.
This issue comes up with
Having tried out Trac on SourceForge I've now disabled it. The problem
is that SourceForge does not provide access to the configuration file
necessary to add notification email addresses so it wouldn't be possible
to know that a bug had been posted without checking the site. The
SourceForge b
Robert Roessler wrote:
I mentioned here recently that I was working on updating my Scintilla
plugin for OCaml to also support Standard ML - and it is now "done"(*).
It looks very nice. I've just been trying it out.
Perhaps I am missing something, but it looks like Poly is all about an
intera
I've just been updating the type checking error messages for fun
declarations and as part of the process I've been looking at the
parsing. The syntax of a fun binding is similar to a pattern in many
ways and the overlap between them is such that the easiest way to parse
them is to treat them j
Rob Arthan wrote:
We have performance problems with ProofPower when compiled with Poly/ML using
the latest sources as compared with version 5.2.1. The main problem is with
loading a large state. In some of QinetiQ's tests, it now takes nearly 40
minutes to load a state (occupying about 150Mb on
Robert Roessler wrote:
This could still potentially be handled by a C-style interface, if we
could optionally associate a C "finalize" function with a volatile -
this function could be called by the Poly memory reclamation when the
volatile is truly unreachable; upon its return, Poly can go ahe
Robert Roessler wrote:
It seems like it could be useful. It isn't possible to run ML code while
actually doing the garbage-collection so it would be necessary to record
that a vol was due to be deleted and then call the finaliser at some
point later on. That, of course, raises the question of whi
Rob Arthan wrote:
On 26 Jul 2009, at 19:37, David Matthews wrote:
Rob Arthan wrote:
We have performance problems with ProofPower when compiled with
Poly/ML using the latest sources as compared with version 5.2.1. The
main problem is with loading a large state. In some of QinetiQ's
test
Philip Clayton wrote:
I have rebuilt ProofPower using this file and the times to start up are
back to normal. I've set a build going to test the 150MB databases but
won't know the outcome until tomorrow. This is looking good so far...
Good. I've committed that change. It looks like it has
Robert,
I thought that it would be quicker and easier to implement this myself
rather than try to explain what to do. Try it out and let me know if it
does what you want. I've extended the example in the
mlsource/extra/CInterface/Examples directory to include a test.
Regards,
David
_
Robert Roessler wrote:
David Matthews wrote:
I thought that it would be quicker and easier to implement this myself
rather than try to explain what to do. Try it out and let me know if it
does what you want. I've extended the example in the
mlsource/extra/CInterface/Examples directo
Last week I committed into SVN the last major piece of some changes I've
been making to the modules implementation. There are a lot of detailed
changes but this last bit involves a change to way structures and
functors are implemented. Previously, whenever a signature was used it
was complete
Philip Clayton wrote:
When using SaveState.saveChild to save the state, I am getting:
Timing - parse:0.0, semantics:0.0, translate:0.0, generate:0.0, run:43.7
Exception SysErr: SysErr ("Out of Memory", SOME ENOMEM) raised
Even after shareCommonData and fullGC I notice that
objSize rootFunct
the
lexing of a block of text that was several MB, I think approx 4-5 MB. I
would imagine that the particular reader/lexer (part of ProofPower/DAZ)
was just building up a very deep structure.
Thanks,
Phil
David Matthews wrote:
Phil,
It looks to me as though there is some very deep data stru
1) I had it so that "finalisation" was only possible with NON-owned
vols, while your approach potentially allows Poly to use this feature
now also.
Well, the vol that has the finaliser actually is an owned vol. That's
because the C_pointer field contains the address of a malloc'd area that
holds
Rob,
All I can say is that it works for me with 5.2.1 downloaded from
SourceForge and the most recent update of Cygwin.
Make sure that you have an up-to-date version of Cygwin.
Try running
./polyimport -H 10 polytemp.txt < exportPoly.sml
and see if you get any other error messages.
Regards,
D
Rob,
A quick look with Google suggests that error 53 is a missing DLL. Try
building a statically linked version:
make distclean
./configure --disable-shared
make
cygcheck ./polyimport.exe
and you should get something like
.\polyimport.exe
C:\cygwin\bin\cygwin1.dll
C:\WINDOWS\system32\ADVA
I fixed a bug recently [831] where I'd reorganised some code and the
wrong identifier was being picked up. It would have been immediately
apparent if the compiler had detected that an identifier was
unreferenced so I've now added that check. In the current SVN version
identifier checking is o
Rob,
Considering then ML semantics is so carefully defined the syntax is
really a mess. There are lots of informal comments which make it really
quite difficult to understand exactly what is allowed and what is not.
The ML90 definition says "For each value binding pat = exp within rec,
exp m
Rob Arthan wrote:
I have a problem building ProofPower with the latest Poly/ML. The build
goes into a loop at a point where it opens a certain structure. This
will be the first time Poly/ML has had to pretty-print a value of the
type THM that represents theorems. This type has a circularity pas
Rob,
Rob Arthan wrote:
Previously, the code checked whether there was circularity and just
printed "..." when it detected it. That's not really possible with the
current code so it relies on the print depth (PolyML.print_depth) to
stop infinite looping. Setting print_depth to 10 in your example
Hi Gabriel,
Gabriel Dos Reis wrote:
I tried to build Poly/ML on Windows using the MSYS/MinGW toolchains, but
was unsuccessful The build failed with:
This is an out-of-source build, meaning that I keep the build directory separate
from the vanilla Poly/ML source tree. I had a quick look fo
Gabriel Dos Reis wrote:
On Fri, Sep 4, 2009 at 3:49 AM, David
Matthews wrote:
Doing an out-of-source build won't currently work. You may be able to build
the library but compiling the basis library into Poly/ML assumes that it is
running within the directory that contains the sources.
Gabriel Dos Reis wrote:
I'm using the latest MinGW/MSYS releases, with full developer toolsets. On my
machine (Windows XP, 32-bit), the header is located under /ming/mingw32/include.
The in-source build indeed is now OK. Thanks!
The out-of-source build still fails for libpolyml. Now, it is
r...@lemma-one.com wrote:
My first attempt to compile Poly/ML 5.2.1 on Snow Leopard (= MacOS X 10.6)
resulted in an error due to a cast of a pointer to an int in
libpolyml/x86_dep.cpp. There is a fix for this in the latest source, but
the build then falls over as follows:
Rob,
I had an email ab
Peter,
Are you subscribed to the Poly/ML mailing list? Rob Arthan has also
been asking about this and it makes sense that everyone is aware of the
various issues. I'm copying this to the list as well.
Rob also found that
./configure --build=x86_64-darwin LDFLAGS='-segprot POLY rwx rwx'
worke
Rob,
r...@lemma-one.com wrote:
If I do:
./configure --build=x86_64-darwin
then make works, but make cvs then fails like this:
make all-recursive
Making all in libpolyml
make[2]: Nothing to be done for `all'.
Making all in libpolymain
make[2]: Nothing to be done for `all'.
make[2]: Nothing to
Just a further update on this: the problem seems to be the config.guess
script which reports that this is a 32-bit processor rather than a
64-bit one. I've updated to the latest version from the master version
at git.savannah.gnu.org but I'm not sure that this fixes it. I came
across a propos
Rob,
r...@lemma-one.com wrote:
It may be possible to force 32-bit mode with
./configure CFLAGS='-arch i386 -O3' CXXFLAGS='-arch i386 -O3' \
CCASFLAGS='-arch i386'
Did you try with the CXXFLAGS option as well? From what I can tell
CFLAGS is only used in C
programs not in the C++ parts such a
Rob,
Yes, I removed PolyML.Compiler.printTypesWithStructureName. 5.3 does a
much better at trying to detect exactly what path is needed to identify
a type and always tries to produce the minimal path. This isn't always
easy or possible in the presence of sharing, type abbreviations and type
Rob,
Can I take it that the current SVN builds on Mac OS 10.6 without any
extra options, although your Makefiles will have to add the -segprot
option? I may need to ask you test it again if the official
config.guess is updated to include support for 10.6.
Eventually I'd like to remove the ne
Rob,
Thanks for cutting that down into something manageable. I've now fixed
it. I'd forgotten about the case of an overloaded type when generating
equality functions. There doesn't appear to be any overloading in your
example until you look very closely and realise that "1" is actually
over
Rob Arthan pointed out that the new behaviour in 5.3 of printing
abstract types isn't always desirable and that it might be useful to
explain how to restore the old behaviour. I've added an entry to the
FAQ http://www.polyml.org/FAQ.html#defaultpretty which includes
instructions on how to inst
Makarius wrote:
The paragraph says "This can be included within the abstract type or
outside it." According to what you have explained to me earlier, it
actually depends if opaque signature matching is involved.
Here is a refined example:
structure Test :>
sig
type T
val x: T
except
Makarius wrote:
On Wed, 16 Sep 2009, Makarius wrote:
On Wed, 16 Sep 2009, David Matthews wrote:
To be honest, when I think of an abstract type I think of the abstype
construction rather than opaque signature matching.
Interestingly, opaque signature matching also causes problems in
SML/NJ
Peter Vincent Homeier wrote:
With a completely fresh copy of the developer version, obtained by
svn, I try to build Poly/ML in a 32-bit version under the latest
version of Snow Leopard (OS X 10.6.1) by
cd polyml/polyml
./configure CFLAGS='-arch i386 -O3' CXXFLAGS='-arch i386 -O3'
CCASFLAGS='-arc
We're approaching the stage of releasing 5.3 so I'd like to encourage
everyone to test the SVN version especially if you have a large
code-base. The changes to the handling of type identifiers and modules
could have introduced bugs and several have been fixed during testing.
Don't forget to ru
Thanks Andras, I'd made a few minor changes to x86 code-generator and
not modified the PPC and Sparc versions to keep them in sync. I've now
committed changes that seem to work for me.
Regards,
David
Andras Pahi wrote:
Hi,
I just checked out revision 879 from SVN.
The 'make compiler' targe
Matthew Fluet wrote:
There appears to be a bug with datatype replication when the
to-be-replicated type is brought into scope by an open.
[fl...@shadow tmp]$ poly
Poly/ML 5.3 Release candidate 1
structure S1 = struct open Date datatype t = datatype weekday end;
Exception- InternalError: codeV
Rob,
Rob Arthan wrote:
As I am not using the X Windows support at the moment, everything is OK for me
on Snow Leopard with Poly/ML at revision 881. However, configure is still not
recognising that X is present as we discussed in:
http://lists.inf.ed.ac.uk/mailman/private/polyml/2009-September
Rob,
It says "xmkmf: command not found", which certainly explains the problem. It
is a bit surprising that xmkmf is not there, but I don't know whether that's
a a general problem with X on Snow Leopard or not. I did have to reinstall X
at least once because the first time it (apparently) sile
Rob,
David Matthews wrote:
It says "xmkmf: command not found", which certainly explains the
problem. It is a bit surprising that xmkmf is not there, but I don't
know whether that's a a general problem with X on Snow Leopard or not.
I did have to reinstall X at least on
Peter Vincent Homeier wrote:
Upon updating the svn repository for Poly/ML to revision 885, I then ran
make distclean
./configure --build=x86_64-darwin LDFLAGS='-segprot POLY rwx rwx'
make
which generated the following transcript:
make all-recursive
Making all in libpolyml
/bin/sh ../libtool -
Rob,
Rob Arthan wrote:
Revision 887 compiles fine on Snow Leopard with just --prefix specified
on the configure command, but it is still not detecting X Windows.
Since I don't have access to a machine where I can really test any
further at the moment this I would prefer to leave this. I ca
Matthew Fluet wrote:
I'm encountering an unexpected (and presumably buggy) type error when
compiling the MLton sources with Poly/ML r883. I am able to compile the
MLton sources with Poly/ML 5.2.1 (and also MLton and SML/NJ), so I'm
fairly certain that the code is type correct. Unfortunately
Phil,
Thanks for pointing that out. I'd completely missed it. I suspect that
it was something added after the draft version that I worked from when I
did the original implementation. I've fixed it now. When the RTS
generates a SysErr exception it uses the errorMsg string if the second
argu
There's been a problem with the multiprocessor code in Poly/ML on the
Sparc and I've traced this to some hand-coded assembly code. The
problem is that v9 processors appear to require memory barrier
instructions in the atomic increment and decrement instructions but
these instructions aren't im
Michael Norrish wrote:
The attached causes the following error message, after doing a
poly < simple.sml
Poly/ML 5.3 Release candidate 1
# # # ... # # Error-Type error in function application.
Function: = : ''a * ''a -> bool
Argument: (v, w) : ''a * hol_type
Reason: Can't unify ''a
Thank you to everyone who reported bugs (or successes) in RC1. There
have been quite a few fixes as a result and now everything that I'm
aware of has been fixed. I have upped the version string to RC2 so this
is the last chance to check that everything is working before the release.
I've made n
Rob,
Rob Arthan wrote:
RC2 is working fine for ProofPower. I am testing on Snow Leopard using
SVN rev 924 of the Poly/ML source. I tried both x86_64 and i386
architectures - to get the latter work you still seem to have to specify
CXXFLAGS etc. I see that configure is still using xmkmf to test
Rob,
Rob Arthan wrote:
RC2 is working fine for ProofPower. I am testing on Snow Leopard using
SVN rev 924 of the Poly/ML source. I tried both x86_64 and i386
architectures - to get the latter work you still seem to have to specify
CXXFLAGS etc. I see that configure is still using xmkmf to test f
I've now released Poly/ML version 5.3 on the SourceForge site. As well
as the usual source code I've also built a Windows installer script that
will install a binary version on Windows. The release notes are at
http://www.polyml.org/docs/ReleaseNotes.html which describe what's new
in this releas
Rob,
Rob Arthan wrote:
David,
Out of interest, I have tried this and it compiles OK. However I think
that multi-threading is causing a problem with it. If I execute:
val shell = Motif.XtAppInitialise "" "HelloWorld" "HW" [] [];
val btn = Motif.XmCreatePushButton shell "hello-btn" [
Andreas Schropp wrote:
im an Isabelle Developer, wondering about the details of profiling 1&2:
* what happens if another thread is executing while profiling is active
for a selected thread (lets say by calling profile 1 f x in Isabelle)?
In the resulting profile it looks to me like profiling d
Andreas Schropp wrote:
Are there plans for profiling concurrent programs or even interactions
of threads?
Makarius and I have discussed more detailed instrumentation of
concurrent programs but so far nothing has been implemented. It
requires some sort of graphical performance monitoring rath
Peisen Yang wrote:
The error I got by using the Source Release is in the attachment.
"./configure" was seems fine, then sudo make and sudo make install I got
errors(The reason why I add sudo is I saw some privilege error when without
sudo)
Please help me to find out why:)
/u
Just to provide a bit more information: although this is an academic
paper it may be of interest to users of Poly/ML. There are some details
about the implementation of multi-threading in Poly/ML and descriptions
of the "futures" code in Isabelle that Makarius wrote on top of the
Thread struct
I don't want to discourage you but you've asked some rather basic
questions along with some more advanced ones. You might benefit from
looking at a book on the language. I'll try to give a quick answer to
your questions.
Question 1: get error when run "open XWindows"
"Error
I've set up a branch in SVN to contain fixes to the current release.
I'm intending to limit this to problems that have been found since the
release which actually affect people. Other problems will be fixed in
trunk and included in the next release. So far I've applied the fix to
the problem
Rob,
I think the problem is actually with the wrapper function that is used
to emulate install_pp in terms of addPrettyPrinter. When I wrote a
version of your pretty printer directly in the new form (included below)
it worked as expected. I've now written a quick document describing the
new
1 - 100 of 700 matches
Mail list logo
