OK, i am a TOTAL noob, so be gentle
You can enumerate bitfields, but commenting is better for x-refing.
I'm not sure how comments interact with x-refs.. i'll have to play with that more. especially dont undersand the difference between ":" and ";"
For maps, I usually manually adjust the address to accurately represent the DPP and comment the name.
So. I totally don't get what you are saying... can you cut and paste an example? Keep in mind that while i understand the c166 pretty well at this point, IDA pro still baffles me.
Text search will find comments, but there isn't a need really. When do you find the need to search for comments?
e.g. say it says "jb 0xFD66.5 blah" and i want to comment it as '; B_ehfm' because i can't name "0xfd66.5" B_ehfm...
how do i search for B_ehfm? or are you saying if i do it right, B_ehfm will show up somehow as a x-ref?
What kind of shared DB did you have in mind?
Basically, some sort of editable/import/exportable db of function and ram locations.. I know IDAPro can export symbol tables... not sure about importing, but I know i can probably write some sort of plugin for it (once i figure out how plugins work etc). Also, would need some sort of metadata format so we can include conversions...
Altho we should really do it ASAP2 style, and have some sort of DB of "types" rather than repeat conversions for every damn item... then i could write a script to convert that to an .ecu file (and back) for ME7L, etc.
Not sure how to handle merging etc. but if i can do it all with a git repo with text files, i think it can work. I could also write a website/sql type of thing for it, but that would be a lot of work and probably beyond what i'm willing to work on solo.
This all depends, of course, if there is enough interest in some sort of shared effort.