|
Page: DCL00-J. Prevent class initialization cycles
|
Jon O'Donnell |
Aug 06, 2021
|
|
Page: DCL01-J. Do not reuse public identifiers from the Java Standard Library
|
Carol J. Lallier |
Jun 16, 2015
|
|
Page: DCL02-J. Do not modify the collection's elements during an enhanced for statement
|
Michal Rozenau |
May 18, 2021
|
|
Page: DCL50-J. Use visually distinct identifiers
|
Svyatoslav Razmyslov |
Jun 25, 2021
|
|
Page: DCL51-J. Do not shadow or obscure identifiers in subscopes
|
Michal Rozenau |
Jan 10, 2023
|
|
Page: DCL52-J. Do not declare more than one variable per declaration
|
Michal Rozenau |
Jan 10, 2023
|
|
Page: DCL53-J. Minimize the scope of variables
|
Will Snavely |
Nov 16, 2017
|
|
Page: DCL54-J. Use meaningful symbolic constants to represent literal values in program logic
|
Will Snavely |
Nov 16, 2017
|
|
Page: DCL55-J. Properly encode relationships in constant definitions
|
Will Snavely |
Nov 16, 2017
|
|
Page: DCL56-J. Do not attach significance to the ordinal associated with an enum
|
Will Snavely |
Nov 16, 2017
|
|
Page: DCL57-J. Avoid ambiguous overloading of variable arity methods
|
Michal Rozenau |
Jan 10, 2023
|
|
Page: DCL58-J. Enable compile-time type checking of variable arity parameter types
|
Will Snavely |
Nov 16, 2017
|
|
Page: DCL59-J. Do not apply public final to constants whose value might change in later releases
|
Will Snavely |
Nov 16, 2017
|
|
Page: DCL60-J. Avoid cyclic dependencies between packages
|
Michal Rozenau |
Jan 10, 2023
|
|
Page: DCL61-J. Do not use raw types
|
Will Snavely |
Nov 16, 2017
|
|
Page: Defensive Programming: Introduction
|
Carol J. Lallier |
Oct 26, 2014
|
|
Page: Denial of Service
|
Robert Seacord (Manager) |
May 01, 2015
|
|
Page: Deprecations
|
Sandy Shrum |
Oct 10, 2016
|
