We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct Ć but invalid C#:
public class Point { int x; int y; } public class A { public void f(Point p) { p.x = 1; } }
I propose that "internal" keyword should be allowed on fields. (and simply ignored)
public class Point { internal int x; internal int y; }
This way Visual Studio/MonoDevelop IDE can be used to write Ć.
Workaround:
public class Point { #if !CITO internal #endif int x; #if !CITO internal #endif int y; }
The text was updated successfully, but these errors were encountered:
It's not the only incompatibility with C#, so perhaps you'll need to try some more serious persuasion on @pfusik ;)
Sorry, something went wrong.
It's certainly the biggest incompatibility (80%) by number of lines of code. Other incompatibilities can be encapsulated in functions, for example:
public static byte ConvertIntToByte(int value) { #if CITO return value.LowByte; #else return (byte)value; #endif }
"internal" is already a valid keyword for functions. Why not for fields?
I know that "common subset of Ć and C#" isn't a supported language. But Visual Studio is better IDE than CiPad ;) Especially for large projects.
The change is very small, just ignore "internal" keyword.
No branches or pull requests
Correct Ć but invalid C#:
I propose that "internal" keyword should be allowed on fields. (and simply ignored)
This way Visual Studio/MonoDevelop IDE can be used to write Ć.
Workaround:
The text was updated successfully, but these errors were encountered: