Hi Dave, hi all, 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? I'm usually purposefully ignoring Unicode issues on this list. They make my head hurt. But in this case, it's about the clueless (like myself). I'd say such a warning may be useful. But... 1) If we add such a warning, we make certain assumptions* about what the user was trying to do and ended up wanting to use bytes.pm. 2) If we assume we have a good idea what she really wanted to do, we should add pointers to the right way to do it next to the warning. Without pointers to the right solution, such a warning wouldn't be very helpful. Best regards, Steffen * I'm being vague for lack of Unicode-fu, here.Thread Previous | Thread Next