File tree Expand file tree Collapse file tree 3 files changed +10
-10
lines changed Expand file tree Collapse file tree 3 files changed +10
-10
lines changed Original file line number Diff line number Diff line change 1
1
---
2
2
refs/heads/master: 4c6bf4872012c010f84dc7fa2cdfe87522533f89
3
3
refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
4
- refs/heads/snap-stage3: e3624ed968905b789b35c2301eb3c8057c05b3b3
4
+ refs/heads/snap-stage3: 32f97cc891a6a2857338b4fcc7bb022e609eac1c
5
5
refs/heads/try: 70152ff55722878cde684ee6462c14c65f2c4729
6
6
refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
7
7
refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
Original file line number Diff line number Diff line change @@ -28,6 +28,7 @@ extern mod rustc;
28
28
use std:: io;
29
29
use std:: os;
30
30
use std:: run;
31
+ use std:: libc:: exit;
31
32
32
33
enum ValidUsage {
33
34
Valid ( int ) , Invalid
@@ -234,7 +235,7 @@ pub fn main() {
234
235
235
236
if ( os_args. len ( ) > 1 && ( os_args[ 1 ] == ~"-v" || os_args[ 1 ] == ~"--version") ) {
236
237
rustc:: version ( os_args[ 0 ] ) ;
237
- return ;
238
+ unsafe { exit ( 0 ) ; }
238
239
}
239
240
240
241
let args = os_args. tail ( ) ;
@@ -244,11 +245,8 @@ pub fn main() {
244
245
for command in r. iter ( ) {
245
246
let result = do_command ( command, args. tail ( ) ) ;
246
247
match result {
247
- Valid ( exit_code) => {
248
- os:: set_exit_status ( exit_code) ;
249
- return ;
250
- }
251
- _ => loop
248
+ Valid ( exit_code) => unsafe { exit ( exit_code. to_i32 ( ) ) } ,
249
+ _ => loop
252
250
}
253
251
}
254
252
}
Original file line number Diff line number Diff line change @@ -1640,9 +1640,10 @@ mod test {
1640
1640
macro_rules! user(($x:ident) => ({letty!($x); $x}))
1641
1641
fn main() -> int {user!(z)}" ,
1642
1642
~[ ~[ 0 ] ] , false ) ,
1643
- // FIXME #8062: this test exposes a *potential* bug; our system does
1644
- // not behave exactly like MTWT, but I haven't thought of a way that
1645
- // this could cause a bug in Rust, yet.
1643
+ // no longer a fixme #8062: this test exposes a *potential* bug; our system does
1644
+ // not behave exactly like MTWT, but a conversation with Matthew Flatt
1645
+ // suggests that this can only occur in the presence of local-expand, which
1646
+ // we have no plans to support.
1646
1647
// ("fn main() {let hrcoo = 19; macro_rules! getx(()=>(hrcoo)); getx!();}",
1647
1648
// ~[~[0]], true)
1648
1649
// FIXME #6994: the next string exposes the bug referred to in issue 6994, so I'm
@@ -1655,6 +1656,7 @@ mod test {
1655
1656
// fn a(){g!(z)}"
1656
1657
// create a really evil test case where a $x appears inside a binding of $x
1657
1658
// but *shouldnt* bind because it was inserted by a different macro....
1659
+ // can't write this test case until we have macro-generating macros.
1658
1660
] ;
1659
1661
for ( idx, s) in tests. iter ( ) . enumerate ( ) {
1660
1662
run_renaming_test ( s, idx) ;
You can’t perform that action at this time.
0 commit comments