Re: [RFC] New requirement for plug-in parser.

[Shigio Yamaguchi]

> gtags-parser cannot satisfy requirement 2.
> Therefore, this should not be required of plug-in parser.

OK. I rewrote the requirement as follows.
How about this?

------------------------------------------------------------------------
[Requirement of plug-in parser]

Plug-in parser must process the files in the order they are given
in the argument. In each file, any order is acceptable.

Examples:

a. Good example

The following 'good-prog' does correct operation as a plug-in parser.

        $ good-prog a.c b.c        <= order: a.c -> b.c
                    ~~~~~~~
        main          25 a.c  main(int argc, char *argv[])
        func          45 a.c  func(int a) {
        sub2          20 b.c  sub2() {
        sub1          10 b.c  sub1() {
                          ^
                          |
                         *** order: a.c -> b.c (Good!)


b. Bad example

The following 'bad-prog' does wrong operation as a plug-in parser.

        $ bad-prog a.c b.c        <= order: a.c -> b.c
                   ~~~~~~~
        main          25 a.c  main(int argc, char *argv[])
        sub2          20 b.c  sub2() {
        sub1          10 b.c  sub1() {
        func          45 a.c  func(int a) {
                          ^
                          |
                         *** order: b.c -> a.c (BAD!!!)

(end of requirement)
------------------------------------------------------------------------
--
Shigio YAMAGUCHI <address@hidden> - Tama Communications Corporation
PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3