David Matthews wrote:
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 co
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 both Unix
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
languages and IDEs there's a clear distinction b
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
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:
...
After this, I may well be interested in the IDE work mentioned for 5.3
(if there is still anything to do) - I have read the "IDE Communications
Protocol" doc, so that at least suggests where you may be going on this.
That didn't come out right - I am not suggesting th
David Matthews wrote:
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,
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
I have recently downloaded the PolyML 5.2.1 archive and built it on my
4GB Vista x64 SP2 box, feeding the supplied Visual Studio workspace to
my VS 2008 SP1 dev environment.
This went quite well, with only 2 build errors and one execution problem
stopping the entire bootstrapping process! :)
