Follow-up Comment #4, bug #64478 (group groff):

This'll be easier now that we have an independent function to lexically
analyze hyphen exception words as request arguments.


commit 13c6faac43a8aa7dbbd80cbe18115e648a776e49
Author: G. Branden Robinson <[email protected]>
Date:   Fri Apr 10 09:34:22 2026 -0500

    src/roff/troff/env.cpp: Refactor.
    
    * src/roff/troff/env.cpp: Lift logic for parsing a hyphenation exception
      word request argument into its own function, so that other requests
      can use it.
    
      (read_hyphenation_exception_word): Implement it.
    
      (add_hyphenation_exception_words_request): Call new function from
      here.

commit f1454c96e50be6bb6ae1057a4c2b5dccf8d63a2f
Author: G. Branden Robinson <[email protected]>
Date:   Sun Apr 12 05:45:56 2026 -0500

    src/roff/troff/env.cpp: Generalize new function.
    
    * src/roff/troff/env.cpp (read_hyphenation_exception_word): Support
      being called with null pointers to store the breakpoint count and
      positions, so that a request that isn't interested in them need not
      reserve storage for them.  Consequently, default these function
      parameters to null pointers.  Dereference and populate the breakpoint
      count and positions only if these data are wanted.  Add assert(3)ion
      that either both pointers are null or neither one is.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64478>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to