[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: plug-in parser's output
From: |
Shigio Yamaguchi |
Subject: |
Re: plug-in parser's output |
Date: |
Thu, 07 Jul 2005 14:47:55 +0900 |
> gtags can't handle plug-in parser's output like this.
>
> === Emacs ctags ===
> Bob::operator new 28 ./testsuite/20_util/memory/allocator/10378.cc static
void* operator new(
>
> === Exuberant ctags ===
> operator unsigned long function 49 ./testsuite/27_io/basic_filebuf/seekof
f/10132-2.cc operator unsigned long() const { return character; }
>
> Should we improve gtags.conf? Or should we give up?
How about ignoring such lines in the script defined in gtags.conf?
But I feel the doubt in keep the support of plug-in parser.
Isn't it better to make better built-in parsers?
What do you think?
--
Shigio YAMAGUCHI <address@hidden> - Tama Communications Corporation
PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3
- plug-in parser's output, Hideki IWAMOTO, 2005/07/07
- Re: plug-in parser's output,
Shigio Yamaguchi <=
- Re: plug-in parser's output, Hideki IWAMOTO, 2005/07/07
- Re: plug-in parser's output, Hideki IWAMOTO, 2005/07/18
- Re: plug-in parser's output, Shigio Yamaguchi, 2005/07/18
- Re: plug-in parser's output, Hideki IWAMOTO, 2005/07/19
- Re: plug-in parser's output, Hideki IWAMOTO, 2005/07/20
- Re: plug-in parser's output, Shigio Yamaguchi, 2005/07/20
- Re: plug-in parser's output, Hideki IWAMOTO, 2005/07/20