17:55:48Selwynwould it be possible to expose C structs and functions in Clasp in much the same way as c++ classes and methods are?
17:57:20SelwynI wonder whether it is worth the effort to have GSL available in Clasp as a 'first class citizen' so to speak - the GSLL library uses a FFI interface to communicate with the GSL API.
17:57:45drmeisterRe: "would it be possible to expose C structs and functions in Clasp in much the same way as c++ classes and methods are?"
17:59:17drmeisterA first class citizen means there need to be changes to the GSL code so that its objects can be managed by the garbage collector. That would be non-trivial but not impossible.
18:00:43drmeisterThere are three choices (1) CFFI interface (already done IIUC) (2) clbind wrappers for C++ interface (easy) (3) Modify source code to make library exposed to the GC directly (hard).
18:07:16kpoeck_I am now getting a BUG: Unknown UAET NIL while loading the ansi-test
18:07:37kpoeck_Can somebody point me in the direction to search for this?
18:08:29drmeisterkpoeck_: Clasp is generating the string "UAET NIL" ?
18:08:53kpoeck_Debugger received error of type: SIMPLE-ERROR BUG: Unknown UAET NIL Error flushed.
18:09:02drmeister"Unknown UAET NIL"? I don't recall ever seeing that before.
18:09:24kpoeck_Well in the backtrace there is (UAET-INFO NIL)
18:09:50drmeisterI'd start recursively grepping clasp source *.cc *.h *.l*sp for that. And then I'd start grepping other libraries that Clasp is loading. Weird.
18:10:03kpoeck_I pulled changes and did my own, so I don't know whether is caused that or some other commit
18:10:15drmeisterYou could also try 'strings cclasp-boehm | grep UAET'
18:10:31drmeisterI have no idea what UAET stands for.
18:10:52kpoeck_Since it might be my own error, let me search for it
18:11:45Selwyni am running ansi-test right now, will post here if i reproduce this