Use a different strategy for transitioning to camel case extfmt

This commit is contained in:
Brian Anderson 2012-09-12 11:22:48 -07:00
parent 2eef6658c3
commit 320331fe35
2 changed files with 3 additions and 6 deletions

View File

@ -273,10 +273,8 @@ mod ct {
// decisions made a runtime. If it proves worthwhile then some of these
// conditions can be evaluated at compile-time. For now though it's cleaner to
// implement it 0this way, I think.
#[cfg(stage1)]
#[cfg(stage2)]
#[cfg(stage3)]
mod rt {
// XXX Rename to rt after snapshot
mod rt2 {
const flag_none : u32 = 0u32;
const flag_left_justify : u32 = 0b00000000000000000000000000000001u32;
const flag_left_zero_pad : u32 = 0b00000000000000000000000000000010u32;
@ -464,7 +462,6 @@ mod rt {
}
// XXX remove after snappies
#[cfg(stage0)]
#[allow(non_camel_case_types)]
mod rt {
const flag_none : u32 = 0u32;

View File

@ -39,7 +39,7 @@ fn pieces_to_expr(cx: ext_ctxt, sp: span,
-> @ast::expr {
fn make_path_vec(_cx: ext_ctxt, ident: @~str) -> ~[ast::ident] {
let intr = _cx.parse_sess().interner;
return ~[intr.intern(@~"extfmt"), intr.intern(@~"rt"),
return ~[intr.intern(@~"extfmt"), intr.intern(@~"rt2"),
intr.intern(ident)];
}
fn make_rt_path_expr(cx: ext_ctxt, sp: span, nm: @~str) -> @ast::expr {