[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Performance profiling of makeinfo

From: Gavin Smith
Subject: Re: Performance profiling of makeinfo
Date: Tue, 14 Apr 2015 21:06:23 +0100

On 14 April 2015 at 18:14, Gavin Smith <address@hidden> wrote:
> On 26 December 2014 at 09:27, Patrice Dumas <address@hidden> wrote:
>> Underlying text is always used to determine the text case.  It is,
>> however, only useful if the text case was changed.  So there could be
>> some gain to ignore it if the case is not changed, since changing case
>> is not very common.  Maybe, if not defined, instead of defining it,
>> $paragraph->{'word'} could be used line 438 in
>>       } elsif ($paragraph->{'underlying_word'} =~
>> /[$end_sentence_character][$after_punctuation_characters]*$/
>>            and $paragraph->{'underlying_word'} !~
>> /[[:upper:]][$end_sentence_character$after_punctuation_characters]*$/) {
> I've tried putting 'word' here instead as a preliminary step to
> disabling the 'underlying_text' operations, but it fails the test
> suite:

Apparently 'underlying_word' is used for the $transparent argument to
the function which can be used to make added characters invisible for
the purposes of deciding whether we are at the end of a sentence. I've
made another change to not process the two strings in parallel when
they are the same, and the test suite passes for this.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]