Over the past years iv’e reported a few compiler issues<\/p>\n\n\n\n
Here’s the current list of open issues I’ve reported<\/p>\n\n\n\n
55502<\/strong> adding a constant to a class cant use an expression while one in code can And there two I would love to see Xojo fix as its impossible for the usage to be ambiguous<\/p>\n\n\n\n 56375<\/strong> compiler incorrectly identifies “global” as syntax error And even if the Enum is scoped as private its , at worst, written as. <\/p>\n\n\n\n It would be simiar for Public, Private and Global. No one of those value lines can be mistaken for the scope of anything else.<\/p>\n\n\n\n 56411<\/strong> compiler misidentifies “attributes” as syntax error in spots where it cannot be ambiguous<\/p>\n\n\n\n Attributes is handled similarly to the above case for scope. And has the same impossible to be ambiguous situation.<\/p>\n\n\n\n Both of these cases are most definitely fixable but so far Xojo has declined to do so.<\/p>\n\n\n\n Out of my list iof just compiler bugs <\/p>\n","protected":false},"excerpt":{"rendered":" Over the past years iv’e reported a few compiler issues Here’s the current list of open issues I’ve reported 55502 adding a constant to a class cant use an expression while one in code can56376 compiler misidentifies syntax error on shared factory in super class 56378 factory pattern cant be implemented properly in Xojo esp … <\/p>\n
56376<\/strong> compiler misidentifies syntax error on shared factory in super class
56378<\/strong> factory pattern cant be implemented properly in Xojo esp when items are in a namespace
56765<\/strong> compiler weird error message seems to be linked to wrong order of evaluation
57500<\/strong> debugging a while loop in debugger appears to skip entire loop
58900<\/strong> compiler incorrectly identifies unused local variables
59004<\/strong> endexception constructor should probably be restricted in some fashion
59061<\/strong> compiler gives a very ambiguous error message on select case statement
61901<\/strong> compiler reports completely bogus error
61949<\/strong> xojo does not warn of conversion on assignment
63438<\/strong> compiler gets comparison confused with assignment
56264<\/strong> make it so when a method returns an array you can immediately index into the return result
56272<\/strong> optional parameters can only be “right most” parameters
60207<\/strong> command line arguments for debug run cannot use a #constant<\/p>\n\n\n\n
In something like an enumeration its impossible for the tokens for Global, Protected, Private and Public to be ambiguous.
An enumeration is written as
<\/p>\n\n\n\nEnum myenumeration\n value\n value\nEnd Enum <\/code><\/pre>\n\n\n\nPrivate Enum myenumeration\n value\n value\nEnd Enum <\/code><\/pre>\n\n\n\n
– 1 has been fixed
– 2 closed as By Design (noted above)
– 1 closed as Not Reproducible (and I have no idea how to reproduce it either)
– 11 are Reproducible
– 3 feature requests Reviewed<\/p>\n\n\n\n