Front page | perl.perl5.porters |
Postings from September 2000
Re: unicode support and perl
From: Simon Cozens
September 16, 2000 04:28
Re: unicode support and perl
Message ID: 20000916122806.B25843@deep-dark-truthful-mirror.perlhacker.org
OK, I need to do some apologising here too.
Marc, for starters, I'm sorry if I accused you of whining. I *know* you're
not just a whiner - you've sent in patches, Spider's had a look at one, Nick's
put it in the repository, and it'll go into 5.7.1, cleaning up one of those
bugs. That's making progress; if I ever accused you of not helping, then I'm
demonstrably wrong here. You're one of the few people who is very obviously
doing good and right things to help out Unicode support.
And I need to apologise to P5P, because I've let this go around and around in
circles when I should have taken it off-list at least. Sorry for the noise.
I've basically come to realise that most of the communication gap here comes
down to problems in the way I work, or rather that the way I work isn't to
everyone's liking and I'm being pretty inflexible about it.
To explain, the way I like to fix problems in Perl is to be presented with a
piece of code which someone claims doesn't work, and change Perl until it does
what people think it should. That's why I ask for test code, and why I get a
bit uppity when people, quite reasonably, refer me back to the bug db. Yes,
it's laziness; I like to be confronted directly with the problem, in my face,
rather than having to go out of my way to find it.
But let's be honest, this is a volunteer effort, and we work on Perl the way
we feel comfortable with. If I have to start digging around in the
perlbugtron, things stop being fun for me because I'm not working the way I
want to. But that doesn't mean I'm allowed to be inflexible about it, and
especially if it's stopping progress being made, so I do need to apologise for
What next? Well, Nick's committed a patch which fixes one of those bugs, but
there are others remaining. If someone wants to be a white knight, I'd really
appreciate it if they could take the time to either dig up the bug db or look
at Marc's issues, or even act as a go-between here and talk to Marc about
what's left (unless it's completely apparent to everyone but me, which is
quite likely...) because I've not been communicating too well, distil it into
some test code and send it to me. (Not the scary $1 thing that Hugo's looking
at, though. There are limits. :)
Yes, call me lazy if you like, but I'd honestly appreciate just another pair
of eyeballs on this from *someone* because I'm too disorganised and busy to
spend all the research time on this. Put a problem in front of me, in terms of
a piece of broken code, and I'll see what I can do with it.
Thanks, all, and sorry again,
Asynchronous inputs are at the root of our race problems.
-- D. Winker and F. Prosser