Hi Joep,

Joep Suijs wrote:

[RobH]
>> It seems you need for ADC something more. We have already a
>> classification in groups. The ADC_GROUP is currently only mentioned in a
>> comment in the device files but could easily promoted to a constant.

> I think this is what I mean. I can't see where this comes from, but
> only see the 'adc' group. have other devices (like SSP) also version
> numbers?

You may have missed (or forgotten about) an earlier discussion with Eur 
when he suggested to use the method of the Microchip C compiler for the 
18Fs (MCC18) with ADC. See: \mcc18\h\pconfig.h and mcc18\h\adc.h, and 
maybe also code in \mcc18\src\pmc_common\adc.

Since MCC18 does not deal with midrange and baseline PICs and there are 
a number of PICS in these families with another ADC variant I added ADC 
_V0 for the little ones.

There are also other group definitions in MCC18, but not for SSP I believe.


> I don't say we need different libraries. I say we need a 'layer'
> between the devices and the code.

Understood and agreed.


>> Here you count also the differences in bit names. Maybe these
>> differences are too small to justify separate libraries.
> Not libraries but code to deal with. When only the names differ, you
> can make aliasses at the top of the library and you are done!

Yes aliasing is another possibility. If a bit or register has a 
different name (for example EEDAT in stead of EEDATA) then an alias like 
'var volatile byte EEDATA at EEDAT' would work.  But if EEDAT does not 
exist you cannot declare an alias. So you need always some conditional 
compilation (like with if defined(EEDAT) ...).

Regards, Rob.


-- 
Rob Hamerling, Vianen, NL (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
-~----------~----~----~----~------~----~------~--~---

Reply via email to