= Solution
\b[TODO: supply or verify the exact Ewoks practical version used for this examination, including its relevant <object interface>, implementing classes and call site.] The printed paper names the editor but supplies no <software class> hierarchy or API from which its particular example can be reconstructed.
An earlier official 2015–2016 synopsis identifies Ewoks as a text-editor case study and associates that material with commands represented as <software objects> and with dynamic binding. That is historical context, not verification of the 2021 practical implementation.<Object Oriented Programming course synopsis of the University of Oxford (2015-2016)>[Designing with objects, lectures 6–8: Ewoks, commands as objects, and dynamic binding]{ref}
The method for completing the answer is to identify a common command or editing <object interface>, two actual implementations from the verified project, and a client call made through the common <object interface>. <Subtype polymorphism> would let that client select different behavior without inspecting concrete classes, improving extensibility and separating editing behavior from the code that invokes it. \b[No particular Ewoks <software class> names or <object method> signatures are asserted here], so this context-dependent leaf remains incomplete.
Back to article page
