[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: cost of popen()
From: |
Bakken, Luke |
Subject: |
RE: cost of popen() |
Date: |
Fri, 17 Jun 2005 10:07:35 -0400 |
Hideki IWAMOTO wrote:
> On Fri, 17 Jun 2005 16:01:14 +0900, Shigio Yamaguchi wrote...
>> Currently, the interface is in command layer. This brings the
>> performance problem to gtags, because the command call far costs
>> than the function call. To solve the problem, we should move the
>> interface from the command layer
>> to the function layer, that is, links gtags-parser as part of gtags.
>
> Does this mean stopping supporting plug-in parser?
It shouldn't if the parser API is defined well. You could even support
dynamic objects for plug-in parsers.
I like the idea!
Luke
- Re: cost of popen(), (continued)
- Re: cost of popen(), Hideki IWAMOTO, 2005/06/16
- Re: cost of popen(), Shigio Yamaguchi, 2005/06/16
- Re: cost of popen(), Shigio Yamaguchi, 2005/06/17
- Re: cost of popen(), Hideki IWAMOTO, 2005/06/17
- Re: cost of popen(), Shigio Yamaguchi, 2005/06/17
- Re: cost of popen(), Hideki IWAMOTO, 2005/06/17
- Re: cost of popen(), Shigio Yamaguchi, 2005/06/17
- Re: cost of popen(), Hideki IWAMOTO, 2005/06/19
- Re: cost of popen(), Hideki IWAMOTO, 2005/06/19
- Re: cost of popen(), Shigio Yamaguchi, 2005/06/19
RE: cost of popen(),
Bakken, Luke <=