According to Andy Wardley:
In a block off the old Chip:
Let's call them \m{X} to require metadata tag X, and \M{X} to forbid
tag X. e.g.:
/\m{italic}\m{bold}Yes!/
I think a better solution would be to add a metadata-matching modifier
('/t' for 'tags' was one possibility that came to mind) that would allow
the familiar (SG|HT|X)ML tags to be overloaded as metadata specifications.
That's not necessarily appropriate for a metadata system that's more
complex than simple inline markup. Metadata may be a tree or some
other such structure.
Still, it's an interesting idea we should keep in mind.
<?foo> # may be in a <foo>...</foo>
That's redundant, IMO. It shouldn't be necessary to specify optional things.
Perhaps something like:
my $perlorg = qr/\.perl\.org/;
/<a href=~$perlorg>.*<-a>/t;
Ah, callouts to qr// objects -- I hadn't thought of that. Another
ingredient to add to the mix.
--
Chip Salzenberg - a.k.a. -
<chip(_at_)perlsupport(_dot_)com>
"... under cover of afternoon in the biggest car in the county?!" //MST3K