On 4 December 2010 17:43, Tom Christiansen <tchr...@perl.com> wrote: >> I think we would both agree that that is way to much. And I >> automatically assume code with "use utf8" in it is subtly >> broken until proved otherwise anyway. :-) > > Oh drat! That's distressing. I some time ago reached the conclusion > that C<use encoding> was evil, but if you are now telling me that > use utf8 is just as bad, I don't know *what* I'm going to do!
I dont know that I would say that. On the other hand I think sticking to ASCII, or other approaches might make life simpler. > One potential problem area that I can imagine is the same one you get with > XML's inline charset declaration: it has to a proper superset of ASCII, > and no non-ASCII characters may occur before the charset declaration. > > Is it that you're worried people will think they will get all their strings > magically _utf8_on()d that way -- when in fact, they don't and the same > rules are followed as without the pragma? > > Or do you fear it's old code that thought that was the only way to get > Unicode semantics, which is almost certainly wrong in many other ways, too? > > Or are you worried about non-shortest-form UTF-8 illegalities > sneaking in unchecked? > > I have a feeling that there must be something more than those, because > they're all obvious and I figure you wouldn't have mentioned it if there > weren't something more perilous and more insidious. > > And *that* has got me nervous. Its them all together. Ive seen too much code that used utf8 improperly to trust it. >> In fact I suspect over a pint we would probably mostly agree >> about what is too much. :-) > > Prolly. Colorado is the state with the most microbreweries per > capita. I don't much care for the beer in Europe apart from what > you get in the British Isles and in Belgium (maybe Benelux). > The rest of it is too easily forgotten, though now and then some > beers from Germany pleasantly surprise me; just not the rule. I generally drink Guiness. :-) [...] > The Java monoglots are completely appalled. One "helpfully" gave me almost > five pages of supernasty Java code just to get around what I did in a few > lines with cpp and token-catenation to effectively pass function pointers. > > I politely declined. > > Fortunately the only success metric at work is getting the job done, not > purity of soul. I *always* beat the Java people in time-to-solution, even > when I use Java, but that's because per their viewpoint, I "cheat". Yeah. I understand. I have had similar experiences with mixing cpp and sql code. > Whatever. (Wonder whether Rob Pike's hiring for Go? :() > > So it may not be a good weekend. I'll try to take some time away > from the computer. That should help. Indeed. Time in the big room always helps. cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
