hi,
i am work in aix 5.3, xlc++ v10.1
# make check
Making check in .
make[1]: Entering directory `/home/source/cpp/protobuf-2.2.0-build-32'
make check-local
make[2]: Entering directory `/home/source/cpp/protobuf-2.2.0-build-32'
Making lib/libgtest.a lib/libgtest_main.a in gtest
make[3]:
hi
when i #include google/protobuf/extension_set.h
the xlc++ always show an error message:
/home/soft/include/google/protobuf/extension_set.h, line 378.10:
1540-0063 (S) The text ( is unexpected.
line 377 to 379
int GetSize() const;
void Free();
int SpaceUsedExcludingSelf() const;
Hi,
On Fri, 2009-09-25 at 16:41 +0300, Daniel Augustin Pavel wrote:
I've worked a bit on improving the perfomance of equals() and
hashCode() for the generated message clases.
[snipped]
My implementation of equals() compares the two messages
field-by-field. In tests, for equal objects it
You will get paid $20.00 for every email you process online. Our
program requires only basic computer skills and can be done wherever
you have access to the Internet.
http://processemailonline.com
--~--~-~--~~~---~--~~
You received this message because you are
Aaand forgot to reply all. Apologies.
Cheers,
-pwr
-- Forwarded message --
From: Daniel Augustin Pavel daniel.pa...@gmail.com
Date: Fri, Sep 25, 2009 at 19:04
Subject: Re: Java generated code: faster equals() and hashCode()
To: Brice Figureau brice...@daysofwonder.com
On Fri,
Maybe your system headers #define Free as a macro? Try adding #undef Free
before that line.
On Fri, Sep 25, 2009 at 7:25 AM, alex as.von.ch...@gmail.com wrote:
hi
when i #include google/protobuf/extension_set.h
the xlc++ always show an error message:
Maybe 'Free' is a macro defined in that compiler environment ? (would
be bad, but these things happen).
What happens if you do an #undef Free in front of that
On Fri, Sep 25, 2009 at 07:25, alex as.von.ch...@gmail.com wrote:
hi
when i #include google/protobuf/extension_set.h
the xlc++
Jinx. :)
On Fri, Sep 25, 2009 at 10:04 AM, Henner Zeller h.zel...@acm.org wrote:
Maybe 'Free' is a macro defined in that compiler environment ? (would
be bad, but these things happen).
What happens if you do an #undef Free in front of that
On Fri, Sep 25, 2009 at 07:25, alex
I do agree that this should not be applied for LITE_RUNTIME because of the
lite runtime goal.
However an extra option could be added where these equals() and hashCode()
are implemented.
LITE_RUNTIME_EXTRA maybe. (any name is fine)
Those 2 methods are definitely needed in most cases.
Cheers
On
So is there a decision for this issue? Will it be a flag for protoc or
a patch (I think I saw somewhere a post mentioning that the patch was
not going to be used because of other issues)? And any possible ETA
for the solution?
On Aug 31, 5:33 pm, Kenton Varda ken...@google.com wrote:
I'm OK
On Fri, Sep 25, 2009 at 12:25, mo mohammad.kolahdou...@gmail.com wrote:
So is there a decision for this issue? Will it be a flag for protoc or
a patch (I think I saw somewhere a post mentioning that the patch was
not going to be used because of other issues)? And any possible ETA
for the
protobuf is very cool. There are two options which I think would be
very helpful:
1) An option to prefix a length field to each message. This would
make it possible to serialize/deserialize a stream of bytes (e.g., a
TCP socket).
2) An option for prefixing a type field to each message -- this
On Fri, Sep 25, 2009 at 1:28 PM, dound doun...@gmail.com wrote:
1) An option to prefix a length field to each message. This would
make it possible to serialize/deserialize a stream of bytes (e.g., a
TCP socket).
This is sort of out of scope of what protobuf does. It should be
handled by
regionStart() is there since JDK 1.5
http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Matcher.html#regionStart()
What is your java version ?
On Fri, Sep 25, 2009 at 15:54, matt matt.hender...@lucidsw.com.au wrote:
I have compiled C++ protobuf successfully but am having enormous
I have compiled C++ protobuf successfully but am having enormous
difficulty compiling the java code. I initially tried manually and
after two days relinquished and installed Maven as recommended in the
README. Building under Maven produced the same errors.
ie:
1. ERROR in
On Fri, Sep 25, 2009 at 15:59, Matt Henderson
matt.hender...@lucidsw.com.au wrote:
Thank you for your prompt response:
Eclipse Java Compiler 0.793_R33x, 3.3.2
I was using the -5 switch for java5 / 1.5 computability
mmh, some time ago that I used Eclipse. Maybe the bytecode
compatibility is
16 matches
Mail list logo