Ok then, lets try. The following can be an SQL table.
First, you have to decide on what set of conf. bit names you stick
with it forever. We have to "draw" the table structure (in fact, the field
structure):

 1. - the name which will remain unchanged
 2. - the new name changed by Microchip
 2. - the size of it (byte, word, bit, etc.)
 3. - the name of the parent byte (if is member of a byte)
 4. - the physical memory address (if is the case)
 5. - the position inside the parent byte (if is the case)
- add the other required fields if is the case;

The above structure is not final and will be decided by Jallib developers.

This table can be maintained with a program with a nice graphical interface.
The new names that will remain unchanged can be added with ease and in
general,
is much more easy to maintain a little database than to provoke a chain of
changes
prone to bugs. You won't ever need to touch old and proven samples and
device files.

The generating program will pick the new name from Microchip files (of a
new device) and will search
in the database for the "real" name designated by us. And you do this ONLY
for new microcontrollers - AMEN!
;-)

In this way, Microchip will never be able to negatively influence the
Jallib project!!!
Lets put to a good use the fact that we don't depend on MPLAB assembler or
GPUTILS assembler!
We have to get out of the pack and live independently.
I suggest you to start with a previous and tested .svn version.

Is like an LTS (long time support) Linux distro.

Best regards,
Vasi


On Wed, Mar 5, 2014 at 2:25 PM, Rob Hamerling <[email protected]>wrote:

>
>
> On 05.03.14 05:51, vasi vasi wrote:
>
>> I still don't get why everything should change again (break) at every
>> MPLAB-X change.
>> Why we can't have a standard set of names (our own) for
>> configuration bits?
>>
>
> Go ahead, do a suggestion, design a scheme. What keeps you?
>
>
> --
> R. Hamerling, Netherlands --- http://www.robh.nl
>
> --
> You received this message because you are subscribed to the Google Groups
> "jallib" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/jallib.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Vasi

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to