| Re: [cdt-dev] Assembly language keywords and directives |
|
HI Aaron, We also have the same issue,
multiple families for one debugger. One way to handle this is to have an
assembly language defined for each family, you can associate a specific
language to the project. This can be done during project creation. The only thing
you will need to do is to provide your own asm scanner for each assembly
language. I am looking in the case where I want to extend the standard CDT
assembly scanner to provide my additional set of token highlight (keywords/directives,
etc…). I think this is what you need as well. Regards, Patrick From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf
Of Aaron Spear This brings up a possibly more
general issue of how people are managing the assembly editor. I know that
at Mentor we had a single debugger that could target multiple families (ARM,
PowerPC, MIPS, …) and the fact that there was not a flexible mechanism
for choosing which assembly was in use was problematic (we ended up creating
our own assembly editor). I think that ideally there should be any number
of named sets of the keywords/directives (extension point?), and which one is
used by the editor in any given file is an attribute possibly inherited from
the containing project, or something like that. As multi-core becomes more
prevalent, being able to mix different families would be key. Cheers, Aaron Spear, VMware From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf
Of Chuong, Patrick Hi, Our compiler supports additional assembly keywords and directives,
is it possible to add additional keywords and directives to the existing set
for assembly editor? I am looking at the code and couldn’t find a way to
do so. Do I need to make my language adaptable to ILanguageUI and duplicate
assembly language code scanner provided by CDT? Thanks, Patrick |