> As in: GIE is the last bit to be set out of all of the things that have
> to do with the Interrupts?

Uh-huh. There are times when you might want to turn interrupts
off and on, and that may mean NOT clearing pending IFs. Say
you have code that has both a clock and comms. The comms
have priority and you don't want them to be interrupted by, er,
an interrupt that isn't vital. So, on comms detection or commence-
ment, you turn GIE off while you deal with the foreground task
of making sure the comms are done properly. Meanwhile, in the
background, the clock (eg a TMR) is still running. When the
comms are finished, you turn GIE back on. If a clock event
happened whilst you were comming, there will be an IF set in
hardware, which will direct program flow to the ISR as soon
as GIE is re-set

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist