An iterator has a current position and advances only when traversal is requested.
What Is InternalIterator::next in PHP?
Advances the iterator, possibly moving it past its last element.
InternalIterator::next() : voidThis operation does not accept method arguments.
Return type: void. Calling next() moves the cursor; reading current() afterwards accesses the following entry.
Example 1: Understanding the Basic Behavior
<?php
$source = new SplFixedArray(3);
$source[0] = 10;
$source[1] = 20;
$source[2] = 30;
$iterator = $source->getIterator();
$iterator->rewind();
$iterator->next();
$iterator->next();
var_dump($iterator->current());Output:
int(30)Explanation: Advances the iterator, possibly moving it past its last element.
Example 2: Testing Another Case
<?php
$source = new SplFixedArray(3);
$source[0] = 15;
$source[1] = 25;
$source[2] = 35;
$iterator = $source->getIterator();
$iterator->rewind();
$iterator->next();
$iterator->next();
var_dump($iterator->current());Output:
int(35)Explanation: Calling next() moves the cursor; reading current() afterwards accesses the following entry.
Practical Example: Applying the Operation
<?php
$source = new SplFixedArray(3);
$source[0] = 40;
$source[1] = 50;
$source[2] = 60;
$iterator = $source->getIterator();
$iterator->rewind();
$iterator->next();
$iterator->next();
var_dump($iterator->current());Output:
int(60)Explanation: Most iterator methods depend on cursor position, and behavior after exhaustion depends on the underlying iterator.
Important Behavior and Edge Cases
- Calling next() moves the cursor; reading current() afterwards accesses the following entry.
- Most iterator methods depend on cursor position, and behavior after exhaustion depends on the underlying iterator.
Comparison With Related Approaches
| Approach | When to Use It |
|---|---|
InternalIterator::next | Advances the iterator, possibly moving it past its last element. |
Iterator interface | ArrayIterator wraps an array; iterator decorators can modify traversal without copying the source values. |
Common Beginner Mistakes
| Mistake | Correct Approach |
|---|---|
| Advancing the cursor and then expecting the previous element to remain current. | Calling next() moves the cursor; reading current() afterwards accesses the following entry. |
| Choosing Iterator interface without checking whether it provides the same result. | ArrayIterator wraps an array; iterator decorators can modify traversal without copying the source values. |
Key Takeaways
- Advances the iterator, possibly moving it past its last element.
- Calling next() moves the cursor; reading current() afterwards accesses the following entry.
- Most iterator methods depend on cursor position, and behavior after exhaustion depends on the underlying iterator.
The examples demonstrate where InternalIterator::next fits within traversable collections. Verify the relevant preconditions whenever you adapt the code to real data.