ExtensionRegistry extends ExtensionRegistryLite, and the generated
parseFrom()/mergeFrom() routines don't need the descriptor-based features
that are added by ExtensionRegistry. Is this causing problems for you?

On Wed, Apr 21, 2010 at 9:35 AM, skay <she...@pobox.com> wrote:

> I'm upgrading from 2.0.3 to 2.3, and the compiler now generates the
> parseFrom java code with ExtensionRegistryLite rather than
> ExtensionRegistry. Is it expected that using optimize_for on anything
> other than LITE_RUNTIME should generate that? I've compiled samples
> using all of the optimize_for options, and all resulted in parseFrom
> using the lite registry.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@googlegroups.com.
> To unsubscribe from this group, send email to
> protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/protobuf?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to 
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en.

Reply via email to