<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>At the moment, no, it would not work to just replace the pattern syntax used in MTR files with the ^...$ format.  That is because (in ACE at least) support for (all 3 types of) pattern matching are specific to the modules of the infrastructure in which they apply.  That is to say, the regex handling in token mapping is not accessible to syntax rules or transfer rules.  Ditto the pattern handling used for morphology.  I’m certainly not a fan of this state of affairs, but changing it would take some doing.  I be thrilled to see a unified approach, possibly based in the notion of regexes as types fitting between *string* and “kangaroo” as proposed earlier, but it wouldn’t be simple, and I’m not 100% sure it would be an improvement, at least in the morphology department.  One vexing wrinkle in particular would be the status of capture groups (necessary both for morphology and token mapping).  These would conceptually be similar to reentrancies, but they are subatomic (for lack of a better term).  I’m also not sure what the formal status of a string that contains a capture group reference would be, or how unifying things with it would be implemented.  I imagine the broader unification-based parsing community probably has experience with something like this that could be interesting to look at.  I worry somewhat that efficiency could be a concern, although it seems like the typical use cases would be unlikely to become too entangled.</div><div><br></div><div>Best,</div><div>Woodley</div><div><br>On Sep 7, 2018, at 9:45 AM, "<a href="mailto:goodman.m.w@gmail.com">goodman.m.w@gmail.com</a>" <<a href="mailto:goodman.m.w@gmail.com">goodman.m.w@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" preoffsettop="2686"><div style="word-wrap:break-word"><div>P.S. By the way, the example you turned up from mtr.tdl is actually to be interpreted as a pattern match, in the spirit of regular expressions.  Arguably the regular expression syntax used in token mapping should be used for transfer / trigger rules as well.</div></div></blockquote><div> </div><div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">Yet another un(der)documented string-matching implementation? In this case, though, the pattern is enclosed in a string so from the perspective of syntax it doesn't change anything. Can we currently just replace these with regexes? [ PRED ^.*_n_.*$ ]<br></div></div></div></blockquote></body></html>