kground: Currently we are just
running ECL in a single thread, since Maxima was not really designed for
multi-threaded use anyway.
Additionally, if someone thinks other options than the ones above are more
appropriate I would be interested in hearing about them as well.
On Sat, 26 Feb 2011, Juan Jose Garcia-Ripoll wrote:
> In the window from the signal handler swap until ECL is booted, ECL will
> simply discard all signals, because the signal queue is not installed and
> ECL is not marked as booted. Or do you perform the swap every time that ECL
> code is execute
The following problem arises with ECL as packaged within Sage. Sage comes
with essentially its own $SAGE_ROOT/usr/local/ tree and tries to ensure
that the whole install directory of sage can be moved and that sage still
runs OK in the new location.
This works for most of ECL, but not for its co
I am having some trouble with figuring out the default choices of the
values of some of the paths used by the ECL compiler.
I have a fairly vanilla install of ecl, where I think that at least the
relative positions of the installed files concerning ecl are typical. I
find:
> (translate-logical
On Sun, 22 May 2011, Juan Jose Garcia-Ripoll wrote:
> ECL has two installation modes, one follows the Unix hierarchy
[...]
> the other one has everything in the same directory (Logical pathname
> SYS:), as it is traditional in Windows.
Thank you for the explanation! That makes sense. So the "sam
On Thu, 30 Jul 2015, Chris Osborne wrote:
Anyhow, here’s the solution:
I just found that enable-smallcons is on by default (for some major performance
gains when I looked into it). In this scenario, there’s a set of macros
ECL_CONS_PTR, ECL_CONS_CAR etc. defined in object.h to access the cons