marat1961 / protobuf-delphi Goto Github PK

Add the ability to control code generation in different files. It is best to use the concept of a namespace to control generation.

In this case, you should not use already existing packages for this. Since the existing packages are used to describe the data model and are designed to resolve collisions when names match.

New(typ);
typ.form := ..;
typ.declaration := obj;
obj.typ := typ;

After successful parsing in our table TopScope refers to the universe, which contains built-in types.
The generation code is discouraged.
We need either to add a module to the table or not to close the module's scope.
There is one more option, we can rewrite the generation code to work with the module and the import list.

We need to slice our large test into several small parts, each of which does its own thing.

What test do we want?
Check the correct generation:

1. For all built-in types in single and multiple;
2. Nested messages;
3. Map;
4. Oneof;
5. Correct handling of forward declaration;
6. Correct processing of imports from several files (modules);
7. Correct handling of reserved fields.

Replace service declaration and rpc with embedded procedure type.

This is a predefined module describing embedded structures and types.

In my computer. I have the source code as follow:
procedure TGen.GenComment(const ? string);
var
s: string;
begin
for s in ?Split([#13#10], TStringSplitOptions.None) do
Wrln('// ' + s)
end;

To facilitate the release of memory occupied by recursive structures, start using memory regions.

What do we have after the work of the compiler?
As a result, we have already formed a consistent type system.

1. The internal structure of the module (object delations) must also be created.
2. It is necessary to add bypass routines for messages, enumerated types, settings and the like.
3. As a result of compilation it is necessary to obtain AST (Abstract Syntax Tree).

Two/three different methods are needed

1. For standard scalar data types
   We use a method binding based on TypeInfo.
2. For user defined types
   a) array or collection (type of collection, type of value)
   b) record or object (TObjMeta)
   Use a pair of generated read/write methods.

Management of the generated code.
Place in settings

1. Frame for the generated data model.
2. Frame for the generated serialization code.
3. Templates for generating fields:

• tag declaration;
• private field declaration in class;
• field declaration in the record;
• property generation;
• getter/setter;
• custom type;
• repeating field;
• standard dictionary.

When declaring class fields, check the names for equality with Delphi keywords.
If there is a match, it is possible:

1. Issue a diagnosis
2. Add prefix &
3. Add the ability to determine:

• Generated field name;
• Generated type name.