Newsgroups: php.i18n,php.internals
Path: news.php.net
Xref: news.php.net php.i18n:1015 php.internals:24200
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <23ead5a35bff30e24f93045de3db6638@gravitonic.com>
Content-Transfer-Encoding: 7bit
Cc: PHP Internals <internals@lists.php.net>
Date: Fri, 23 Jun 2006 14:00:57 -0700
To: PHP I18N <php-i18n@lists.php.net>
Subject: TextIterator changes
From: andrei@gravitonic.com (Andrei Zmievski)

I am working on implementing BreakIterator API [1]. I considered two 
approaches: making a separate class or merging the API into the 
existing TextIterator. Having a separate class would be a bit cleaner, 
but I can see people wanting to use it in foreach(), and since 
TextIterator already provides a lot of BreakIterator's functionality, I 
decided that merging would be the best option. However, there is an 
overlap between the BreakIterator API and the current TextIterator one, 
so there will have to be some changes.

1. TextIterator::current() signature will change from:

    mixed current()

to:

    mixed current(integer &$offset)

in order to support BreakIterator's functionality of returning offset 
in current().

2. TextIterator::next() will return the offset of the next boundary 
instead of returning nothing.

3. TextIterator::rewind() will be renamed to TextIterator::first() to 
conform to BreakIterator's first()/last() API.

So this is heads up. Let me know if you have a problem with this.

-A

[1] http://icu.sourceforge.net/apiref/icu4c/ubrk_8h.html