It looks like it should be hash-table-ref/default instead of
hash-table-ref, at extras.scm:1575
(otherwise you get: Error: call of non-procedure: #(42))
- Daniel
___
Chicken-users mailing list
Chicken-users@nongnu.org
Hi,
Just FYI, the chicken.html packaged with 2.2 is out-of-date. 'make
chicken.html' or make install will fix this.
Daniel
On Mon, 26 Sep 2005, Daishi Kato wrote:
At Sun, 25 Sep 2005 17:00:20 +0200,
felix winkelmann wrote:
- Embedding:
* All the `entry-point' related things have
On Thu, 25 Aug 2005, Daniel B. Faken wrote:
I'm switching from using my own version of CHICKEN_eval_string()
friends to the builtin one, which is now a callback.
When I was using my own version, I defined it in the normal top-level
scheme file, and my eval-fn had access to all the units
Hi,
When I define a type like c-string, int, and others as 'const' (i.e.
(const c-string), (const int), ..) their accessors give garbage output.
Just wanted to note it.. maybe I'll have time to figure it out in a week
or so. Just making them mutable for now..
thanks,
Daniel
On Wed, 17 Aug 2005, felix winkelmann wrote:
[...]
Q3: What are you missing most desperately from Chicken, or better:
if there is one thing that you really want it to have, what would that be?
my wish list.. :)
* Better error-messages/debugging support. Even using the debug module, I
find
/generate_glenum_strings.py is taken from
the original print SPU.
AUTHOR
Daniel B. Faken
email: Daniel_Faken -at- brown.edu
Some of this work was funded by grants from the U.S. Department of Energy.
___
Chicken-users
Hi,
The manual should probably note that recursive definitions don't work.
E.g. in this code: (the structure is part of 'chromium')
(define-foreign-record (SPU struct _SPUSTRUCT)
[(const c-string) name] [(const c-string)
Hi,
In chicken.h we find
#define C_SIZEOF_FLONUM 3
But (whereas this may have been right in the past), in runtime.c:C_flonum():
#ifndef C_SIXTY_FOUR
/* Align double on 8-byte boundary: */
if(aligned8(p)) ++p;
#endif
..which is not included in the size of '3', and which means
Hello,
I've been trying out the trick we discussed
(http://lists.gnu.org/archive/html/chicken-users/2005-07/msg00077.html),
but having confusing issues. I just thought I would report on these..
I've attached a torture test for this method, below, which resembles my
code pretty well (sans
On Wed, 27 Jul 2005, Daniel B. Faken wrote:
Hello,
I've been trying out the trick we discussed
(http://lists.gnu.org/archive/html/chicken-users/2005-07/msg00077.html),
but having confusing issues. I just thought I would report on these..
[...]
Oh, one more thing I tried
On Mon, 25 Jul 2005, felix winkelmann wrote:
On 7/22/05, Daniel B. Faken [EMAIL PROTECTED] wrote:
Hello,
I've been encountering problems using the FFI with functions that take a
(signed char *). For example, with this short program:
---
(define-foreign-type
On Fri, 22 Jul 2005, felix winkelmann wrote:
On 7/21/05, Daniel B. Faken [EMAIL PROTECTED] wrote:
On a related note: is it OK to call C_alloc() to construct data to be
passed via CHICKEN_invoke()?
Yes, that should work.
The manual entry for C_alloc() says ..Note that stack
Hello,
I've been encountering problems using the FFI with functions that take a
(signed char *). For example, with this short program:
---
(define-foreign-type GLbyte signed-char)
#!
typedef signed char GLbyte;
int call_fn(GLbyte x, GLbyte *y);
#
Hi,
The manual entry for (define-foreign-record) should indicate that, when
using the (TYPENAME FOREIGNNAME) version of NAME, the FOREIGNNAME should
be quoted.
I actually only figured this out by vague recollection of other
FFI behaviour, since if you try to compile this (as I did at
Hello all,
I'm wondering how I can get access to Chicken's FFI for building
function calls in C.
The problem I have is that I need *entry points* as well as callbacks,
because I am using Chicken as a (scripted) library which C programs will
call out into (see
Hello all,
I'm trying to build the new release with --with-libffi, but it appears
that the configuration is messed up. (my compiler output is appended)
Specifically, it seems that libffi is *not* compiled into libchicken,
and so to use libchicken, libffi.a must be explicitly included when
16 matches
Mail list logo
