🚀 go-pugleaf

In article <1852@xyzzy.UUCP> kan@mutley.dg.com () writes:
>I've been looking for the issue for weeks, but finally found it today.
>It's in the Byte IBM Special Edition for Fall 1988 (volume 13, #11).
>To summarize, C library functions are called with the c-call function.
>C style structures are handled like this:
>
>/* from their example */
>struct FileFindBuf {
>	unsigned create_date;
>	unsigned create_time;
>	unsigned access_date;
>.
>}
>
>becomes:
>
>(define FileFindBuf
>	'((word create_date)
>	  (word create_time)
>	  (word access_date)
>.
>))
>
>Unfortunately, the source for the extentions of XLISP to OS2XLISP were not
>published in the issue.  I assume it's available from the usual Byte
>source sources.
>

I needed to access and set C structures (i.e. defined and allocated by C),
so I hacked together a parser that converts C structure definitions into
a form that is suitable for use in scheme, and some scheme utility code
to use it.

As an example, given:

typedef struct {
   int i;
   char c;
   float f;
} Example;

And a scheme function 'get-an-example' that returns a pointer to a new
example, I can do the following:

(make-struct-accessor 'Example 'i)
(make-struct-accessor 'Example 'c)
(make-struct-accessor 'Example 'f)

(define s (get-an-example))

(set-example-i! s 10)
(set-example-c! s #\newline)
(set-example-f! s 1.2)

(+ (example-i s) (example-f s)) => 11.2

Note that this code is not really suitable for structures in scheme
(although it could be adapted), but rather for accessing and modifying
structures in C from scheme.

Mail to me for more info.

- Eric (raible@orville.nas.nasa.gov)