On Fri, Feb 22, 2019 at 11:29:49AM +0200, Lauri Tirkkonen wrote: > On Thu, Feb 21 2019 20:22:16 -0700, Andrew Hewus Fresh wrote: > > > I'm only including the diff because it took quite a long time to run the > > > script (177m08.01s real). > > > > There are a lot of unicode symbols. Someday if I get super bored I'll > > write something to do it in parallel :-) > > True, there's a lot of them, but it does also seem to be spending quite > a bit of time per symbol. In FreeBSD and also my hobby OS Unleashed, > data is taken from Unicode's CLDR, which I think *might* be faster (it's > been a long time since I did anything with that), but on the other hand > there are so many reasons to dislike that approach.
It may be faster to run, but figuring out where the data I needed is in which file was definitely not faster. Although all this Unicode stuff is super interesting and I would like to understand all that, it's quite a way down my TODO list. > I quite like the simplicity of your script - it doesn't really matter > much if it takes a long time to run since you don't need to run it > very often. Especially since the result is used directly and not something that is part of the system build process that happens on every machine. I will mention that perl 5.29 already has Unicode 11 included, and so it will be a part of perl 5.30 when it is released and hopefully I won't get too far behind on that. Perl5's versioning scheme is that odd releases are for development and even releases are stable, so 5.9, 5.11, and 5.29 are all development releases while 5.28 and 5.30 will be maintenance releases. https://metacpan.org/pod/distribution/perl/Porting/pumpkin.pod#How-are-Perl-Releases-Numbered? l8rZ, -- andrew - http://afresh1.com Real programmers don't document. If it was hard to write, it should be hard to understand.
