Might I suggest that you make the radix explicit in all your code (or examples).
E.G. MOVLW 16D
makes it more idiot proof, yet clear to the human what the value means.

I have found that different assemblers assume different radixes so I always
write with explicit radix values so I know that they'll always work as expected,
or generate an error message which flags the problem.

Robert

Andrew Warren wrote:
>
> Roberts II, Charles K. <PICLIST@mitvma.mit.edu> wrote:
>
> > I am trying to use the 16 by 16 bit divide from
> > http://home.netcom.com/~fastfwd/answers.html#PIC00094. I can not
> > get it to work.
>
> Charles:
>
> Since the code is known to work (I wouldn't have put it on my web
> page if it didn't), the problem must be elsewhere.  Let's start with
> the easyest possibility first:
>
>     Is your default radix set to decimal (i.e., is there a "LIST R =
>     DEC" line in your source code)?
>
>     If not, the "MOVLW 16" at the start of the routine is being
>     interpreted as "MOVLW 22".  To fix this, don't add a "LIST R =
>     DEC" to your source; you'll probably break something else that
>     assumes hex radix.  Instead, just change that line to "MOVLW
>     0x10".
>
> If that wasn't the problem, please post some more details... Like
> what result you get for a specific set of inputs.
>

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics