[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RFC] Replacing the sort filter of global(1).
From: |
Shigio YAMAGUCHI |
Subject: |
[RFC] Replacing the sort filter of global(1). |
Date: |
Sun, 22 Jan 2006 15:50:18 +0900 |
Hi all,
I would like to replace global(1)'s current sort filter with new one.
Now, global(1) calls gnusort(1) to sort the output.
On the other hand, we have developed new sort filter which is
much faster than gnusort in almost case. (Essential part of it
was written by Iwamoto san.)
You can use this filter by typing like follows:
$ global --devel <argument>
I think there is no problem about new filter after testing.
Therefore, I suggest the followings:
o Replace gnusort(1) with new sort filter (gtags --sort).
and delete gnusort(1) from the package.
o Merge new sort filter(gtags --sort) as part of global itself.
[current implementation]
process1 process2
+-------------+ +-------------+
| global |==>| sort filter |===> output
+-------------+ +-------------+
|
v
[new implementation]
process1
+--------+-------------+
| global | sort filter |===> output
+--------+-------------+
o Use system's POSIX sort command for plug-in parser.
Since POSIX sort command is even needed for plug-in parser,
we should check whether or not POSIX sort exists in the target
system using configure script. If POSIX sort is not found,
the use of plug-in parser will bring an error message like:
$ gtags
Error: POSIX sort(1) is required to use plug-in parser.
What do you think?
Are there any problem?
--
Shigio YAMAGUCHI <address@hidden> - Tama Communications Corporation
PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [RFC] Replacing the sort filter of global(1).,
Shigio YAMAGUCHI <=