Tony Sidaway wrote: > [...] > My current thought is this: In step 1, I pass the library a key (in > static memory, not heap) which I associate with the port (I place the > actual port in a srfi-69 hash table under that key). On receiving the > key, in stage 2, my write procedure (which would ideally be written in > Chicken as a safe-foreign-wrapper procedure) would pick the port out > of the hash table using that key, and write the string using a method > compatible with Chicken's port mechanism. > [...]
Hello, for a similar technique of callback management you may want to have a look at the implementation of the SQLite3 egg, which allows you to define arbitrary new SQL functions in Scheme using sqlite3:define-function and associates... cu, Thomas _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
