[PEPr] +1 for Internationalization::I18N_UnicodeString
| From: | PEPr | Date: | Mon, 16 Aug 2004 22:23:33 +0000 |
| Subject: | [PEPr] +1 for Internationalization::I18N_UnicodeString | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-32716@lists.php.net to get a copy of this message | ||
Harry Fuecks (http://pear.php.net/user/hfuecks) has voted +1 on the proposal for
Internationalization::I18N_UnicodeString.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=131
Vote information:
http://pear.php.net/pepr/pepr-vote-show.php?id=131&handle=hfuecks
Comment:
Looks good and certainly something that's badly needed.
One thing that seems a bit of a shame is including PEAR at the start: adds 1000ish lines of code to
parse on every request just in case of error (which typically should be uncommon). I guess most
users of this will expect a lightweight set of tools, comparable to the native string functions with
minimal processing overhead.
A nice way to get around this when raising errors is to conditionally include PEAR on error, rather
than at the start e.g.;
} else {
require_once 'PEAR.php';
return PEAR::raiseError('Malformed UTF-8 string');
}
When checking for errors, that's trickier but I imagine users would prefer something more
suspect like;
if(strtolower(get_class($this->_unicode))=='pear_error')
given it saves those lines of code.
--
Sent by PEPr, the automatic proposal system at http://pear.php.net