Hi Russ and Steve
for 16F ...
gives in asmCode:While 0 Wend next command
Should do the trick, no ???Code:L0001 GOTO L0002 GOTO L0001 L0002 .... Next Command
Alain
Hi Russ and Steve
for 16F ...
gives in asmCode:While 0 Wend next command
Should do the trick, no ???Code:L0001 GOTO L0002 GOTO L0001 L0002 .... Next Command
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Alain,
well yes or no, but it's just longer to type![]()
Joe
Yes, I think you got it right.
To make it easier...
GOTO $+1
is the same as
NOP
NOP
well instruction-cycle wise (can I say that??? )
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I should probably have explained:
I don't leave the dummy statement in a finished program. Usually, it occupies a space where another function, or a GOTO, or a GOSUB will be placed.
I really like Alain's
WHILE 0
WEND
. . . which I assume I could render on one line as WHILE 0 : WEND, and then go from there.
But the GOTO $+1 intrigues me, too. Will that work as a PBP command?
Russ
N0EVC, xWB6ONT, xWN6ONT
"Easy to use" is easy to say.
yeah it will work, but you need to use the @ sign before (how it's called anyways, here we use to call it commercial A, then AT... )as it's an ASM statement
@ GOTO $+1
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks