* Nicholas Clark <nick@ccl4.org> [2009-02-19 15:20]: > If we're going to deprecate something, we need to stop using it > in the core. Which would mean that we need an alternative in > the core. > > Which would mean a bikeshed argument about what next. I think there’s fairly good consensus in favour of either File::Next or File::Find::Object. Note that it’s easy to cast a callback API as a wrapper around an iterator API, but without continuations, it’s not possible to do the opposite. It should be possible to merge File::Find’s test suite into the prospective newcomer’s and then leave behind a thin wrapper that implements the File::Find API which can then stay around forever, if we so wish. (This argument hangs off the fact that a filesystem walking module is needed by the Perl code in the core. Otherwise I’d just say to deprecate File::Find.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>Thread Previous | Thread Next