Hi,
I have recently switched to using the cffi+lotsastuff version and I
find it very slow for certain applications. The reason for this is
that PARSE-TYPE is called from FOREIGN-TYPE-SIZE, and PARSE-TYPE is
very expensive. It would be relatively easy to cache the type parsing
results in a hash t
On Fri, May 30, 2008 at 5:49 PM, Luís Oliveira <[EMAIL PROTECTED]> wrote:
> PARSE-TYPE has been slow ever since it started to check for cycles.
> This change is not specific to the cffi+lotsastuff branch:
We are using the latest release version of CFFI internally, and I have
tried out the cffi+lot
On Fri, May 30, 2008 at 7:27 PM, Luís Oliveira <[EMAIL PROTECTED]> wrote:
> On Fri, May 30, 2008 at 5:13 PM, Hans Hübner <[EMAIL PROTECTED]> wrote:
>> Every invocation of FOREIGN-STRING-ALLOC eventually invokes
>> PARSE-TYPE, and we use it a lot.
>
> Thanks to th
On Fri, May 30, 2008 at 10:55 PM, Luís Oliveira <[EMAIL PROTECTED]> wrote:
> On Fri, May 30, 2008 at 8:08 PM, Hans Hübner <[EMAIL PROTECTED]> wrote:
>> On Fri, May 30, 2008 at 7:27 PM, Luís Oliveira <[EMAIL PROTECTED]> wrote:
>>> Thanks to the optimization m
On Fri, May 30, 2008 at 5:13 PM, Hans Hübner <[EMAIL PROTECTED]> wrote:
>>> On Fri, May 30, 2008 at 7:27 PM, Luís Oliveira <[EMAIL PROTECTED]> wrote:
>>>> Thanks to the optimization mentioned above (a compiler macro for
>>>> foreign-alloc),
Hi,
is there a good reason why WITH-FOREIGN-STRING allocates the buffer on
the heap instead of using WITH-FOREIGN-OBJECT, which will allocate on
the stack on platforms that support it?
Thanks,
-Hans
___
cffi-devel mailing list
cffi-devel@common-lisp.net
On Fri, Jun 20, 2008 at 9:13 AM, Luís Oliveira <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 20, 2008 at 5:21 AM, Hans Hübner <[EMAIL PROTECTED]> wrote:
>> is there a good reason why WITH-FOREIGN-STRING allocates the buffer on
>> the heap instead of using WITH-FOREIGN-OBJ
On Fri, Aug 21, 2009 at 19:10, Luís Oliveira wrote:
> As Daniel Herring hinted, one way you can solve this problem is to
> setup asdf:*central-registry* such that UFFI's uffi.asd takes
> precedence over the clbuild/systems/uffi.asd one. Would that work for
> you?
I use an automated mechanism to s
Ralph,
what you observe is not a bug in CFFI, but a feature of the Common Lisp
pathname system. The *FOREIGN-LIBRARY-DIRECTORIES* contains a list of
pathname designators. When a string is used as a pathname designator
(either by putting a string onto that list or by using the #P reader macro
to
