freenode/#clasp - IRC Chatlog
Search
14:34:58
Bike
drmeister: there's already some stuff for function descriptions in functor.cc, but it treats them as void* for some reason? instead of using the structure. is that how it worked before the structure was defined?
15:11:51
Bike
"Malongains a callback to a Python function. Also malongains two doubles and two longegers that can be passed back and forth"
17:39:12
drmeister
Bike: I first created the %function-description% and %function-description*% types in llvm and I had not exposed them in C++ - so I passed %function-description*% pointers around as a void* . Please replace any (void*) with core:FunctionDescription*
17:44:02
Bike
Do you think we could have a source-location structure in the runtime? We could probably add source info to classeslike immediately except I don't want to have four slots
17:48:36
Bike
the structure would have what we use for source info, i.e.e a file handle, a line number, a column number, and a file position.
17:49:26
drmeister
https://github.com/clasp-developers/clasp/blob/dev/include/clasp/core/sourceFileInfo.h#L83
17:50:14
drmeister
Well, it's there - I used to use it a lot - then source tracking degraded to almost useless. Now it's alive and better than ever.
17:52:17
drmeister
Right - it doesn't yet. Is that all that you would want to add to the function-description?
17:59:30
Bike
there's nothing particularly i want to add. it's got the name, the docstring, the lambda list, the source position. that's fine
18:33:45
Bike
i see the scraper uses define_source_info which uses ext:annotate for docstrings... so i guess not actuallytouching thefunction