> Yes, that's a BC break. Instead of changing it, there could be a new > function. But as it can be simply built in userland, I don't see much > reason to have it in core.
Whether or not it's in core, the two-pronged approach is what Python does (range and xrange). Sometimes you want an array and not a generator. That language is really sympathetic to generator use, but it never forces you to use them. The core libraries are structured thoughtfully in that regard. Thanks, Adam
