Highlighting of syntax for custom files

[shusterboris]

Good day, everybody!
I have few files with special syntax in my C/C++ project.
At first I need add string "--" as begin of comments. Added
"//" | "--" { yybegin(SCOMMENT); }
to CSybbolTokenizer.lex and CXref.lex
... indexer is working but nothing changed

The next thing... I need add a few new keywords and syntax like MODULE .... ENDMODULE as declaration.
I tried everything: regeexps in the ctags opt-file, tried to create custom Analizer and jflex but unsuccessfully

I understand the question sounds crazy... but do we know something that help me to solve the problem

[shusterboris]

Ok, As for syntax highlighting for specific language that doesn't support by ctags, I solved the problem. May be this is dirty, but... In the package opg.opengrok.indexer.analisys I created folder bacis (this is the name of language I need parse, very specific language for some legacy system). In this package I created classes BacisAnalizer, BacisSymbolTokenizer, BacisXRef using classes for C as examples. Also I created *.lex? files: added some specific language construction, like comments and so on. Also I created my own class Consts that contains list of keywords. Please note that all files are in one package, unlike other languages implemented here (XRef in the jar, lex-files in the jflex folder) to avoid name conflicts.
Ah... also I added BacisAnalizerFactory to list of factories in the CTags. I understand that all this is rude and unladylike. Apparently, you can't teach an old dog new tricks... But maybe it will be useful to someone

[shusterboris]

The problem I didn't manage to solve: implementation of search by declaration. In theory, we need to create correct regular expression, add ctags option, something like:
--langdef=bacis
--langmap=bacis:.bam.bad.bac.uid
--kinddef-bacis=d,definition,Definitions
--regex-bacis=//\1/d
then start indexer with custom analizer -A :org.opengrok.indexer.analyzers.Bacis --option=path_to_options_file
and have a fun...
But currently it doesn't work. Indexer starts, but don't generate any tags
I hoped investigate it, using
@test
void testDoCtags() throws Exception {
Definitions result = getDefs("bug16070/arguments.c");
assertEquals(13, result.numberOfSymbols());
}
in the CTagsTest (I did see this advise in discussions here)
But all tests in the package returns null as result. Very strange.

[shusterboris]

It works if kinddef option change to "function". And it was not clear for me on the first look. In the expression --regex-bacis=//\1/d "\1" means "first matched group that regex found is a name of function"