Front page | perl.perl5.porters |
Postings from February 2010
On Wed, Feb 24, 2010 at 12:32:50PM -0500, Jesse Vincent wrote: > > > > On Mon 22.Feb'10 at 16:47:36 +0000, Dave Mitchell wrote: > > On Sun, Jan 03, 2010 at 11:27:22PM +0000, Dave Mitchell wrote: > > > I think these days there's a general consensus that, for normal day-to-day > > > tasks, the user has no need for bytes.pm, and indeed, that most naive use > > > of it is likely to be harmful. > > > > > > Given that, should we add a warning to bytes.pm's pod to the effect that > > > you shouldn't be using this for new code unless you really know what you're > > > doing, and that a desire to do so probably indicates a design flaw in your > > > code or your understanding of perl's Unicode implementation? > > > > Following the discussion, I've committed the following: > > Based on your explanation, "deprecate" feels like a very strong > statement. It's more of a "This library does unspeakable things to Perl's > understanding of strings. It's unlikely that you want to use it. Instead > have a look at ..." > > Or do we actually have a better way to do _everything_ bytes does? The earlier discussion in the thread seemed to reach a rough consensus that any use (apart from debugging etc) of bytes.pm was a mistake, even bytes::length. -- A walk of a thousand miles begins with a single step... then continues for another 1,999,999 or so.Thread Previous | Thread Next