> On Nov 24, 2015, at 10:28 AM, Eric Covener <[email protected]> wrote:
>
> On Tue, Nov 24, 2015 at 10:21 AM, Jim Jagielski <[email protected]> wrote:
>> For these types of paths, where we use a switch/case against
>> the 1st char of the token, the real reason why we used that
>> impl was to avoid the (expected) expensive string comparison.
>
> Maybe naively, I thought we were saving some potential function
> call overhead here rather than some strcasecmp overhead.
Yeah... you are likely right. In which case, we should adjust
ala the suggested
if (!ap_casecmpstr(token+1, "ublic")) {
implementation. Yeah, that's ugly, I agree.
