Name should be YRcs or YRsharp

Xkein / PatcherYRpp

C# style YRpp for DynamicPatcher's Extensions.

GNU General Public License v3.0

12 stars 6 forks source link

Name should be YRcs or YRsharp #5

Open Metadorius opened 2 years ago

Metadorius commented 2 years ago

...because pp means ++ from C++, and it's not what we have here 😛

Xkein commented 2 years ago

I know lol, respecting the great repository YRpp first.

YRSharp should be better name but the code smell too like c/cpp and is weird in C# (performance considerated).

If one day we can describe YR's class in more natural pattern, i would like to rename this repository.

There are my several idea:

Writing code in more convenient any natural style then execute the source generator to make a post process (like the JobSystem in unity and Header Tool in Unreal)
Customize the .Net runtime to meet our demand -- fast (gc and interop suppressed), convenient (writing without the miserable struct key word that make us feel like using C), maintainable
Developing a tool like CsWin32 can help us convert the YRpp to YR# automatically

qyl27 commented 6 months ago

Maybe we can use Roslyn plugin to make these ideas now?

Xkein commented 6 months ago

Maybe we can use Roslyn plugin to make these ideas now?

Not that way. Roslyn is for C# but we need something from C++ to C#. It is a tool for parsing C++ AST, exporting meta and generating code. Trouble comes when we try converting something like:

function using assembly - jmp, call, push, mov, ...
external headers - windows sdk, C++ STL, ...
template classes feature that is not well supported by C# generic
and so on

That is, we can not automate all things, meaning much heavy labor inside...

qyl27 commented 6 months ago

Sorry for suggesting this without thorough consideration.
I think perhaps we could encapsulate certain details (such as injection or assembly) with an additional layer.
Also, regarding the conversion of C++ header file definitions to C#, I've heard of some automated tools for that, but I haven't looked into it carefully yet.
If needed, I am willing to help with this part of the work.

Xkein commented 6 months ago

Sorry for suggesting this without thorough consideration. I think perhaps we could encapsulate certain details (such as injection or assembly) with an additional layer. Also, regarding the conversion of C++ header file definitions to C#, I've heard of some automated tools for that, but I haven't looked into it carefully yet. If needed, I am willing to help with this part of the work.

Very happy to hear that. I am wrting a similar project but it is not aim to generate C# code. It use CppAst and Scriban. I have no plan for "YR#" yet. You can start by yourself. Also I will happy to contact you when i start that plan.

qyl27 commented 6 months ago

Sorry for suggesting this without thorough consideration. I think perhaps we could encapsulate certain details (such as injection or assembly) with an additional layer. Also, regarding the conversion of C++ header file definitions to C#, I've heard of some automated tools for that, but I haven't looked into it carefully yet. If needed, I am willing to help with this part of the work.

Very happy to hear that. I am wrting a similar project but it is not aim to generate C# code. It use CppAst and Scriban. I have no plan for "YR#" yet. You can start by yourself. Also I will happy to contact you when i start that plan.

Ah, thanks a lot.