You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whilst trying to write some signatures for formats that are JSON based, I realised that the bytesequence I needed to describe should be able to deal with optional layout characters. The following JSON blocks are all functionally equivalent (with layout characters shown in brackets), but can't all be described with a single bytesequence because of the optional white spaces, tabs and new lines.
Whilst trying to write some signatures for formats that are JSON based, I realised that the bytesequence I needed to describe should be able to deal with optional layout characters. The following JSON blocks are all functionally equivalent (with layout characters shown in brackets), but can't all be described with a single bytesequence because of the optional white spaces, tabs and new lines.
Ideally I should be able to specify a class of bytes and allow for wildcard matching to allow me to express the bytesequence as
BOFOffset 0: An opening {, followed by zero or more spaces, tabs, new-lines or carriage-returns, followed by "key1"....
i.e. :
The text was updated successfully, but these errors were encountered: