Hi all, usually we have fully specified mspec documents. This way we can fully generate our model, parsers and serialisers.
Especially when it comes to protocols that we haven't fully understood yet (Like the DeltaV and the Beckhoff auto-discovery) there are sometimes big blocks of data which we simply don't know yet. If we use "const" we'll probably get loads of parse errors. If we use "reserved" we'll get tons of log output. Both don't really reflect that we don't actually know what this data is. "unknown" pays respect to this fact and documents it. I would implement this field type to simply skip the given number of bits when parsing and to throw an exception when serializing. This way we can use the mspec to produce passive-mode drivers first and as soon as we fully understood a protocol, we can create the active versions. What do you think? I did this now as I would like to have this change in the next release of the build tools and not have to do that again any time soon. Chris
