Martin McCormick wrote:

>         Warnings are usually there for a purpose even though they may
> not immediately shut down what one is doing, so I figured I had better
> find out what sort of trouble I was starting.

  True enough, though 302 and 305 are really style reminders and 224 is
total nonsense.

  Andy Baker reccomends suppressing 302.  I would prefer to reccomend
suppressing 224 globally as I stated, but making a point of coding to
avoid 302 and 305.  305 is avoided by never defaulting the destination
of an operation, but always explicitly using F or W (*NEVER* 0 or 1!).

  302 is avoided either by macros or by using labels such as TRISB^HIBIT
where HIBIT is defined as $80.  With that blatant marker, you will tend
to remember to check bank bits.
--
  Cheers,
        Paul B.