'*-bank' question

Hi,

I know that 'select-bank' after a variable name in code words forces the 
compiler to generate appropriate switching instructions for the 
variable's home bank.

However, when coding a prog using lib3 and multitasker, I came across 
situations where this wasn't working quite right. Seemed the compiler 
heuristics were assuming an incorrect 'current bank', and therefore not 
issuing the right bank select instructions.

So my question is - is there any way to reset the compiler's 'current 
bank' state? In other words, to force the compiler to forget what bank 
it thinks it's set to, and force explicit bsf/bcf rp0/rp1 instructions?

I think this might be a useful safety net when tracing weird issues.

-- 
Cheers
David