4 ms·
That's an unusual assertion. Perl has much better facilities for working with unicode, and many other advanced facilities for parsing and so forth.
by a8da6b0c91d 11y ago
That's an unusual assertion. Perl has much better facilities for working with unicode, and many other advanced facilities for parsing and so forth.
- bch 11y ago> Perl has much better facilities for working with unicode Which facilities are those ? > many other advanced facilities for parsing Be curious to hear what those are, but note that Tcl is hilariously simple to extend and build up custom constructs to suit ones needs.
- eviltwinskippy 11y agoNot to mention that Tcl has Unicode in the core, has had Unicode in the core for at least 8 years, and the long and short is that EVERY string operation is Unicode aware. You can have unicode procedure names, if that was your fancy.
- bch 11y ago...right, which is why I was wondering where Perl's support is superior. Tcl's support isn't perfect nor complete, but it's still pretty impressive.
- wrenky 11y agoI would like to see what advanced facilities perl has for text parsing that TCL doesn't!
- kbenson 11y agoMe too, but I suspect it might take someone of tchrist's level with experience in both languages to give a good answer. I would be interested in how TCL handles the issues tchirst has to deal with outlined in his famous SO post[1]. Note: If you read that post and think, "Wow, Perl requires a lot of setup for unicode and TCP doesn't require nearly as much" without understanding the specifics of why each step is there, and how TCL handles the same issue, you are likely underthinking the issue. 1: http://stackoverflow.com/questions/6162484/why-does-modern-perl-avoid-utf-8-by-default http://stackoverflow.com/questions/6162484/why-does-modern-p...