...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="742200134eff6bd2-6a3b7196-49d14d7c-9b1789df-869954473efd902d3f4d6e12"><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="7d8c4c262c56a511-88076a82-408f4052-889791d8-ac8f1c63a1a6d6f8dc3302fd"><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="ac89df15e68c472c-db0c1ecf-423d4f96-b2d4855e-14cec5131f053752bb005b90"><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="183a1369a697c92c-14c2bce0-4d17439f-b05aa307-5aab761722f3213d8d83c4fa"><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="86ad9944dd38244a-a59f38e9-4c0144ca-95a694aa-5d2a46a82376933bd2750c56"><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> |
...
OBJ06OBJ12-J. Compare classes and not class names 04. Object Orientation (OBJ) OBJ04-J. Provide mutable classes with copy functionality to allow passing instances to untrusted code safely