Well, I'm glad you understand it -- I don't. And now I need to peel open my Camel (4th edition) and figure out what your regexp does. After 15 years, I'm still learning too. :/
Alex / talexb / Toronto
Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.
| [reply] |
Thanks for posting your solution to this -- I've managed OK with regexps, but your post encouraged me to get a little more familiar with how lookaround assertions work. I'm going to document the regexp you've provided in order to show that I believe the instructions are still incorrect (see also my post here where I list all of the possible legal patterns that I think exist).
Alex / talexb / Toronto
Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.
| [reply]
[d/l] |
) # .. end of first group (is this missing
# a '?' to show it's optional?)
Nope. The first group exists, even if it's empty. That is called out explicitly. The only reason for the ? after the non-capturing group is because the X itself is optional - and not present when the second group is not present.
As for your other post, again, you're using the more precise instructions as definitive instead of the less precise instructions (with explicit examples). If we take the examples as definitive, and fill in their ambiguity with the precise instructions instead of the other way around, we see that the X is always followed by something. That the precise instructions would seem to allow X without anything after them becomes moot because we are starting with the higher-level instructions which already said that wasn't allowed (through the example).
The problem is that communication is a two-way street, and you're using your definitions of "set" and "might" and "zero or one" instead of theirs. That theirs is nonsensical is completely beside the point - they showed us their flawed dictionary through the examples. Not everyone understands that "set" can include the null or empty set. Or that their use of "might" is ambiguous (they mean "might include a, might include b, might include c" and left off the "but must include something" bit, thinking that "set" means "something" and can never be empty).
Think about this as a list of items in perl:
@r = (@$a, @b, c,); # c would be a function call!
In perl, those commas, which represent "X" in the OP's question, are required. Except for the last one. However, in other languages, such as C, that last one is an error. And that follows the requirement - you can have that X, but only if something follows it, though what that is can be anything. To complete the simile, "a" becomes "@", "b" becomes "$", and c becomes "a name (such as a, b, c here)". The OP just can't allow that trailing comma, because he's reading something more like C than Perl. (Of course, in perl, "c", being "a name", isn't actually optional unless the first two are also missing.)
The hardest part about any spec, as always, is figuring out what the author meant as opposed to what they said. And that means understanding who the author is and where they're coming from. In this case, it was a wild-assed guess. But that's one of the beauties of the site - I'm not regularly the one to predict what a petitioner is asking, but it's pretty often that someone does predict it. It just happened to be me this time. :) | [reply]
[d/l]
[select] |
:) Thanks for your explanation. Because the examples seemed to contradict the rules, I went with the rules. This is an interesting exercise and lesson for me.
I think these rules could have been written more clearly .. but I won't go on any more about this. It's been an education.
Alex / talexb / Toronto
Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.
| [reply] |
Awesome, it works! 13 years programming Perl, and I'm still learning new sh*t. | [reply] |