The wrap method on generated flyweights is failing to validate maxValue is sufficient

[cmebarrow]

It is therefore in some cases reading memory beyond maxLimit. The wrap method on the Flyweight class itself should verify that maxLimit is greater than offset. Generated wrap method should validate that maxLimit - offset is at least large enough to accommodate all required and default values.

Taking the DataFW as an example, as generated from the following IDL:

        struct Frame
        {
            int64 streamId;
        }
       
        struct AuthorizedFrame extends core::stream::Frame
        {
            int64 authorization = 0;
        }

        struct Data extends core::stream::AuthorizedFrame [0x00000002]
        {
            uint8 flags = 1;            // 0x01 FIN
            int64 groupId;
            int32 padding;
            int32 length;
            octets[length] payload = null;
            octets extension;
        }

calling DataFW.wrap(buffer, offset, maxLimit) should throw an exception if maxLimit - offset is not at least 8 + 8 + 1 + 8 + 4 + 4 = 33. Currently it will just attempt to interpret bytes going beyond maxLimit!