Post by tsh73 on Feb 13, 2024 8:53:56 GMT -5
I think it will be beneficial for testing LB5 if it could be driven from command line, and possibly returned error codes on error
All I want to make sure is that program is compatible with LB5
So it does not have to produce anything, like TKN or EXE
(Though command line way of producing TKN or EXE sure will come handy *after*)
So we can run a big batch file
. which takes (next) program and tries to compile it
.. and either process it without error and quit (so we conclude "compatible")
.. or produce an error (may be standard error stream that could be capture with " 2>errorLog.txt" ?)
.. (btw for "compiles or not" break on first error is enough)
... - but still quits without user intervention, so batch file can go on
Me thinks it will be big help with testing,
to see which of existing examples do not compile,
and to see if new version not to break some previous codes
(regression testing).
All I want to make sure is that program is compatible with LB5
So it does not have to produce anything, like TKN or EXE
(Though command line way of producing TKN or EXE sure will come handy *after*)
So we can run a big batch file
. which takes (next) program and tries to compile it
.. and either process it without error and quit (so we conclude "compatible")
.. or produce an error (may be standard error stream that could be capture with " 2>errorLog.txt" ?)
.. (btw for "compiles or not" break on first error is enough)
... - but still quits without user intervention, so batch file can go on
Me thinks it will be big help with testing,
to see which of existing examples do not compile,
and to see if new version not to break some previous codes
(regression testing).
