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... ;)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.