Changes between Version 19 and Version 20 of StructuredBinaryData

Timestamp:

2012-08-07T05:57:55Z (14 years ago)

Author:

Sean Bartell

Comment:

Outer struct access is complete

StructuredBinaryData

@@ -178 +178 @@
 parameters. Currently, the only possible expressions are parameters given to
 the current transform, boolean and integer literals, and previously decoded
-fields in the current `struct`:
+fields in the current `struct` or an outer `struct`:
 {{{
 transform item(little_endian) = struct {
@@ -273 +273 @@
    This is essential for non‐sequential blobs like filesystems.
  Complex expressions:: Expressions that use operators or call transforms.
- Accessing outer fields:: Expressions can use previously decoded fields of the
-   current `struct`, but they need a way to access the previously decoded
-   fields of an outer `struct`.
  Assertions:: These could be implemented as transforms that don't actually
    change the input. There could be multiple levels, ranging from “warning” to
@@ -301 +298 @@
    could be passed automatically, without having to write it out every time. A
    more advanced automatic parameter could keep track of current offset being
-   decoded within a blob. There would need to be some sort of scoping to
+   decoded within a blob. There would need to be some sort of grouping to
    determine which transforms have the automatic parameters.
  Smarter length calculation:: Bithenge should automatically detect the length