Permalink
Browse files

More files from the original svn repo

  • Loading branch information...
1 parent b4fdf7a commit 71c31044928df4578e8d5bdc3479bb0b09016d6c @gaelen gaelen committed Apr 5, 2012
Showing with 31,164 additions and 0 deletions.
  1. +237 −0 INSTALL.txt
  2. +5 −0 editors/README.txt
  3. +105 −0 editors/proto.vim
  4. +220 −0 editors/protobuf-mode.el
  5. +95 −0 examples/AddPerson.java
  6. +50 −0 examples/ListPeople.java
  7. +58 −0 examples/Makefile
  8. +29 −0 examples/README.txt
  9. +95 −0 examples/add_person.cc
  10. +58 −0 examples/add_person.py
  11. +30 −0 examples/addressbook.proto
  12. +68 −0 examples/list_people.cc
  13. +38 −0 examples/list_people.py
  14. +96 −0 java/README.txt
  15. +186 −0 java/pom.xml
  16. +764 −0 java/src/main/java/com/google/protobuf/AbstractMessage.java
  17. +325 −0 java/src/main/java/com/google/protobuf/AbstractMessageLite.java
  18. +51 −0 java/src/main/java/com/google/protobuf/BlockingRpcChannel.java
  19. +64 −0 java/src/main/java/com/google/protobuf/BlockingService.java
  20. +403 −0 java/src/main/java/com/google/protobuf/ByteString.java
  21. +885 −0 java/src/main/java/com/google/protobuf/CodedInputStream.java
  22. +1,081 −0 java/src/main/java/com/google/protobuf/CodedOutputStream.java
  23. +1,887 −0 java/src/main/java/com/google/protobuf/Descriptors.java
  24. +438 −0 java/src/main/java/com/google/protobuf/DynamicMessage.java
  25. +266 −0 java/src/main/java/com/google/protobuf/ExtensionRegistry.java
  26. +169 −0 java/src/main/java/com/google/protobuf/ExtensionRegistryLite.java
  27. +788 −0 java/src/main/java/com/google/protobuf/FieldSet.java
  28. +1,834 −0 java/src/main/java/com/google/protobuf/GeneratedMessage.java
  29. +731 −0 java/src/main/java/com/google/protobuf/GeneratedMessageLite.java
  30. +206 −0 java/src/main/java/com/google/protobuf/Internal.java
  31. +93 −0 java/src/main/java/com/google/protobuf/InvalidProtocolBufferException.java
  32. +155 −0 java/src/main/java/com/google/protobuf/LazyStringArrayList.java
  33. +72 −0 java/src/main/java/com/google/protobuf/LazyStringList.java
  34. +215 −0 java/src/main/java/com/google/protobuf/Message.java
  35. +325 −0 java/src/main/java/com/google/protobuf/MessageLite.java
  36. +58 −0 java/src/main/java/com/google/protobuf/MessageLiteOrBuilder.java
  37. +110 −0 java/src/main/java/com/google/protobuf/MessageOrBuilder.java
  38. +58 −0 java/src/main/java/com/google/protobuf/ProtocolMessageEnum.java
  39. +696 −0 java/src/main/java/com/google/protobuf/RepeatedFieldBuilder.java
  40. +47 −0 java/src/main/java/com/google/protobuf/RpcCallback.java
  41. +71 −0 java/src/main/java/com/google/protobuf/RpcChannel.java
  42. +118 −0 java/src/main/java/com/google/protobuf/RpcController.java
  43. +135 −0 java/src/main/java/com/google/protobuf/RpcUtil.java
  44. +117 −0 java/src/main/java/com/google/protobuf/Service.java
  45. +52 −0 java/src/main/java/com/google/protobuf/ServiceException.java
  46. +241 −0 java/src/main/java/com/google/protobuf/SingleFieldBuilder.java
  47. +618 −0 java/src/main/java/com/google/protobuf/SmallSortedMap.java
  48. +1,476 −0 java/src/main/java/com/google/protobuf/TextFormat.java
  49. +99 −0 java/src/main/java/com/google/protobuf/UninitializedMessageException.java
  50. +953 −0 java/src/main/java/com/google/protobuf/UnknownFieldSet.java
  51. +146 −0 java/src/main/java/com/google/protobuf/UnmodifiableLazyStringList.java
  52. +163 −0 java/src/main/java/com/google/protobuf/WireFormat.java
  53. +460 −0 java/src/test/java/com/google/protobuf/AbstractMessageTest.java
  54. +528 −0 java/src/test/java/com/google/protobuf/CodedInputStreamTest.java
  55. +318 −0 java/src/test/java/com/google/protobuf/CodedOutputStreamTest.java
  56. +80 −0 java/src/test/java/com/google/protobuf/DeprecatedFieldTest.java
  57. +460 −0 java/src/test/java/com/google/protobuf/DescriptorsTest.java
  58. +226 −0 java/src/test/java/com/google/protobuf/DynamicMessageTest.java
  59. +48 −0 java/src/test/java/com/google/protobuf/ForceFieldBuildersPreRun.java
  60. +980 −0 java/src/test/java/com/google/protobuf/GeneratedMessageTest.java
  61. +118 −0 java/src/test/java/com/google/protobuf/LazyStringArrayListTest.java
  62. +115 −0 java/src/test/java/com/google/protobuf/LazyStringEndToEndTest.java
  63. +148 −0 java/src/test/java/com/google/protobuf/LiteTest.java
  64. +313 −0 java/src/test/java/com/google/protobuf/MessageTest.java
  65. +185 −0 java/src/test/java/com/google/protobuf/NestedBuildersTest.java
  66. +190 −0 java/src/test/java/com/google/protobuf/RepeatedFieldBuilderTest.java
  67. +320 −0 java/src/test/java/com/google/protobuf/ServiceTest.java
  68. +155 −0 java/src/test/java/com/google/protobuf/SingleFieldBuilderTest.java
  69. +420 −0 java/src/test/java/com/google/protobuf/SmallSortedMapTest.java
  70. +49 −0 java/src/test/java/com/google/protobuf/TestBadIdentifiers.java
  71. +3,811 −0 java/src/test/java/com/google/protobuf/TestUtil.java
  72. +752 −0 java/src/test/java/com/google/protobuf/TextFormatTest.java
  73. +437 −0 java/src/test/java/com/google/protobuf/UnknownFieldSetTest.java
  74. +152 −0 java/src/test/java/com/google/protobuf/UnmodifiableLazyStringListTest.java
  75. +427 −0 java/src/test/java/com/google/protobuf/WireFormatTest.java
  76. +71 −0 java/src/test/java/com/google/protobuf/multiple_files_test.proto
  77. +53 −0 java/src/test/java/com/google/protobuf/nested_builders_test.proto
  78. +45 −0 java/src/test/java/com/google/protobuf/nested_extension.proto
  79. +48 −0 java/src/test/java/com/google/protobuf/nested_extension_lite.proto
  80. +48 −0 java/src/test/java/com/google/protobuf/non_nested_extension.proto
  81. +50 −0 java/src/test/java/com/google/protobuf/non_nested_extension_lite.proto
  82. +90 −0 java/src/test/java/com/google/protobuf/test_bad_identifiers.proto
  83. +41 −0 more_tests/Makefile
  84. +29 −0 vsprojects/config.h
  85. +20 −0 vsprojects/convert2008to2005.sh
  86. +46 −0 vsprojects/extract_includes.bat
  87. +286 −0 vsprojects/libprotobuf-lite.vcproj
  88. +446 −0 vsprojects/libprotobuf.vcproj
  89. +414 −0 vsprojects/libprotoc.vcproj
  90. +273 −0 vsprojects/lite-test.vcproj
  91. +92 −0 vsprojects/protobuf.sln
  92. +192 −0 vsprojects/protoc.vcproj
  93. +114 −0 vsprojects/readme.txt
  94. +209 −0 vsprojects/test_plugin.vcproj
  95. +625 −0 vsprojects/tests.vcproj
