Moore, Paul (lists.bootstrap): >Usually, portability. Assuming you mean glib which is part of the Gnome >project, isn't that Unix-only? We have to consider Perl on Mac, Windows, >VMS, OS/390, ... Nope, glib is extremely portable. Look at it again! >Agreed. But again, is libunicode available and supported on all platforms >where Perl is? If not, are they receptive to portability patches for new >platforms? I'm sure they will be. OK, I'll come clean. I'm doing some behind-the-scenes politicking to ensure that they will be. >And on a more people-oriented note, will those people who like to >hack Perl unicode stuff, enjoy hacking on libunicode? That's me, so yes. :) >As long as their development communities agree. Not everyone's goals match >those of Perl. Will the glib maintainers want patches to provide VMS/Mac/... >support? One of Glib's aims is portability. They're trying to extend to as many platforms as possible because they want GNOME to extend to as many platforms as possible. Our support helps them in other ways as well. Portability goals are pretty common. Remember all that I8/U8/I16/U16/I32/U32 stuff? They've already done that. Maybe we've got more platforms covered than they have, but then we can help them. Of course, this would mean that Perl would have a GNU-style ./configure && make build cycle. I only throw that in to make some more people go "Ooooh!" >PR is a slippery subject. "Those Perl guys are working with the FSF fanatics >these days, time to go to Python". Or "Those Perl guys are working with the >Gnome group. Goodbye, Windows compatibility". Or "Those Perl guys are >working with Microsoft. The world has ended" (remember the ActiveState >conspiracy theo ries?) This is true. But people will make up untruths about Perl no matter what we do. Let's make sure we're doing the right thing, no matter what anyone else may say. The PR is the job of our spokesperson, right? -- Do not underestimate the value of print statements for debugging.