 |
 |
 |
- Original Message From: "Pete Cordell"
> Personally I think that, subject to occurrence constraints, the particle
> that is currently gobbling up input, should have priority (i.e. they're
> greedy). That ... has similarities to how regular expressions behave.
Apologies for answering my only e-mail, but just to check that I wasn't
mistaken about the behaviour of regular expressions, I put together the
following Perl program:
#!/usr/bin/perl
$instance = 'AAA';
$instance =~ /(?:A(.+))+/;
print "instance: $instance\n";
print "captured: $1\n";
This gave the output:
instance: AAA
captured: AA
which seems quite sensible to me and I think XSD1.1 should emulate it.
(In case it is not obvious, my A in the regular expression corresponds to an
<xs:element ref='apple'/> and the . the xs:any wildcard. Just in case
you're out of practice on your PCREs, the (?:...) construct provides
grouping without any capturing. One day I won't have to look that up!)
Regards,
Pete Cordell
Codalogic
For XML C++ data binding visit http://www.codalogic.com/lmx/
From mike@s... Wed Jun 25 23:31:30 2008
Received: from maggie.w3.org ([19
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |