You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2018/08/15 14:58:00 UTC
[jira] [Resolved] (DAFFODIL-1984) Separator prefix of terminator -
not getting longest match
[ https://issues.apache.org/jira/browse/DAFFODIL-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Beckerle resolved DAFFODIL-1984.
----------------------------------------
Resolution: Fixed
Assignee: Dave Thompson (was: Michael Beckerle)
Fixed in 73d071750b7b484e010cb357f226b93de2f4439a
> Separator prefix of terminator - not getting longest match
> ----------------------------------------------------------
>
> Key: DAFFODIL-1984
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1984
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.2.0
> Reporter: Michael Beckerle
> Assignee: Dave Thompson
> Priority: Blocker
> Fix For: 2.2.0
>
>
> Regression in new separator/sequences code.
> When the separator is a prefix of the terminator, or any other piece of in-scope terminating markup, then the separator match is preferred to the longest match, and that makes any format that depends on longest-match disambiguation to fail.
> The one example we have of this is in VMF's spec scraper.
> So we also need a test of this in daffodil-test to have better coverage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)