…mes of which are derived from the Java package name. Protocol buffer function, such as IS-INITIALIZED, CLEAR, etc. continue to live in the PROTOCOL-BUFFER package. StudlyCaps field, message, and enum names are converted to hyphenated names. String fields are stored as instances of %STRING-FIELD%, a hidden class. Create new string fields with PB:STRING-FIELD. Extract values from a string field using PB:STRING-VALUE or PB:UTF8-STRING-VALUE.
…ment it to handle enum defaults. Use the new DefaultValue function in enum_field.cc.
wire-format-test.lisp: Rename to wire-format_test.lisp. protobuf.asd: Reflow comments.
OS X and Linux.
PROTOBUF-CONFIG. README: Mention Lispworks support. Re-fill paragraphs.
Joel Reymont. Fix errors with single floating point literals -- use 123f0 not 123s0.
and package called com.google.base.
files. Convert varint tests to use Stefil. Document new build and test procedure in the README file.
(values returntype &optional). unittest.proto: comment not fields with NaN defaults, since SBCL can't handle NaNs in class initforms. protocol-buffer.lisp: Use symbol macros for infinities and NaNs. Maybe we'll get rid of these entirely, if no Lisp has complete support.
separate directory by default. Remove .gitmodules -- we no longer rely on having a google-protobuf submodule. Change README to reflect the new compilation procedure.
…lute file path is used for the proto file argument to protoc. The internal Google compiler wants a relative file path, but the external compiler wants an absolute path. Also, add syntax="proto2" to all proto files so the Google internal protobuf compiler is happy with them.
…we need for testing in directories google/protobuf and google/protobuf/testdata. message-test.lisp, protobuf-test.asd: new file paths for test files
package.lisp: export BASE:VECTOR-INDEX protobuf.asd: new variable for protoc-gen-lisp pathname protoc/lisp/Makefile: add installation target
…e the Lisp backend code from the google-protobuf repository to this one. The backend code is currently Linux only. We need to use autoconf/automake.
int32-to-uint32, int32-to-uint64, int64-to-uint64. Instead, just use (cl:ldb (byte 64/32 0) xxx), which returns an unsigned integer of the right width.
…that the output directory exists when converting a proto file to Lisp. Add some comments.
point construction function. Add a comment about the fact that SBCL is currently broken for NaN values and so we initialize to zero.