Hi guys,
So far I didn't see a reaction to my proposal for the naming convention
for multiple USARTs, so I assume you all agree.
I have been working on a renaming of multiple USART and SSP modules,
probably later for other multiple modules occurences (CCP?).
- for the first USART there is always an unqualified variable
(without a '1') defined as such in MPLAB, or added as alias
when qualified MPLAB contains a qualified name (RC1REG will
have alias RCREG)
- for the second USART there is always a qualified name with a
'2' at the end of the name, defined as such in MPLAB or added
as alias (RC2REG will have alias RCREG2).
- similarly for bits in non-specific USART registers (like
interrupt bits)
A library supporting the first or only USART should use unqualified
names, a library supporting the second USART should always use a name
with a '2' as suffix, no conflict when both USARTs are used in the same
program.
Note (Matt): The names with a '1' suffix as added on end October will
disappear!
For SSP modules the naming convention must be slightly different,
because there are SSP modules with multiple SSPCON registers. Therefore
the sequence number must be embedded. For the first SSP module names (or
aliases) will be unqualified like: SSPCON1, SSPCON2, etc. For the second
SSP module the names will be SSP2CON1, SSP2CON2, etc.
The differences between current and future names will be minor, but my
dev2jal script is better prepared for a consistent naming for other
multiple modules. A consistent naming (per module type) makes it easy to
build libraries for PICs with multiple similar modules.
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
