Yes; *at the moment* I don't make that search path very accessible. When I
have the lid up I'll look at that, but for now if you really need to handle
a complex include path, there is an ugly workaround... and not via the IDE
tools (only at the command line).
Marc
On 13 December 2010 22:18, Thad
Updates:
Status: Fixed
Labels: FixedIn-2.4.0
Comment #5 on issue 196 by ken...@google.com: Python: Ascii output is not
assured to be in utf-8
http://code.google.com/p/protobuf/issues/detail?id=196
Cool, it sounds like it is indeed fixed.
--
You received this message because y
Indeed, this was a bug that we fixed.
On Wed, Dec 8, 2010 at 7:04 AM, jim horng wrote:
> Hi Kenton,
>
> here are the stacktrace, i found i'm using 2.1.0
>
> java.lang.NullPointerException
>
> at
> com.google.protobuf.UnknownFieldSet$Builder.mergeFieldFrom(UnknownFieldSet.java:422)
>
>
Updates:
Status: Accepted
Labels: -Type-Defect Type-Enhancement
Comment #4 on issue 247 by ken...@google.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
We do already have the ability to output to a jar file. I suppose dum
Comment #8 on issue 248 by ken...@google.com: protobuf will not compile
without thread library
http://code.google.com/p/protobuf/issues/detail?id=248
To be clear, the warning printed by configure (for v2.3.0 and earlier) is
bogus. It's a side effect of a deeper bug in the m4 file that we'r
