On Thu, Jul 16, 2009 at 11:14 AM, Mr Moose wrote:
>
> It is found!
>
> After 4 interesting days of debugging the bastard I realized that I
> rercently had to add 3 preprocessor defines to my build system:
>
> _CRT_SECURE_NO_WARNINGS
> _SECURE_SCL=0
> _HAS_ITERATOR_DEBUGGING=0
>
> If they are missi
HOW TO SETUP THE ULTIMATE AFFILIATE PROGRAMME...HOW TO SETUP THE ULTIMATE
AFFILIATE PROGRAMME...HOW TO SETUP THE ULTIMATE AFFILIATE PROGRAMME...
http://autoresponder123.50webs.com/how-to-setup-the-ultimate-affiliate-programme.html
http://autoresponder123.50webs.com/how-to-setup-the-ultimate-affi
Here is the patch. I included parameters for both the compression
level and the compression strategy, both of them defaulting to the
same thing the gzip binary uses.
--Pete
On Wed, Jul 15, 2009 at 4:37 PM, Kenton Varda wrote:
> OK. Make sure that the parameter is optional, with the default match
When I write out messages using C++ I'm careful to clear messages and
re-use them, is there something equivalent on the java side when
reading those same messages in?
My code looks like:
CodedInputStream stream = CodedInputStream.newInstance(inputStream);
while ( !stream.isAtEnd() )
{
MyMe
I think what you want is lazy parsing, which unfortunately isn't available
yet. You could always read bytes off the stream in chunks, or write your
own CodedInputStream to skip to the end of each message every time it sees a
length.
Alek
On Fri, Jul 17, 2009 at 8:13 PM, Alex Black wrote:
>
> W
