On Fri, Feb 11, 2011 at 11:29 AM, Juan Jose Garcia-Ripoll <juanjose.garciarip...@googlemail.com> wrote: > On Fri, Feb 11, 2011 at 1:50 AM, Willem Broekema <metaw...@gmail.com> wrote: >> There seem to be some ECL compiler issues that I have to make small >> test cases for. For now I'm able to work around them by falling back >> to interpreted mode. > > Could you report them individually or collectively as bugs? Having such > reports at Sourceforge, even anonymous, helps me a lot to keep track of what > is left to be done
Sure, I will add issues for them. >> I would like to suggest this library for inclusion on the buildbots: >> http://ecls.sourceforge.net/logs_lib.html > > We moved towards quicklisp for loading / testing libraries. Is cl-python > present there? Yes, but an older version that won't work in ECL. I'll try to get the version in quicklisp updated and let you know when that is done. - Willem ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
