It's a cool idea, but his reason for creating it is kinda dumb.
Creating an entire "project" just to check a code snippet is just silly.
Just create a "testing" directory and throw your one off test files into it and compile/run them there.
I start mine with a comment explaining what I'm testing, why I'm testing it, and what special compilation flags are required, if any. I even have an Emacs macro that fills in the boilerplate includes and main function. The overhead involved is probably less than 15 seconds.
It has the advantages that I can test multiple compilers and I keep a history of the things I've tried.
The ROOT project has been using CINT for ages. Talk to your favorite physicist friend -- they'll be confused why the CS crowd _doesn't_ have this technology.
This is just an updating of what must be an awful hack to be built on LLVM infrastructure.
Comments
It's a cool idea, but his reason for creating it is kinda dumb.
Creating an entire "project" just to check a code snippet is just silly.
Just create a "testing" directory and throw your one off test files into it and compile/run them there.
I start mine with a comment explaining what I'm testing, why I'm testing it, and what special compilation flags are required, if any. I even have an Emacs macro that fills in the boilerplate includes and main function. The overhead involved is probably less than 15 seconds.
It has the advantages that I can test multiple compilers and I keep a history of the things I've tried.
The ROOT project has been using CINT for ages. Talk to your favorite physicist friend -- they'll be confused why the CS crowd _doesn't_ have this technology.
This is just an updating of what must be an awful hack to be built on LLVM infrastructure.
Because actually using ROOT is painful, and the CS crowd had lisp and now python/pypy.
http://www.insectnation.org/howto/living-without-root
https://linuxfr.org/nodes/18919/comments/632920
http://comments.gmane.org/gmane.comp.lang.c%2B%2B.root/5924