I might be misunderstanding, but it looks like I've hit some cases where 3.0 wants #:re-export-and-replace, and 2.2 rejects it, and I'd like to create modules that work cleanly with both.
At first I imagined I might use cond-expand, but it won't work inside a define-module form. Another option might be a procedural re-export-and-replace! that could be called conditionally after the define-module. Yet another option might be to add #:re-export-and-replace to 2.2, perhaps even as just an alias for #:replace (if that's adequate in 2.2), but that has the disadvantage of requiring a 2.2 update, which decreases it's appeal. In any case, if I'm not misunderstanding, I'm happy to help work on whatever improvement we prefer. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4