in reply to Re^3: Reusing a complex regexp in multiple spots, escaping the regexp
in thread Reusing a complex regexp in multiple spots, escaping the regexp

I took a quick look into Ralf Brown's Interrupt List and the material is far too vast to be easily understood.

Please consider providing a SSCCE with sample input if you need further help.

Please be aware that the AI generated code is far from being correct or the best approach. (I only tossed two prompts at it to generate that output.)

Hints for improvement

Hope this helps :)

Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery

Replies are listed 'Best First'.
Re^5: Reusing a complex regexp in multiple spots, escaping the regexp
by ecm (Novice) on Apr 13, 2026 at 17:45 UTC
    I took a quick look into Ralf Brown's Interrupt List and the material is far too vast to be easily understood.
    Yes, it is not for the faint of heart.
    Please consider providing a SSCCE with sample input if you need further help.
    The answers so far are already very satisfying.
    the Xs in your hex character class look wrong, I suppose they are only allowed at the beginning like xFF
    No, some MEM and @ (CALL) references do use literal Xes instead of hexits. Such as if there's references to "MEM xxxxh:xxx0h - Multiprocessor Specification - FLOATING POINTER STRUCTURE" or "CALL xxxxh:xxxxh - Alternate Multiplex Interrupt Specification TSRs"
    you should consider a match all clause like (?<unknown>.*) at the end of your branches, to catch errors or missing implementations (e.g a weird number where you expected a hex)

    I don't understand this. I don't want to match anything if there's no hyperlink reference in a given line. (Actually in one case I do want to know nothing was matched but it's not a problem, I just do last MATCHLINK before and if the code afterwards is run after having entered a single "link" item, I know nothing was matched.)

    Thanks!