67 lines
3.2 KiB
C
67 lines
3.2 KiB
C
|
// Protocol Buffers - Google's data interchange format
|
||
|
|
// Copyright 2008 Google Inc. All rights reserved.
|
||
|
|
// https://developers.google.com/protocol-buffers/
|
||
|
|
//
|
||
|
|
// Redistribution and use in source and binary forms, with or without
|
||
|
|
// modification, are permitted provided that the following conditions are
|
||
|
|
// met:
|
||
|
|
//
|
||
|
|
// * Redistributions of source code must retain the above copyright
|
||
|
|
// notice, this list of conditions and the following disclaimer.
|
||
|
|
// * Redistributions in binary form must reproduce the above
|
||
|
|
// copyright notice, this list of conditions and the following disclaimer
|
||
|
|
// in the documentation and/or other materials provided with the
|
||
|
|
// distribution.
|
||
|
|
// * Neither the name of Google Inc. nor the names of its
|
||
|
|
// contributors may be used to endorse or promote products derived from
|
||
|
|
// this software without specific prior written permission.
|
||
|
|
//
|
||
|
|
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
||
|
|
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
||
|
|
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
||
|
|
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
||
|
|
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
||
|
|
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
||
|
|
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
||
|
|
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
||
|
|
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
||
|
|
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
||
|
|
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||
|
|
|
||
|
|
// Author: kenton@google.com (Kenton Varda)
|
||
|
|
// Based on original Protocol Buffers design by
|
||
|
|
// Sanjay Ghemawat, Jeff Dean, and others.
|
||
|
|
//
|
||
|
|
// This file exists solely to document the google::protobuf namespace.
|
||
|
|
// It is not compiled into anything, but it may be read by an automated
|
||
|
|
// documentation generator.
|
||
|
|
|
||
|
|
// Core components of the Protocol Buffers runtime library.
|
||
|
|
//
|
||
|
|
// The files in this package represent the core of the Protocol Buffer
|
||
|
|
// system. All of them are part of the libprotobuf library.
|
||
|
|
//
|
||
|
|
// A note on thread-safety:
|
||
|
|
//
|
||
|
|
// Thread-safety in the Protocol Buffer library follows a simple rule:
|
||
|
|
// unless explicitly noted otherwise, it is always safe to use an object
|
||
|
|
// from multiple threads simultaneously as long as the object is declared
|
||
|
|
// const in all threads (or, it is only used in ways that would be allowed
|
||
|
|
// if it were declared const). However, if an object is accessed in one
|
||
|
|
// thread in a way that would not be allowed if it were const, then it is
|
||
|
|
// not safe to access that object in any other thread simultaneously.
|
||
|
|
//
|
||
|
|
// Put simply, read-only access to an object can happen in multiple threads
|
||
|
|
// simultaneously, but write access can only happen in a single thread at
|
||
|
|
// a time.
|
||
|
|
//
|
||
|
|
// The implementation does contain some "const" methods which actually modify
|
||
|
|
// the object behind the scenes -- e.g., to cache results -- but in these cases
|
||
|
|
// mutex locking is used to make the access thread-safe.
|
||
|
|
namespace google {
|
||
|
|
namespace protobuf {
|
||
|
|
// TODO(gerbens) remove this comment, we need it to prevent clang-format
|
||
|
|
// from combining the brackets. Which would mess with extract script
|
||
|
|
} // namespace protobuf
|
||
|
|
} // namespace google
|