freenode/#clasp - IRC Chatlog
Search
6:23:15
beach
That should happen only if you have a backquote in a place that is not allowed. Of course, it could be that I have neglected some such places that ought to be allowed.
6:24:14
drmeister
The backquote at the bottom: `(OR (RATIONAL ,rat-start ,rat-end) (FLOAT ,real-start ,real-end)))
6:33:35
beach
I just see some #+ and #-, and I can very well imagine that I omitted to allow backquote inside those.
6:40:06
drmeister
We had a discussion a couple of days ago about cst-read handling eof - is this an acceptable solution for that?
6:40:07
beach
The fix for #+ and #- should be simple. I'll deal with it after I get your pull request.
6:51:42
drmeister
::notify bike bclasp seems rock solid now - no more exception handling problems that I can see.
6:53:19
drmeister
::notify bike It was a very, very longstanding problem in the WITH-TRY macro when an exception bubbles up the stack.
6:57:26
drmeister
Ah - sorry. I checked the output but I didn't give it any case that would test that branch - sorry.
7:04:29
beach
I fixed the backquote problem. It was a matter of wrapping the #+ and #- bodies in with-preserved-backquote-context.
16:22:29
beach
I can't fix it today. I am tired after a long day of work. Progress was made, though.
16:25:03
beach
drmeister: By the way, good news. Together with scymtym, we are extracting the entire reader to a separate repository. He has agreed to help with improvements and such. Part of the plan is to have a separate test suite and separate documentation.
16:28:12
drmeister
I changed the feature expressions to convert #+(and ecl (not clasp)) to just #+ecl
16:35:36
drmeister
Timing-wise the cst reader will not slow things down noticeably - it takes 1.4 seconds to read two of clasp's source files. The C++ reader takes 0.7 seconds.
16:38:56
drmeister
I'll just call a special function every 10MB of memory allocated and have dtrace generate a backtrace every time that special function is entered.
16:42:58
beach
I am pretty sure the compilation times will be dominated by optimizations and not by reading the source code.