Hi Three,

You can still read the pin even if it's set up to be an interrupt.

As far as using a goto instead of a retfie, any path you take must
eventually end in retfie or you'll break the stack. And since you ask
the question, let me suggest that by asking that particular question I
think the structure of your program is faulty if you are thinking about
doing it that way. Interrupts should be fairly short, maybe increment a
counter, put a byte in a buffer, or set a flag and then return.

Cheerful regards,

Bob


On Mon, 28 Jul 2008 12:07:40 -0700 (PDT), "threewheeler7"
<threewheeler7@hotmail.com> said:
> 
> I really have not had too much experience with interrupts, i have built
> and
> coded a few things that should have had them, mostly for the reason that
> way
> back when i first started learning about PICs, i was always warned how
> hard
> interrupts where to implement and that i should find a way to work
> without
> them. so that turned me off from them for the longest time. but i know
> they
> have there place and i need to start using them more. So 1. if i am using
> RB0/INT as my interrupt source, can i still read RB0 as a bit without
> disabling interrupts? ie. waiting for input to fall back down. also can i
> exit a interrupt routine with a "goto" instead of a "retfie"? ie. if i
> need
> to stop the program from what its doing and do something completely
> different.

-- 
http://www.fastmail.fm - IMAP accessible web-mail

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