205 karma · joined June 11, 2018
Sounds like that is what happens.
So I started by adding the ability to define syllable structure in the rules file, then I tried running the syllable rule through the same compiler I used for the regular sound change rules. It ended up being even slower than I was anticipating, so I decided to skip the NFA to DFA conversion step and wrote a backtracking NFA runner. This worked _okay_, but if the syllable rule isn't able to fully match a word it ends up backtracking forever, and I never managed to figure out how to fix that.
Last year I read a post about parser combinators and I decided to rewrite the syllable detector. I finished the rewrite and then ran into an error and gave up. This last weekend I revisited it and it turned out it was just user error again; my syllable definition rule had a mistake, but thankfully the error was a lot easier to fix with the new design. Now it emits a warning, and I'm rewriting my sample sound changes rules to use the new boundary markers and hammering out any issues, which are a lot less than I was afraid of.
I'm thinking about rewriting the sound change rule compiler to use the same combinators I did for the syllable rules, but it would be kind of a shame after all the work I put into the DFA compiler lol
Well, there was also narwhal bacon and Streetlamp Le Moose.
I don't read celebrity news, how should I know People's track record?
I did something like this when I was moving my files onto a new computer like 25 years ago, and all I had was a floppy drive. Just continuously dump the data onto a floppy until space runs out and ask for another one until there are no more files.