On Fri, 13 Nov 2015 12:30:34 +0100
Attila Lendvai wrote:
> > I'll remove the `new-cmp' directory before the next
> > release to avoid unnecessary confusing of people approaching the
> > codebase.
>
> random suggestion: leave it behind in a separate branch with an
> appropriate name.
Unfortunate
On Tue, 10 Nov 2015 03:17:17 +0100
"Pascal J. Bourguignon" wrote:
> I compiled and installed successfully ecl-android on a cyanogen
> cm-12.1 android on Sansung Galaxy S4.
>
> After getting quicklisp:
>
> - I tried (ql:add-to-init-file) but I'm not sure it was successful,
> since it waits for
On Fri, 06 Nov 2015 00:12:40 +0100
Bix wrote:
> Yep, manage memory manually is impratical and as you said circular
> structures are one of the real problem.
With reference counting these should be a problem, although libgc is a
mark-and-sweep collector which should detect when elements are no
l
On Sun, 25 Oct 2015 09:28:03 +0100
Bix wrote:
> just two quick question:
> 1. Is it possible to disable the threading model and have multiple
> thread to eval the code or have one ECL per thread?
> 2. Can the garbage collector be disabled at all and have the memory
> managed in a reference counti
On Tue, 01 Sep 2015 07:29:00 +0200
Daniel Kochmański wrote:
> Ok, it failed (just after sending an e-mail, it's good to know that
> Muprhy's law still works :-)).
A complete hang?
--
Matt
On Tue, 01 Sep 2015 07:25:37 +0200
Daniel Kochmański wrote:
> btw, it doesn't hang on my machine (runs ~30m already, if it'll
> fail I'll let you know). Could you provide more details? (OS,
> *features*, number of cores etc.)
I also have been trying to reproduce it on NetBSD/amd64 with 4 cores i