You could always extend the compiler, but I bet you could get away with a simple preprocessor that aliases types and represents those larger integers as raw bytes.
--Chris On Jun 30, 2011, at 7:30 AM, Eric Hopper <omnifari...@gmail.com> wrote: > I'm building an application around protocol buffers. The types in my > application can be mapped to types that protocol buffers supports, so > I can sort of on-the-fly translate. For example, I have a timestamp > field that can be translated to a 64 bit unsigned integer. But it > would be really nice to do this within protocol buffers. > > Additionally, there are some types that protocol buffers supports > internally, but has no language types for. For example, I would like > the ability to work with integers that were larger than 2^64-1. > > Is there a way to use options and hook the compiler to generate your > own types for fields? Is there a way to hook the validation code so > you can make types for integers larger than 2^64-1? > > Thanks, > -- > Eric Hopper > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to protobuf@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. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@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.