Re: What suffixes are supported/for what languages

[Shigio Yamaguchi]

> A parser bound to each suffix - just like the 'else if ( suffix )
> parser' tree hardcoded in gctags/gctags.c that i modified by hand
> to add new suffixes for an existing parser.
> maybe you could start by adding a command that would display the
> built in bindings of suffix to parser?
> 
> you would have an internal default list used if there were no
> related entries in the .global config and a command like
> 'gtags --config suffix-per-parser' would print out:
> 
> parse_C : c;
> parse_C++ : C,H,cc,cpp,hpp,cxx;
> parse_detect_C_C++ : h;
> parse_Java : jar;
> 
> or something like this, just make it easy to parse for machines
> and humans.

Anyway, we must modify parser by hand, because all ctags style parser,
including gctags, decide language type by suffix. (Some parser may have
its own config file. In that case, we must modify the file instead.)
If a parser doesn't understand suffix '.msg', the parser can do nothing
about a file 'xxx.msg'.

So, I understand that your suggestion is to treat multi parser.
In current GLOBAL, we can do it like this:

default:
        suffixes=c,h,C,H,cc,cpp,hpp,cxx,jar:\
        GTAGS=multi_parser %:\
        ...

[multi_parser]
-----------------------------------------------
#!/bin/sh
for file in $*; do
        case $file in
        *.c)    parser=parse_C;;
        *.[CH]|*.cc|*.[ch]pp|*.cxx)
                parser=parse_C++;;
        *.h)    parser=parse_detect_C_C++;;
        *.jar)  parser=parse_Java;;
        *)      ...;;
        esac
        $parser $file
done
-----------------------------------------------

Isn't it enough?
--
Shigio Yamaguchi - Tama Communications Corporation
Mail: address@hidden, (Spare mail: address@hidden)