Fcalva/cyclone
1
0
Fork 0
mirror of https://github.com/justinethier/cyclone.git synced 2025-07-15 16:57:35 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Revised 0.28.0 section

Browse source
This commit is contained in:
Justin Ethier 2021-04-06 13:29:21 -04:00
parent 2e476e3817
commit ff4dd5e927
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
CHANGELOG.md
View file

@ -6,16 +6,16 @@ Features
- Updated the compiler and runtime to allow a (practically) unlimited number of function arguments. This involved changing the calling conventions of our generated C code and runtime functions. - Updated the compiler and runtime to allow a (practically) unlimited number of function arguments. This involved changing the calling conventions of our generated C code and runtime functions.
Most importantly, this change is transparent to application developers. Programs will continue to work without requiring modifications, though it may be necessary to update `define-c` definitions if there are unused parameters, to prevent warnings from the C compiler. For example: Most importantly this change is transparent to application developers. Programs will continue to work without requiring modifications. This includes code using our FFI, though it may be necessary to update `define-c` definitions if there are unused parameters in order to prevent warnings from the C compiler. For example:
(define-c read-error (define-c read-error
"(void *data, object _, int argc, object *args)" "(void *data, object _, int argc, object *args)"
" object port = args[1]; " object port = args[1];
object filename = args[2]; object filename = args[2];
object msg = args[3]; object msg = args[3];
...
TODO: is the following true? What about unused args in the C code????? No changes are a required if `(cyclone foreign)` is used to integrate with C.
Note that no changes are a required if `(cyclone foreign)` is used to integrate with C.
- Provide alternative library names for each of the SRFI libraries. Generally these names follow the recommendations from R7RS Large - for example `(scheme list)` as a friendlier alternative to `(srfi 1)`. Where such a name does not exist we provide a name with the `(cyclone)` prefix: - Provide alternative library names for each of the SRFI libraries. Generally these names follow the recommendations from R7RS Large - for example `(scheme list)` as a friendlier alternative to `(srfi 1)`. Where such a name does not exist we provide a name with the `(cyclone)` prefix: