Open Yzrsah opened 5 years ago
Thanks for you observation. A I can see you did not notice that main interface of this library are macro replacements on the top. That feature makes my API implementation resistant to underlying changes.
In https://github.com/cplusplus/reflection-ts I see good things and also bad thing. For example 21.12.2 is OK. Other thighs I do not sees as useful.
If I can easily use reflection to perform (de)serialization and binding then this library is good. Otherwise just another bad job.
I do not work this for money or glory I just experiment for my self. And if someone see this useful it is welcome to use.
Thanks for your comment. If you have some questions or more suggestion do not hesitate to contact me.
Regards Dejan
On Mon, Dec 31, 2018 at 11:01 AM Zyrsha notifications@github.com wrote:
Do not make new reflection libraries. There is already a virtual graveyard of 50 of them for C++.
But if your library is an emulator for the Reflection TS, then it is OK.
How to do a bad job:
- Make another new C++ reflection library. (the project is obsolete before you even started)
How to do a good job:
- Follow along with the latest Reflection TS and try to make a library which emulates it. https://github.com/cplusplus/reflection-ts
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dmilos/reflection/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/APIjvHatEbI20QjsO6aIgxX-94W0YV6Lks5u-eBvgaJpZM4ZlUvS .
Do not make new reflection libraries. There is already a virtual graveyard of 50 of them for C++.
But if your library is an emulator for the Reflection TS, then it is OK.
How to do a bad job:
How to do a good job: