Gambit-list Janvier 2008

gambit-list@iro.umontreal.ca

20 participants
24 discussions

Little error in the docs?
by Esteban U. Caamano Castro 12 Jan '08

12 Jan '08

I think there is a small contradiction in the documentation for c-lambda in the manual at http://www.iro.umontreal.ca/~gambit/doc/gambit-c.html#SEC132 [...] the result to be returned from the call should be assigned to the variable `___result' except when the result is of type struct, union, type, pointer, nonnull-pointer, function or nonnull-function in which case a pointer must be assigned to the variable `___result_voidstar' which is of type `void*'. [...] But then in one of the examples: (define stdin ((c-lambda () (pointer "FILE") "___result = stdin;"))) Shouldn't that be "___result_voidstar = (void*)stdin;", then?

2 1

Type checking
by jadamson＠partners.org 11 Jan '08

11 Jan '08

Dear Gambit List, I have a set of datatypes defined with c-define-type based on the GNU Scientific Library. The Gambit-C manual says "For type checking on the Scheme side..." to use the TAG function of the type definition as in (c-define-type gsl-matrix* (pointer gsl-matrix "gsl-matrix*")) What is the best way to use this to define a boolean test (e.g. gsl-matrix*?) for this type? I feel like I must be missing something since the explanation of type checking stops with how to define the TAG and how it's printed in the external representation of an object of that type. For example: ;;gsl-matrix-initialize returns a pointer ;;to a gsl-matrix (define A (gsl-matrix-initialize)) A #<gsl-matrix* 2 0x38f9e89> Thanks, Joel -- Joel J. Adamson Biostatistician Pediatric Psychopharmacology Research Unit Massachusetts General Hospital Boston, MA 02114 (617) 643-1432 (303) 880-3109 The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.

3 4

#\esc's wrong ascii code
by Adrien Pierard 10 Jan '08

10 Jan '08

Hello Schemers. It looks like Gambit associates the value 26 to the #\esc character, instead of 27. (char->integer #\esc) => 26 (integer->char 26) => #\esc it might be unintentional, but lib/_io.c has ___DEF_GLO(26,"##escape-keyword?") Isn't this blind chance? Adrien. -- Hapy new year

3 2

Building issues with 4.1.2 under Windows
by Nick 07 Jan '08

07 Jan '08

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Gambit-list Janvier 2008