I've noticed that @indrora originally applied Apache to his contribution, and all our subsequent commits thus were also Apache-licensed.

There is a problem with Apache license being incompatible with GPLv2, thus this license choice can potentially impede adoption of Kaitai Struct for free/open source projects which still use GPLv2.

The majority of other runtimes are MIT-licensed, so could I persuade you all to switch to MIT?

I'm trying to get all runtimes to use uniform order of methods and sectioning. Can you enlighten me if C#'s #region / #endregion can be nested?

I.e. I'd like to use something like (indented for the sake of illustration, won't be indented in real code):

#region Integer types
  #region Signed
    #region Big-endian
    #endregion
    #region Little-endian
    #endregion
  #endregion
...
#endregion

I guess that it's valid from compiler's POV, and, so far I've checked that:

• it works flawlessly in KWrite/Kate (i.e. regions/subregions get properly folded)
• it kind of works in MonoDevelop (only top-level regions are seen in document's structure view, and MonoDevelop does not seem to support folding at all)
• Doxygen does not support nested regions properly, and thus messes up "group names" — but, anyway, probably Doxygen is not a documentation generator of choice for C#?

Could you check if that would be ok with Visual Studio editor? What about major documentation generation tools?

The method ReadBitsIntLe() uses left shift operation which may contribute to overflow. We could use Math.Pow() method for left shift to avoid the overflow

                ulong v = (ulong)(buf[i] * Math.Pow(2,BitsLeft));
                //ulong v = (ulong)(buf[i] << BitsLeft);

I can make this change and send a pull request

Hi Im currently trying to learn how to use this awesome tool and I have noticed that the version of the NuGet package available is 0.7 where version 0.8 exists.
Could you please upload the latest version?

Some parts of the code implicitly depend on the stream being seekable and tellable, like FileStream. Arbitrary streams (like pipes?) may be non-seekable and non-tellable. Either clarify in documentation that such a restrition exists, or change the code somehow.

public bool IsEof
{
    get { return BaseStream.Position >= BaseStream.Length; }
}
public long Size
{
    get { return BaseStream.Length; }
}