Comment #16 on issue 361 by Fix warnings

It's the convention at Google to use "int" as
loop counters, which makes it pointless to
update the code to use "size_t"

Surely the max-value that the loop counter is compared against should *also* have type "int", too, then? (as suggested in comment #14)

Signed/unsigned comparisons can cause subtle bugs and are worth avoiding, one way or another...

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups "Protocol 
Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to