Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Jon Skeet	72ec33676f	Tidy up reflection in advance of attempting to implement DynamicMessage. There are corner cases where MessageDescriptor.{ClrType,Parser} will return null, and these are now documented. However, normally they should be implemented, even for descriptors of for dynamic messages. Ditto FieldDescriptor.Accessor. We'll still need a fair amount of work to implement dynamic messages, but this change means that the public API will be remain intact. Additionally, this change starts making use of C# 6 features in the files that it touches. This is far from exhaustive, and later PRs will have more. Generated code changes coming in the next commit.	9 years ago
Jon Skeet	2a15051a1e	Introduce a Parser property into MessageDescriptor, and populate it from generated types. Generated code coming in next commit - in a subsequent PR I want to do a bit of renaming and redocumenting around this, in anticipation of DynamicMessage.	10 years ago
Jon Skeet	284bb452e4	Generated code changes and manual changes for previous commit.	10 years ago
Jon Skeet	6fa17e7597	Reimplement JSON recursion by detecting the depth in the tokenizer. Added a TODO around a possible change to the tokenizer API, changing PushBack(token) into just Rewind() or something similar.	10 years ago
Jon Skeet	0fb39c4afe	Created a new exception for JSON failures. This is only thrown directly by JsonTokenizer, but surfaces from JsonParser as well. I've added doc comments to hopefully make everything clear. The exception is actually thrown by the reader within JsonTokenizer, in anticipation of keeping track of the location within the document, but that change is not within this PR.	10 years ago
Jon Skeet	3d257a9dc1	Add recursion limit handling to JSON parsing. Fixes issue #932.	10 years ago
Jon Skeet	6a94273549	Move the creation of the "fields by JSON name" dictionary to the descriptor.	10 years ago
Jon Skeet	fb2488225f	Implement JSON parsing in C#. This includes all the well-known types except Any. Some aspects are likely to require further work when the details of the JSON parsing expectations are hammered out in more detail. Some of these have "ignored" tests already. Note that the choice not to use Json.NET was made for two reasons: - Going from 0 dependencies to 1 dependency is a big hit, and there's not much benefit here - Json.NET parses more leniently than we'd want; accommodating that would be nearly as much work as writing the tokenizer This only really affects the JsonTokenizer, which could be replaced by Json.NET. The JsonParser code would be about the same length with Json.NET... but I wouldn't be as confident in it.	10 years ago