1. Is there documentation for these codes? Is there a specification document? Is there a requirements document? If there is a specification document, rewrite it according to the specification document. The core algorithm can refer to C#. If there is unsupported syntax, use alternative syntax to implement it (goto is nothing more than used to implement loops, recursions, judgments, etc.) If there is no specification document, it will be fine if there is a requirement document. Rewrite the specifications according to the requirements document, and then write the program. You can also refer to the C# code.
2. There is no documentation. Understand the code, then write specification documents, and then develop JAVA.
If I have time to write a regex, I can modify 100 gotos...
More than a hundred lines of goto...
I have been writing C# for several years...I have never used goto...(sad)
Whoever wrote the goto can change it.
The easiest way is to rewrite it manually
C# to Java Converter
I can’t work with people who write gotos.
Let alone goto, it is wrong to write more than a hundred lines for a function.
1. Is there documentation for these codes? Is there a specification document? Is there a requirements document?
If there is a specification document, rewrite it according to the specification document. The core algorithm can refer to C#. If there is unsupported syntax, use alternative syntax to implement it (goto is nothing more than used to implement loops, recursions, judgments, etc.)
If there is no specification document, it will be fine if there is a requirement document. Rewrite the specifications according to the requirements document, and then write the program. You can also refer to the C# code.
2. There is no documentation.
Understand the code, then write specification documents, and then develop JAVA.
It is best to make changes after understanding the code business.
Uncouple and reconstruct.