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/01/25 22:26:00 UTC
[jira] [Updated] (DAFFODIL-1005) Abort exception for bitOrder
changing when not on a byte boundary
[ https://issues.apache.org/jira/browse/DAFFODIL-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Beckerle updated DAFFODIL-1005:
---------------------------------------
Component/s: (was: General)
(was: Front End)
TDML Runner
> Abort exception for bitOrder changing when not on a byte boundary
> -----------------------------------------------------------------
>
> Key: DAFFODIL-1005
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1005
> Project: Daffodil
> Issue Type: Bug
> Components: TDML Runner
> Affects Versions: s14
> Reporter: Elizabeth Fahl
> Assignee: Michael Beckerle
> Priority: Major
> Fix For: deferred
>
>
> When the bitOrder is changed in the documentPart at a bit that is not on a byte boundary, there should be an error. This is erroring but with an Abort exception instead of a nice error message.
> edu.illinois.ncsa.daffodil.exceptions.Abort: bitOrder can only change on a byte boundary.
> [error] edu.illinois.ncsa.daffodil.exceptions.Assert$.abort(Assert.scala:95)
> [error] edu.illinois.ncsa.daffodil.exceptions.Assert$.usageErrorUnless(Assert.scala:71)
> [error] edu.illinois.ncsa.daffodil.exceptions.Assert$.usage(Assert.scala:62)
> [error] edu.illinois.ncsa.daffodil.tdml.Document$$anonfun$checkForBadBitOrderTransitions$1.apply(TDMLRunner.scala:953)
> See test "bitOrderChangeInvalid" in daffodil-test/src/test/scala-debug/edu/illinois/ncsa/daffodil/section05/simple_types/TestSimpleTypes2.scala and daffodil-test/src/test/resources/edu/illinois/ncsa/daffodil/section05/simple_types/BitOrderInvalid.tdml
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)