freenode/#clasp - IRC Chatlog
Search
4:30:06
drmeister
beach: You mentioned some known problem in the concrete syntax tree about variables being IGNORE?
4:31:40
beach
It has to do with &optional (var form supplied-p) and &key (var form supplied-p). If the VAR is declared IGNORE, the SUPPLIED-P is incorrectly marked as being declared that way too, resulting in a warning.
4:32:37
beach
It is not a fatal problem, and the situation doesn't occur very often, but the problem should definitely be fixed.
4:35:00
Bike
this isn't very related, but do you have any thoughts about how to signal the opposite warning? you know, that a variable is bound but unused. it doesn't seem to fit in well with how things work.
4:36:28
beach
I guess if it is not live immediately after it is created, then that's a good place to warn.
12:16:14
frgo
::notify drmeister Q: I do have an extension now almost getting through the compiler... I now get: In file included from ../../src/gctools/gc_interface.cc:815:
12:16:14
frgo
./generated/initClassesAndMethods_inc.h:5865:46: error: incomplete type 'clasp_ext_rti_dds::RTIDDSExposer_O' named in nested name specifier
12:16:14
frgo
- This is due to the fact that gc_interface.cc does not have the include file that contains the new class definition of the extension. I could add this manually, but the problem is here that we don't have a clear separation of extension code to clasp core code. I'd rather find a way of generating an include file with a well defined name containing all extension include files. That single include file could then be a
12:41:36
frgo
::notify drmeister I opened a new issue regardimg doing #define free in clasp header file as this causes problems. https://github.com/drmeister/clasp/issues/403