I also think this should be in some config var
see http://defect.opensolaris.org/bz/show_bug.cgi?id=17849
which deals with similar problem

we have a class that handles ctags params and how to execute it
it's right now not very configurable
would be cool if one could inject additional ctags params there

so I suggest starting there, if Martin can pick it up I will be only happy, can do the mentoring for him
(it's a low hanging bug, so easy to pick up ;) )

hmm?
L


On 19.3.2012 16:10, Vladimir Kotal wrote:

Hi all,

I just realized most of the assembler function definitions in a code base we are indexing are not detected by OpenGrok because of the macros used to define these functions.

They look like this (including the whitespace):

        ENTRY_NP(foo)

    /* some assembly code */

        SET_SIZE(foo)

There is also a problem with the whitespace at the beginning of the lines since ctags will not pick up the individual instructions in the function but I am more after the function definitions now.

There seems to be easy remedy in ctags with:

/opt/ctags\-5.8/ctags --language-force=asm --language-force=asm --regex-asm='/(ENTRY_NP|ENTRY)+\(([^ ]*)\)/\2/f/' ./test\-whitespace.c

which will produce the types correctly:

$ cat tags
!_TAG_FILE_FORMAT 2 /extended format; --format=1 will not append ;" to lines/
!_TAG_FILE_SORTED       1       /0=unsorted, 1=sorted, 2=foldcase/
!_TAG_PROGRAM_AUTHOR    Darren Hiebert  /dhieb...@users.sourceforge.net/
!_TAG_PROGRAM_NAME      Exuberant Ctags //
!_TAG_PROGRAM_URL       http://ctags.sourceforge.net    /official site/
!_TAG_PROGRAM_VERSION   5.8     //
foo     ./test-whitespace.c     /^      ENTRY_NP(foo)$/;"       f


Now, how to pass this extra argument (--regex-asm and its value) to OpenGrok indexer ?


v.
_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss

_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss

Reply via email to