Fix commandline interface file under heapcheck.

The internal down-integrate script probably does not handle the
top level macros well. Moved the macro inside of the namespace
declrations to avoid down-integrate errors in the future.

Change-Id: I3790357f36b0204a2a26577805192a3a1e989df8

Define GOOGLE_ATTRIBUTE_NOINLINE for MSVC. Workaround for VS2015 Release build compiler bug

Fix bugs on windows

Update cmake and BUILD files.

Change-Id: I17e16fdae6e4d2fb74d178fa5564a609ed58af1d

Change-Id: I74a73d3135ec1e0e4d52d741a77456b8e55f038f

Change-Id: I83a93fdb119a643fbc884e6ec3624493f6270370

(cherry-picking an intenral change).

Manually merge pull request: https://github.com/google/protobuf/pull/674
that fixes the gcc C++11 build.

Change where we rename Descriptor.cs to DescriptorProtoFile.cs.

We now do this in protoc instead of the generation simpler.

Benefits:
- Generation script is simpler
- Detection is simpler as we now only need to care about one filename
- The embedded descriptor knows itself as "google/protobuf/descriptor.proto" avoiding dependency issues

This PR also makes the "invalid dependency" exception clearer in terms of expected and actual dependencies.

Remove Python 2.5 cruft

Add tox, Python 2.6 compatibility, and many Python 3 compatibility fixes

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>

Change-Id: If3fb07754a734bae610d95124528e073515ac525

Change-Id: Ieb7a2c2fbf35bc2a8fa65b915a5ecb68c83863e4

See issue #240 - MSVC in VS2015 seems to inline a function it shouldn't. My original workaround was to disable inlining for the whole file, but I found a way to do it on just this specific function using __declspec(noinline).
Unfortunately __declspec has to go at the start of the function declaration, while __attribute in GCC can go either before or after. I had to move lots of GOOGLE_ATTRIBUTE_NOLINE to make it compile. I have not yet tested this change with GCC.

Will there be other side effects of defining this, given it wasn't previously?

I also noticed a few functions marked with both the 'inline' keyword, and GOOGLE_ATTRIBUTE_NOINLINE - huh? Is there an explanation for this, or is it an oversight?

Ruby: Conform to C89/C90 variable declaration rules.

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>

Change-Id: I6cf77f01370204ad4bc7b345a040a9a3de1706a0

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>

Signed-off-by: Dan O'Reilly <oreilldf@gmail.com>