ortus-coding-standardslisted

# Ortus Coding Standards ## Overview Ortus Solutions maintains consistent formatting rules across all BoxLang, CFML, and Java source code. These rules are enforced via the **OrtusJava Eclipse formatter profile** (`ortus-java-style.xml`) for Java, and via the conventions documented here for BoxLang and CFML. When in doubt, match what already exists in the file you are editing. --- ## Indentation Use **tabs** for indentation — never spaces for the leading indent. - Class body: indented one tab from the class declaration. - Method body: indented one tab from the method signature. - Switch cases: indented one tab from `switch`. - Case body: indented one tab from the `case` label. - Continuation lines (wrapped expressions): indented one level. ```java // Java — tab-indented, end-of-line braces public class UserService { public User findById( int id ) { if ( id <= 0 ) { throw new IllegalArgumentException( "id must be positive" ); } return repository.find( id ); } } ``` ```js // BoxLang — same indentation rules class UserService { function findById( required numeric id ) { if ( id <= 0 ) { throw( type = "InvalidArgument", message = "id must be positive" ) } return variables.repository.find( arguments.id ) } } ``` --- ## Spacing Inside Parentheses **Always** place a space after `(` and before `)` in: - Method declarations - Method invocations - Control flow keywords (`if`, `for`, `