This is Awesome!
Thank you.
Fab.
> On Apr 24, 2020, at 9:40 AM, Daniel Kochmański wrote:
>
> Dear All,
>
> we've released today a new version of ECL. For details please see the
> announcement on our blog:
> https://common-lisp.net/project/ecl/posts/ECL-20424-release.html
>
> Best regards,
> D
> On Sep 21, 2017, at 8:31 AM, Dima Pasechnik wrote:
>
>
>
> On Tue, Sep 12, 2017 at 1:18 AM, Fabrizio Fabbri wrote:
> >
> >> On Sep 11, 2017, at 7:13 PM, Dima Pasechnik wrote:
> >>
> >>> On Mon, Sep 4, 2017 at 11:15 AM, Daniel Kochmański
> On Sep 11, 2017, at 7:13 PM, Dima Pasechnik wrote:
>
>> On Mon, Sep 4, 2017 at 11:15 AM, Daniel Kochmański
>> wrote:
>> From the backtrace it is sure that fail is caused inside the call to
>> GC_init. Such errors are known to have happened when another GC was
>> initialized already on the sy
Il giorno 29 giu 2017, alle ore 10:25, Daniel Kochmański
ha scritto:
>> It seems like one of these should be removed. If so, I can remove one
>> of them and change all of the calls to it. I would say keep
>> FEprogram_error and remove FEprogram_error_noreturn.
>>
> If they do the same then ye
Hi Dave.
> Il giorno 23 giu 2017, alle ore 04:39, Dave Richards ha
> scritto:
>
> I am able to build ECL on mingw-w64 in 32-bit mode, but when I build in
> 64-bit mode it fails with a Lisp Initialization error.
Could you post the error?
> I notice that when
> building under MSVC there is an
The issue is fixed.
> On May 5, 2017, at 11:35 AM, Fabrizio Fabbri wrote:
>
> Hi all,
> I'm sitting on the very latest develop branch on OSX.
>
> I'm noticed that some time the compilation will hang when the compiler is
> invoked.
> I'm not able to repr
Hi all,I'm sitting on the very latest develop branch on OSX.
I'm noticed that some time the compilation will hang when the compiler is
invoked. I'm not able to reproduce it consistently and if I kill the build and
retry it does complete.
Empirical observation show that it is happen when we invok
> Il giorno 7 apr 2017, alle ore 16:51, Gross, Daniel
> ha scritto:
>
> Hi,
>
> I have some lisp source code and would like to test compatibility with ECL.
> Is there a simple way to test for compatibility. Ideally, I would compile
> and/or repl and run the code with ecl.
>
Hi Daniel,
wh
> Il giorno 8 nov 2016, alle ore 22:08, Daniel Kochmański
> ha scritto:
>
> Dear All,
>
> New ECL Quarterly issue has been published today. I hope to make it more
> regular, sorry for the delay.
>
> https://common-lisp.net/project/ecl/posts/ECL-Quarterly-Volume-V.html
>
> I have also some l
Hi Luca,
do your branch have commit 8fed1fa9 ?
Cheers
F.
> Il giorno 1-set-2016, alle ore 22:11, Daniel Kochmański
> ha scritto:
>
>
> Hey,
>
> lucareg...@yahoo.it writes:
>
>> Hi All,I have attempted unsuccesfully to compile Ecl under VS 2015
>> enterprise.I have simply run the nmake com
Hi all,
quick question.
I’ve got my embedded ecl on a multi thread windows service.
Before doing anything I call cl_boot.
Then multiple request coming in served by different thread.
At this point I call ecl_import_current_thread and the evaluate some lisp code
with cl_safe_eval with Cnil as en
Hi all,
I make ECL compile with Win64 cl compiler, and so far it does not work
bad.
I want to run the unit test, and I was able to do it manually
with some failure but I'm not 100% sure that I run those in the right
way.
It there some instruction that I can follow or can you tell me wich is
the p
Hi all,
I'm on my win64 build and I'm using asdf to define my system but with
asdf:make-build or
asdf:load-bundle-op the ld-flags option to link some additional static
library to my fasl is not passed to the linker.
So far I workaround with (si:setenv "_CL_" "bla bla bla") but it's not
ideal.
A
13 matches
Mail list logo