View
@@ -0,0 +1,237 @@
+This file contains detailed but generic information on building and
+installing the C++ part of this project. For shorter instructions,
+as well as instructions for compiling and installing the Java or
+Python parts, see README.
+
+======================================================================
+
+Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
+Foundation, Inc.
+
+ This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+
+Basic Installation
+==================
+
+ These are generic installation instructions.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system. If you're
+ using `csh' on an old version of System V, you might need to type
+ `sh ./configure' instead to prevent `csh' from trying to execute
+ `configure' itself.
+
+ Running `configure' takes awhile. While running, it prints some
+ messages telling which features it is checking for.
+
+ 2. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+Compilers and Options
+=====================
+
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+ If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+ By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+ Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+ There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on. Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+ If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+ Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+`configure' Invocation
+======================
+
+ `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+ Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+
+`--srcdir=DIR'
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
View
@@ -0,0 +1,5 @@
+This directory contains syntax highlighting and configuration files for editors
+to properly display Protocol Buffer files.
+
+See each file's header comment for directions on how to use it with the
+appropriate editor.
View
@@ -0,0 +1,105 @@
+" Protocol Buffers - Google's data interchange format
+" Copyright 2008 Google Inc. All rights reserved.
+" http://code.google.com/p/protobuf/
+"
+" 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.
+
+" This is the Vim syntax file for Google Protocol Buffers.
+"
+" Usage:
+"
+" 1. cp proto.vim ~/.vim/syntax/
+" 2. Add the following to ~/.vimrc:
+"
+" augroup filetype
+" au! BufRead,BufNewFile *.proto setfiletype proto
+" augroup end
+"
+" Or just create a new file called ~/.vim/ftdetect/proto.vim with the
+" previous lines on it.
+
+if version < 600
+ syntax clear
+elseif exists("b:current_syntax")
+ finish
+endif
+
+syn case match
+
+syn keyword pbTodo contained TODO FIXME XXX
+syn cluster pbCommentGrp contains=pbTodo
+
+syn keyword pbSyntax syntax import option
+syn keyword pbStructure package message group
+syn keyword pbRepeat optional required repeated
+syn keyword pbDefault default
+syn keyword pbExtend extend extensions to max
+syn keyword pbRPC service rpc returns
+
+syn keyword pbType int32 int64 uint32 uint64 sint32 sint64
+syn keyword pbType fixed32 fixed64 sfixed32 sfixed64
+syn keyword pbType float double bool string bytes
+syn keyword pbTypedef enum
+syn keyword pbBool true false
+
+syn match pbInt /-\?\<\d\+\>/
+syn match pbInt /\<0[xX]\x+\>/
+syn match pbFloat /\<-\?\d*\(\.\d*\)\?/
+syn region pbComment start="\/\*" end="\*\/" contains=@pbCommentGrp
+syn region pbComment start="//" skip="\\$" end="$" keepend contains=@pbCommentGrp
+syn region pbString start=/"/ skip=/\\"/ end=/"/
+syn region pbString start=/'/ skip=/\\'/ end=/'/
+
+if version >= 508 || !exists("did_proto_syn_inits")
+ if version < 508
+ let did_proto_syn_inits = 1
+ command -nargs=+ HiLink hi link <args>
+ else
+ command -nargs=+ HiLink hi def link <args>
+ endif
+
+ HiLink pbTodo Todo
+
+ HiLink pbSyntax Include
+ HiLink pbStructure Structure
+ HiLink pbRepeat Repeat
+ HiLink pbDefault Keyword
+ HiLink pbExtend Keyword
+ HiLink pbRPC Keyword
+ HiLink pbType Type
+ HiLink pbTypedef Typedef
+ HiLink pbBool Boolean
+
+ HiLink pbInt Number
+ HiLink pbFloat Float
+ HiLink pbComment Comment
+ HiLink pbString String
+
+ delcommand HiLink
+endif
+
+let b:current_syntax = "proto"
Oops, something went wrong. Retry.

0 comments on commit 71c3104

Please sign in to comment.