Libraries: JSON

[Automated-Trading]

JSON:

Serialization and deserialization of the JSON format

Author: Kuzma Shevelev

[Kuzma Shevelev]

Automated-Trading:

JSON:

Author: Kuzma Shevelev

Can you tell me why the library is displayed only among Russians?
. I think that so it is unlikely to be noticed and can be used, although I think it would be very convenient for generating data for network queries.

[Edgar Akhmadeev]

I haven't looked at your implementation because I use jAson. Are there any advantages to your implementation? Can you give a comparison?

[Kuzma Shevelev]

Edgar Akhmadeev #:
I haven't looked at your implementation because I use jAson. Are there any advantages to your implementation? Can you give a comparison?

1. Size, 20kb vs 30kb

2. Allows to work flexibly with any JSON structure
- There are methods for defining value types, which allows to handle cases when value can be of different types
- There are methods for getting object keys, which allows to handle cases when keys are not known in advance
- User-friendly library interface, makes it convenient and understandable to fill JSON structure.

3. Clear and human-readable source code
- Allows you to easily understand the work of the library, making the principle of its work transparent
- Clear structure of the library will allow you to conveniently debug network requests and responses
- Does not use operator overloading, providing methods with clear names, making the code understandable to any developer.

[Stanislav Korotky]

Kuzma Shevelev #:

Can you tell me why the library is displayed only among Russians?
I think that it is so unlikely that anyone will notice and use it, although I think it would be very convenient for generating data for network queries.

Because codebase is made that way (at least for now) - by default the code is guaranteed to be registered only in one language version (you could also do it in the English branch), and transfer to other languages - only under some conditions (it should be specified - automatically by popularity, by moderators' command or somehow else).

As for the json theme itself, there is also for example a minimalistic implementation of toyjson.mqh from algobook.

[Maxim Kuznetsov]

Kuzma Shevelev #:

1. Size, 20kb vs. 30kb

2. Allows to work flexibly with any JSON structure
- There are methods for defining value types, which allows to handle cases when value can be of different types
- There are methods for getting object keys, which allows to handle cases when keys are not known in advance
- Convenient library interface, makes it convenient and understandable to fill JSON structure.

3. Clear and human-readable source code
- Allows you to easily understand the work of the library, making the principle of its work transparent
- Clear structure of the library will allow you to conveniently debug network requests and responses
- Does not use operator overloading, providing methods with clear names, making the code understandable to any developer.

here I even decided to see what " Comprehensible and human-readable source code" :-)

cross out point 3 - you, like the author of jAson, didn't even bother to write comments and documentation. And with operators it is more convenient and clear to the user, so avoiding them is more of a disadvantage than an advantage.

[Kuzma Shevelev]

Stanislav Korotky #:

Because codebase is made that way (at least for now) - by default the code is guaranteed to be registered only in one language version (you could also do it in the English branch), and porting to other languages - only under some conditions (it should be specified - automatically by popularity, by moderators' command or somehow else).

As for the json theme itself, there is also for example a minimalistic implementation of toyjson.mqh from algobook.

I looked, there really is, I think even a very good version

But in any case, I think that this library will find its audience, which will like the interface I have implemented to use it.

[Aleksandr Slavskii]

Kuzma Shevelev #:

Can you tell me why the library is displayed only among Russians?
I think that it is so unlikely that anyone will notice and use it, although I think it would be very convenient for generating data for network queries.

To make your code visible to English-speaking audience, you should post it on an English forum.

Go to the English forum.

Go to their codobase.

Add the code.

Now, the code from one forum segment is not copied automatically to another segment, you have to do it yourself.