That's an unusual assertion. Perl has much better facilities for working with unicode, and many other advanced facilities for parsing and so forth.
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.
You can have unicode procedure names, if that was your fancy.
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-p...