datalog/tests
Jay McCarthy 84a3b742ae fixes pr1
This is a potentially weird case and decision on what to do about it. In
general, when we print out answers, we try to make sure that they look
like valid datalog. In this case, a Racket value is being used a Datalog
constant (which is legal and part of the #lang datalog embedding), so we
can't know what syntax was used to get it in the first place... so by
using a ~v we get a distinctive printing that shows it isn't datalog.

On the other hand, I could change #lang datalog so that it's environment
is empty and this program wouldn't be referring to '()
2016-02-24 09:38:56 -05:00
..
examples Remove extra dirs. 2014-12-01 22:13:42 -05:00
paren-examples Remove extra dirs. 2014-12-01 22:13:42 -05:00
pr fixes pr1 2016-02-24 09:38:56 -05:00
private Remove extra dirs. 2014-12-01 22:13:42 -05:00
tool Remove extra dirs. 2014-12-01 22:13:42 -05:00
ast.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
eval.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
main.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
parse.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
pretty.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
racket.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
runtime.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
test-docs-complete.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00
util.rkt Remove extra dirs. 2014-12-01 22:13:42 -05:00