Thank you for a solution.
But is there any way to force ecl use utf-8 instead of utf-32, and in
simple english case be the same as ascii? May be it has some special
functions to work exactly with specified encoding?
2012/7/23 Polos Ruetz
> 2012/7/22, Арсений Заостровных :
> > std::string out
2012/7/22, Арсений Заостровных :
> std::string outStr = (char*)princed->base_string.
This code is taken from "EQL" and converts from/to a QString.
(But maybe there's a better way.)
cl_object from_qstring(const QString& s)
{
cl_object l_s = ecl_alloc_simple_extended_string(s.length());
Hi all.
I'm using the latest release of ecl - 12.7.1. The question may be not about
the ecl at all. But there a misunderstanding: what encoding ecl uses by
default during conversation between lisp and c? The nice project
http://createuniverses.blogspot.com/2009/09/qtimagine-skeleton-project-for-liv
On Tue, Jul 17, 2012 at 1:25 PM, Mark Cox wrote:
> I am having a problem where the ecl process enters the sleeping state upon
> exiting. It does not do it every time.
As explained on a separate email this is due to a race condition in the
garbage collector. Unfortunately I do not know any fix y
On Sun, Jul 22, 2012 at 8:48 PM, Pascal J. Bourguignon <
p...@informatimago.com> wrote:
> People will blog about how they used (require :ecl-quicklisp) in ecl,
> newbies
> will complain that it doesn't work (on their implementation), then may
> blog about the social problems of #lisp or cll…
By
Juan Jose Garcia-Ripoll
writes:
> On Sun, Jul 22, 2012 at 8:08 PM, Zach Beane wrote:
>
> I can appreciate the desire for Lisp systems to have some form of
> Quicklisp integration, but I am reluctant to see divergence of
> instructions like this. I really like that the instructions fo
Juan Jose Garcia-Ripoll writes:
> As you may recall, ECL now ships a module :ecl-quicklisp that installs and
> loads quicklisp. I made several changes to it:
>
> * If quicklisp has already been loaded, ECL will not reload it.
>
> * (require :ecl-quicklisp) installs quicklisp on different location
On Sun, Jul 22, 2012 at 8:13 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@gmail.com> wrote:
> In short: it is not compulsory, it allows me to plug in customizations
> such as enforcing monolithic libraries, it also allows to plug in
> additional steps that quicklisp need not consider, such
On Sun, Jul 22, 2012 at 7:45 PM, H Durer wrote:
> After I compiled my own version of ecl, I sudo make install'ed it to
> /usr/local/...
>
.. the patch took some time to get into the repo. My apologies for posting
so fast.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madri
After I compiled my own version of ecl, I sudo make install'ed it to
/usr/local/...
I now tried to use the ecl-quicklisp as a non-root user but get this:
snip
> (require :ecl-quicklisp)
;;; Loading "/usr/local/lib/ecl-12.7.1/ecl-q
On Sun, Jul 22, 2012 at 6:32 PM, H Durer wrote:
>
> | ;;; The following lines added by ql:add-to-init-file:
> | #-quicklisp
> | (let ((quicklisp-init (merge-pathnames "quicklisp/setup.lisp"
> | (user-homedir-pathname
> | (when (probe-file quicklisp-in
On Sun, Jul 22, 2012 at 3:44 PM, Juan Jose Garcia-Ripoll
wrote:
> On Sun, Jul 22, 2012 at 4:12 PM, H Durer wrote:
>>
>> So, should we remove the stuff added by ql:add-to-init-file from our
>> ~/.eclrc and just add a "(require :ecl-quicklisp)"?
>
>
> I actually never used ql:add-to-init-file. What
On Sun, Jul 22, 2012 at 4:12 PM, H Durer wrote:
> So, should we remove the stuff added by ql:add-to-init-file from our
> ~/.eclrc and just add a "(require :ecl-quicklisp)"?
>
I actually never used ql:add-to-init-file. What is it?
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113
So, should we remove the stuff added by ql:add-to-init-file from our
~/.eclrc and just add a "(require :ecl-quicklisp)"?
On Sun, Jul 22, 2012 at 11:26 AM, Juan Jose Garcia-Ripoll
wrote:
> As you may recall, ECL now ships a module :ecl-quicklisp that installs and
> loads quicklisp. I made several
On Sun, Jul 22, 2012 at 12:51 PM, H Durer wrote:
> I managed to install the libatomic-ops-dev package which gives me the
> headers and the lib pre-built.
> Could you outline what is involved in using the system libatomic-ops?
> Would configure find that and use it or do I need to tweak things in
Thanks Juanjo.
At the moment I am trying a compile with -DAO_USE_PTHREAD_DEFS in the
CFLAGS. That seems to include a header which will implement these
primitives via pthreads mechanisms. Not very efficient I guess but it
might work.
On Sun, Jul 22, 2012 at 10:50 AM, Juan Jose Garcia-Ripoll
wr
16 matches
Mail list logo
