>-----Original Message-----
>From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] 
>Sent: 13 October 2005 13:46
>To: Microcontroller discussion list - Public.
>Subject: Re: [PIC] Success (Was:- Very Newbie -Progress!)
>
>
>> From: "Olin Lathrop"
>
>> (65536 increments/rollover) / (4096 increments/second) = 16
>
>I made a second post very shortly after the first as I soon 
>spotted the division being the wrong way around and made the 
>corrections
>
>> >         w_temp                 ;you need these variables 
>in the list
>> >         status_temp
>> >         counter
>> >         shadowb
>> 
>> I don't know what you're trying to do here, but you can't just use a 
>> variable name as an opcode
>
>Theey aren't being used as opcodes. I don't know how Ed is 
>declaring his variables, whether with cblock, res, whatever, 
>so simply said in the comment that these variable names are used
>
>> >         movlw   0x08           ;or use .8 for a decimal value,
> 
>> Please don't use the .<decimal number> syntax
>
>I don't see anything inherently wrong with it
>
>> I think Microchip would like to get rid of it and keeps it for 
>> compatibility with ancient code
>
>Do you have any evidence for that ? I can't see any easy way 
>for them to get rid of even if they did want to, apart from 
>just dropping it from future MPLAB. Any old code would then 
>have to be processed with an old version of MPLAB. Given that 
>7.x is quite advanced and still allows various number systems 
>it wouldn't necessarily be that onerous to do so if 8.x or 
>later had only hex and binary (not that I can see it ever happening)

I think you are misinterpreting Olins comments.  He dosen't wan't to abolish the use of decimal bases in MPASM, but rather always make decimal the default radix, so the dot is never required.  I agree with him, the dot notation is an annoyance.  It's easily forgotten and easily missed when reading the code.  

As decimal and hex are by far the most widely used bases, and MPASM supports the use of the common C style hex notation (e.g. 0x1234), it's seem just neater and more obvious to do things this way.

Regards

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================

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