Antform is available on sourceforge. I use it to provide a form for users to
select options during the compile or to get the username and password for the
CM system.
SVN login
This puts a form up for user input. The problem would be that if the parallel
tasking redirects out
Chuck Holzwarth wrote:
Perhaps the facility that spawns the targets could manage the screen/buffer
output. This would mean that some facility would have to exist similar to
named pipes in Unix. This way, console output would be directed from the
buffer (or pipe) that had first output while other
Perhaps the facility that spawns the targets could manage the screen/buffer
output. This would mean that some facility would have to exist similar to named
pipes in Unix. This way, console output would be directed from the buffer (or
pipe) that had first output while other targets would be produ
Chuck Holzwarth wrote:
[...]
How do you propose to handle potential fatal/non fatal errors? If target a
exits due to an error, should there be an option to kill a or allow it to
complete (similar to failonerror="yes/no")? If both a and (b,c) must succeed
for d, should a be killed if b or c fails
It may be better to stay away from a grammar that gives the rules and use
something like:
...
How do you propose to handle potential fatal/non fatal errors? If target a
exits due to an error, should there be an option to kill a or allow it to
complete (similar to failonerror="yes/no
Isn't this the default behaviour anyway?
Should not be interpretted as " 'a' depends on 'b' then 'c' then 'd' ", as that
would imply that 'b' depended up 'c', which in turn depended upon 'd'.
If such a dependency did exist, it should be incorporated in the depends
attribute of the 'b' & 'c' ta
