...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="150e695da8bf4659-4154d3f6-475f43da-af2695e1-f140d7de6d7bca2b1e927521"><ac:plain-text-body><![CDATA[ | [[API 2006 | AA. Bibliography#API 06]] | [Class Calendar | http://download.oracle.com/javase/6/docs/api/java/util/Calendar.html] | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3e9d304fff5823e3-a86de7b8-456d4ed6-a9e29464-9f6c10c95d43da6f3f633595"><ac:plain-text-body><![CDATA[ | [[Bloch 2008 | AA. Bibliography#Bloch 08]] | Item 16: "Favor composition over inheritance" | ]]></ac:plain-text-body></ac:structured-macro> | |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="35d33840e6343d62-f540d994-486945fc-9b3ea9be-ce71e856588e650b43eb8e27"><ac:plain-text-body><![CDATA[ | [[Gamma 1995 | AA. Bibliography#Gamma 95]] | Design Patterns: Elements of Reusable Object-Oriented Software | ]]></ac:plain-text-body></ac:structured-macro> | |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f9f9ab752cb9a399-b1b13ebc-47034e51-b24a9be9-7295709b9e6b62496e2a60e4"><ac:plain-text-body><![CDATA[ | [[Lieberman 1986 | AA. Bibliography#Lieberman 86]] | Using prototypical objects to implement shared behavior in object-oriented systems | ]]></ac:plain-text-body></ac:structured-macro> | |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a7fefbc2e837de34-36443fec-49cd43fc-8d19933d-5b4c17675202236c8ed5f647"><ac:plain-text-body><![CDATA[ | [[SCG 2007 | AA. Bibliography#SCG 07]] | Guideline 1-3 Understand how a superclass can affect subclass behavior | ]]></ac:plain-text-body></ac:structured-macro> |
...
OBJ12-J. Compare classes and not class names 04. Object Orientation (OBJ) OBJ04OBJ14-J. Provide mutable classes with copy functionality to allow passing instances to untrusted code safelyDo not mix generic with non-generic raw types in new code