[armedbear-ticket] [armedbear] #218: More Compreshensive Regression testing
armedbear
armedbear-devel at common-lisp.net
Tue Jul 17 20:58:41 UTC 2012
#218: More Compreshensive Regression testing
----------------------------------------------------------------------------------------------+
Reporter: https://www.google.com/accounts/o8/id?id=aitoawmy4u2arai5whm4pn4h0biwcvdnd33aq5k | Owner: ehuelsmann
Type: enhancement | Status: new
Priority: minor | Milestone: 2.0
Component: interpreter | Version: 1.1.0-dev
Keywords: |
----------------------------------------------------------------------------------------------+
Comment(by https://www.google.com/accounts/o8/id?id=aitoawmy4u2arai5whm4pn4h0biwcvdnd33aq5k):
easye: A command-line switch?
Perhaps, yes. That would make the current implementation easier to test
w/o messing with the current ways of building. Simply, the switch would
tell ABCL to ignore the the .cls/.abcl files and always use the .lisp
Way easier than my manual way of of testing: (this here is incomplete but
you get the idea)
mkdir LISPHOME
xcopy src\org\*.lisp LISPHOME\org\ /d /e
javac -d LISPHOME -sourcepath src\ src\org\armedbear\lisp\*.java
src\org\armedbear\lisp\util\*.java
javac -cp LISPHOME -d LISPHOME -sourcepath src\
src\org\armedbear\lisp\java\swing\*.java
src\org\armedbear\lisp\protocol\*.java
javac -cp LISPHOME -d LISPHOME -sourcepath src\
src\org\armedbear\lisp\scripting\*.java
java -cp LISPHOME org.armedbear.lisp.Main
:cd ../ansi-tests
(load "doit.lsp")
Which also doesn't preclude re-disabling the compiler,
so a command line switch enabling of a boolean is still going to be the
smartest choice.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/218#comment:2>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
More information about the armedbear-ticket
mailing list