diff options
author | Paul Phillips <paulp@improving.org> | 2011-04-01 17:18:34 +0000 |
---|---|---|
committer | Paul Phillips <paulp@improving.org> | 2011-04-01 17:18:34 +0000 |
commit | a6ba30b8eb1968979db92d3a006d57343983e684 (patch) | |
tree | c47af0e4a8de82d811dd298b8feee5945c5084ec /pull-binary-libs.sh | |
parent | 4df2e9335b7f8831f7877baf855c28bb35d90c18 (diff) | |
download | scala-a6ba30b8eb1968979db92d3a006d57343983e684.tar.gz scala-a6ba30b8eb1968979db92d3a006d57343983e684.tar.bz2 scala-a6ba30b8eb1968979db92d3a006d57343983e684.zip |
Finding myself wanting a working -Ystop, I did ...
Finding myself wanting a working -Ystop, I did the following.
-Ystop-after:phase works
-Ystop-before:phase works
-Ystop:phase is a backward compat alias for -Ystop-after
Until now -Ystop, although documented to "stop after phase", actually
stopped before phase, to the consternation of some. Furthermore the
programmatic way to influence the stop phase (protected def stopPhase in
Global#Run) involved returning true if you wanted to stop before the
phase. So now the command line option works as advertised, and the
method has the same semantics. The only potential loser is some script
which uses -Ystop: based on the actual behavior rather than the documented
behavior. Well, someone had to lose. No review.
Diffstat (limited to 'pull-binary-libs.sh')
0 files changed, 0 insertions, 0 deletions