Re: Automatic documentation of match operations?

which depend on: ...

Since you mention pos at the bottom, perhaps it makes sense to add that to the list of things that matches depend on?

BTW, you may be interested in my nodes here and here.

Comment on Re: Automatic documentation of match operations?

Replies are listed 'Best First'.
Re^2: Automatic documentation of match operations? by LanX (Saint) on Apr 10, 2023 at 16:43 UTC
Oh thanks a lot for the links, very nice. > perhaps it makes sense to add that to the list of things that matches depend on? Point is that there are far more side effects than just `pos` and I wanted to keep it simple for a start. Visualizing all side effects would be complicated. And testing challenging. Resetting the string is already solving it. There are various fuzzy ideas at play here automation of documentation testing of documentation case folding of conditions/deductions (more a math problem) drawing the "best" table drawing a table on demand for user requirements IDE support code intelligence regression testing of Perl versions testing of Perl ports (like to JS) Bottom line: a meditation... ;) Cheers Rolf _{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :) Wikisyntax for the Monastery}	[reply]

Replies are listed 'Best First'.

> perhaps it makes sense to add that to the list of things that matches depend on?

Point is that there are far more side effects than just pos and I wanted to keep it simple for a start.

Visualizing all side effects would be complicated. And testing challenging.

Resetting the string is already solving it.

There are various fuzzy ideas at play here

Bottom line: a meditation... ;)

Cheers Rolf
_{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)

Wikisyntax for the Monastery}