[[basics:intro|Intro]]
[[basics:ex1|Ex1]]
[[basics:ex2|Ex2]]
[[basics:ex3|Ex3]]
[[basics:ex4|Ex4]]
[[basics:ex5|Ex5]]
[[basics:ex6|Ex6]]
[[basics:ex7|Ex7]]
====== The Basics: Exercise 7 ======

From the aspect ''Basics'', declare that the class ''Application'' implements the interface ''Iterable<String>''.

<note tip>
Employ the form ''declare parents: //Type// implements //Type//''.
</note>

This will raise a compiler error since ''Application'' does not provide an implementation for the ''iterator()'' method prescribed by the interface. We will also provide an implementation for this method from the aspect.

First, declare a public field ''name'' of type ''String'' for the ''Application'' class, with the default value "MyApplication".

<note tip>
The inter-type declaration of members (fields or methods) has the same syntax as the ordinary declarations of members, but the method or field name must be prefixed by name of the receiving class and a dot (''.'').
</note>

Next, add a method ''iterator()'' with return type ''Iterator<String>''. This method will return an iterator over the values of the two fields of the ''Application'' class. To construct this iterator, you can employ the following snippet inside the method body:

<code aspectj>
java.util.Arrays.asList(name, "go: " + go).iterator();
</code>

The declaration of this method should resolve the previous compiler error. To test the new code, add a new class ''ApplicationTest'' with the following implementation:

<code aspectj>
public class ApplicationTest {
  public static void main(String[] arg) {
    Application t = new Application();
    t.name = "YourApplication";
    for(String s: t)
      System.out.println(s);
  }
}
</code>

To start this new ''main'' method, right-click on the class ''ApplicationTest'' and select **Run As** -> **Java/AspectJ Application**.

<note important>
Beside the expected output, you might see output from your previous advices when you run the code from class ''ApplicationTest''. Review your previous code and try to understand why they also apply to the new behavior.
</note>

----

Continue with the [[invariant:intro|Invariants]] track.