Kostiantyn Shchepanovskyi

I think it comes from [protobuf](https://github.com/google/protobuf/blob/76195058e25d19fc918996d55d3ad69ee55cb77e/src/google/protobuf/io/coded_stream.cc#L206): ``` cpp void CodedInputStream::PrintTotalBytesLimitError() { GOOGLE_LOG(ERROR)

We can increase it to 2Gb, as it is already done in [Google Protobuf 3.2.0](https://github.com/google/protobuf/releases/tag/v3.2.0).

Please check https://github.com/protostuff/protostuff-compiler project, there this problem is solved.

Hm, I did not know about this `enums_by_name` side-effect. It should be possible to reimplement "enums by name" in different way, similar to `io.protostuff.JsonOutput#numeric`.

Fix for this issue requires too much changes. It will not be a part of 1.3.0 release.

We can not fix this without breaking backward compatibility (need to add new methods to `Schema` interface). Moved to milestone "2.0".

> Introduced UnsafeByteStrings to support zero-copy ByteString creation. https://github.com/google/protobuf/releases/tag/v3.0.0-beta-2

You are right, something like this should work: ``` java interfact InstantiatorFactory { RuntimeEnv.Instantiator create(Class typeClass); } public static RuntimeSchema createFrom(Class typeClass, InstantiatorFactory inst); ```

As a workaround, if there are problems with default constructor - this might help: https://github.com/protostuff/protostuff/issues/132#issuecomment-130423561 Proper solution with customizable instantiator can be added, PRs are welcome.

Sorry for late reply. It's definitely valid to have proto file with unspecified package. I'll check this case.