- Apr 02, 2013
-
-
Scott McKay authored
-
- Apr 01, 2013
-
-
Scott McKay authored
-
- Mar 20, 2013
-
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
- Mar 16, 2013
-
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
Fixes the bug tickled by the tests in this commit's parent.
-
Steven Spitz authored
These tests tickle an error serializing emtpy messages as fields of other messages when using speed-optimized serializers.
-
- Mar 08, 2013
-
-
Alejandro R Sedeño authored
-
- Mar 07, 2013
-
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
This ensures that all pathnames for all .proto files we load get put in PROTO-IMPL::*ALL-SCHEMAS*, not just those we import.
-
Alejandro R Sedeño authored
Don't override file extension for imports; assume the string that was used to form the pathname is accurate. This makes base-path and proto-file the same, so fold them both into proto-file. Drop bogus checks for type "proto".
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
- Mar 06, 2013
-
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
* FIND-SCHEMA no longer works on a string or keyword. Both of these were based on the PATHNAME-NAME of the protobuf, which has a high probability of collision. (e.g., common.proto -> "COMMON", :COMMON) Instead, look up schemas based on package and name. For instance, the protobuf foo.proto, declaring "package FooPackage;", can be found with: (FIND-SCHEMA 'FOO-PACKAGE::FOO) * Pathname-based schema lookup no longer ignores file type.
-
Alejandro R Sedeño authored
* DO-PROCESS-IMPORT is now responsible for deciding whether or not to process an import. It does so by searching for the .proto to be imported, and upon finding it, checks to see if we alredy have a schema for that pathname. Additionally, it now returns the pathname. * PROCESS-IMPORTS and PROCESS-IMPORTS-FROM-FILE now defer the work of figuring out whether or not an import has been done to DO-PROCESS-IMPORT. PROCESS-IMPORTS uses the return value of DO-PROCESS-IMPORT to update the PROTO-IMPORTED-SCHEMAS of the schema being processed.
-
Alejandro R Sedeño authored
New functions: * ASDF::PROTOBUF-MANGLE-NAME: Takes a pathname, returns a string to be used as a filename that represents the original path. e.g., #P"/foo/bar/baz.quux" becomes "foo-bar-baz-quux" * ASDF::PROTOBUF-LISPIZE-PATHNAME: Takes a pathname, returns a new pathname with the name mangled as described above, and with a lisp type.
-
Alejandro R Sedeño authored
-
- Mar 03, 2013
-
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
So far only CCL appears to consistently handle this.
-
Alejandro R Sedeño authored
-
Scott McKay authored
- Use 'defparameter' instead of 'defvar' where appropriate. - Fix 'defvar' doc strings to distinguish between globals and "thread locals". - Avoid using 'nconc'. introduce a new 'appendf' macro instead. - Add a comment lamenting the fact that exporting something like 'proto-options' also exports the writer '(setf proto-options)'. Fixed in Dylan.
-
- Mar 01, 2013
-
-
Scott McKay authored
-
Scott McKay authored
-
- Feb 28, 2013
-
-
Scott McKay authored
-
Scott McKay authored
-
Scott McKay authored
-
Alejandro R Sedeño authored
This prevents geodata.proto's FASL from being clobbered by geodata.lisp's FASL. Before both were geodata.fasl, now the former is geodata.proto.fasl. This is generally a good idea.
-
Alejandro R Sedeño authored
-
- Feb 27, 2013
-
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-
Alejandro R Sedeño authored
-