DenGhostYY

If you implement this as in C#, then a lot of legacy Alaska code will not compile on XSharp. We planned to replace the [readonly](https://github.com/X-Sharp/XSharpPublic/issues/1490) (if there are any difficulties...

Because at the moment class fields marked with `readonly` can only be assigned inside a constructor, but not inside methods of the same class, although Alaska allows this.

This [ticket](https://github.com/X-Sharp/XSharpPublic/issues/1490) shows exactly this difference in the behavior of the keyword `readonly`

From Alaska documentation about the `readonly` > The option READONLY limits write access for an instance variable. The assignment of a value to an instance variable declared READONLY is only...

Perfect solution. Then the same solution can be applied for the keyword `readonly` #1490. Yes, this assignment `o:nNumber := 10` ends in a runtime error in alaska.

Regarding passing class fields by reference, such code works the same way on both Alaska and XSharp ``` procedure main() local o := Example():new(4) ? o:nNumber ? o:Inc() ? o:nNumber...

We have simplified the UDC for [enums](https://github.com/X-Sharp/XSharpPublic/issues/1250), so we didn't check it on earlier versions

The modifier `new` only works if I add a type declaration to the variable `o`. This option does not suit me, since the type declaration will have to be added...

The description of the method syntax doesn't mention the identifier calling convention anywhere. Can I send you a sln-project? https://www.xsharp.eu/help/command_xpp_classmembers.html https://github.com/X-Sharp/XSharpPublic/issues/1286#issuecomment-1609047415

Did I understand correctly that the commit has already been made and I can update the compiler using this link? https://www.xsharp.eu/itm-downloads/download?path=installers%252FXSharpSetupPublic2.16.0.5.zip > The calling convention was recently added in this...