Syntax and Structure Rules
- Q723: Why does EK9 reject name$ instead of $name?
- Q724: Why does EK9 reject ?name instead of name?
- Q725: Why must methods come before operators in an EK9 class?
- Q726: Why must references use the :: qualifier?
- Q727: What module names are reserved in EK9?
- Q851: Why do references need a module qualifier with :: in EK9?
- Q852: Which module names are reserved in EK9?
- Q888: Why can EK9 programs only return Integer?
- Q889: What arguments can an EK9 program accept?
- Q893: Why does EK9 require 'defines class' and 'defines function' section headers?
- Q894: How do EK9 constructors work with parameters?
- Q907: How is EK9 structured compared to Pascal?
- Q916: How do I declare multiple parameters on a function in EK9?
- Q917: How do return values work in EK9 functions?
- Q943: Why does EK9 reject empty defines blocks?
- Q947: Which types are allowed for typed program arguments in EK9?
- Q952: Why must EK9 constructs be used in their valid context?
- Q1306: Why can't a local construct share a name with a referenced (imported) type in EK9?
- Q1307: Why does EK9 reject the same symbol listed twice in a references block?
- Q1308: Why does my references statement fail with E03030 reference does not resolve?