•  Search
• About
  • News
• API Docs (Java 11)
• Developing
  • AST Visualizer
  • Getting Started
  • Technical Design
  • Extension library
• Testing
  • Integration Testing
  • Regression Tests
  • Compliance Issues
• Publications
• Google Group
• Source Code
  • Issue Tracker
  • Git Repo
  • Code Style
• NeoBeaver

Code Style

Using a consistent code style improves readability. The coding style used for ExtendJ is based on Google's Java Style Guide, with a few special considerations for JastAdd code:

• Synthesized and inherited attributes should not share the same name. Synthesized and inherited attributes are fundamentally different and if two different kinds of attributes share the same name then it can easily lead to unexpected behaviour.
• The refine constructs can cause lines to be very long. If a refine line is longer than 100 characters, then a line break should be inserted after the aspect name part of the refinement.
• If an attribute equation is too long to fit on the line, prefer to add a line break after the first equals sign rather than inserting a line break in the middle of the expression.