protobuf - Protocol Buffers – Google’s data interchange format

	Commit message (Collapse)	Author	Age
*	Integrated internal changes from Google	Adam Cozzette	2018-03-13
\|
*	Addming missing includes in stubs headers.	Jisi Liu	2015-07-17
\| \| \| \| \| \|	This is to prepare removing those additional headers in common.h Change-Id: I707d6d8eaf193eb28195a827c7fec738b968ab3e
*	Replace links to code.google.com/protobuf with ↵	Feng Xiao	2014-10-01
\| \| \| \|	developers.google.com/protocol-buffers
*	down integrate to svn	jieluo@google.com	2014-07-18
\|
*	add missing dll export macros for msvc.	liujisi@google.com	2013-01-11
\|
*	Improve GoogleOnceInit() in Protocol Buffers.	pliard@google.com	2012-04-10
\| \| \| \| \| \| \| \| \| \|	It is based on V8's new CallOnce(): http://codereview.chromium.org/9447052/. This patch includes the following changes: - POD (no static initializer generated) and faster implementation on Windows. - GoogleOnceInit() can now take an additional parameter which is forwarded to the function provided by the user. This patch is part of the static initializers removal initiative.
*	Ensure that 'once' objects are declared using the macro. This is either the ↵	temporal	2009-12-18
\| \| \| \|	third or fourth time I've screwed this up when down-integrating, because our internal code does not require the macro (it's not portable) and on Linux a pthread_once_t that is zero-initialized just happens to work. So, I only discover the problem when I test on Mac, then kick myself for making the same mistake yet again. No more! This time, I have renamed GoogleOnceType to ProtobufOnceType, thus making the type name differ from our internal code. As a result, if you don't update the decls to use the macros, they won't compile. Hah! Take that, future self!
*	Fix final leak (win32 only).	kenton@google.com	2009-05-18
\|
*	Make building libprotobuf as a DLL work again.	kenton@google.com	2009-04-28
\|
*	Integrate recent changes from Google-internal code tree. See CHANGES.txt	kenton@google.com	2009-04-25
	for details.