Hi,
I de-bitrotted instruction-level tracing in the VM. Ideally it would
display like ,disassemble does, but that would take some more work.
Still, Guile's speed is mostly proportional to how many instructions are
executed, besides amount of garbage consed, and this view can be
interesting to
Hi,
I got the prolog parser reporting syntax errors for prolog programs.
It's soo nice to have an small analysis and a position where the error
is located. With this I can take on writing more complex prolog programs. An
example that is in the pipe is a FOL (first order logic)
theorem solver,
Hi,
On Thu 16 Sep 2010 21:00, Stefan Israelsson Tampe stefan.ta...@spray.se
writes:
http://www.ccs.neu.edu/scheme/pubs/icfp10-cf.pdf
I was wondering if you would like to see it ported to guile? I could try
to do that!
I think we could use an implementation in any case. Is there a free
Hi!
Stefan Israelsson Tampe stefan.ta...@spray.se writes:
I got the prolog parser reporting syntax errors for prolog programs.
It's soo nice to have an small analysis and a position where the error
is located. With this I can take on writing more complex prolog programs. An
example that
Hi Andy,
Andy Wingo wi...@pobox.com writes:
I de-bitrotted instruction-level tracing in the VM. Ideally it would
display like ,disassemble does, but that would take some more work.
Still, Guile's speed is mostly proportional to how many instructions are
executed, besides amount of garbage
What are your plans for your Prolog compiler, in terms of releases,
merges, and whatnot? :-)
This is on my list before I think that it will be merged/released a beta
1.
I'm in the process to replace the matchers with modified Shinn. The main
problem using prompts is that I don't get tail
Hi,
Stefan Israelsson Tampe stefan.ta...@spray.se writes:
For setting up the error reporting I used a pdf
describing the syntax-parse macro
http://www.ccs.neu.edu/scheme/pubs/icfp10-cf.pdf
Yeah, that seems like an improvement in terms of error detection and
error reporting (better
