Missing hasNext() Check Before Using next() in Iterator

[Xiqinger]

Describe the bug
The current implementation utilizes an Iterator without checking the hasNext() method before calling next(). This can lead to NoSuchElementException if there are no more elements in the Iterator.
The "printEvaluation" method in the "oops.OOPSevaluation" class utilizes the "elementos.hasNext" check to ensure that "first" has a value. However, it does not guarantee that "second" will have a hasNext() value of true.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Additional context
To mitigate this issue, it is recommended to add a hasNext() check before accessing the "second" element, line 350 and line 327 .

[dgarijo]

Thanks!!