Invalid Tagger args are silently ignored

[polm]

If you do something like fugashi.Tagger("d /asdf") (no hyphen), the invalid arguments will be ignored and you'll get a working tagger. That's weird and unhelpful. It seems to be the way the MeCab API works, but the actual MeCab command line behaves reasonably (gives an error), so there should be a way to modify the behavior.

[lambdadog]

Confused why this is the case, studying the codepath in mecab.

mecab_new creates its tagger using createTagger, which then calls TaggerImpl::open, which calls ModelImpl::open which then calls Param::open and load_dictionary_resource just like mecab_do (the entry-point for the executable) all with (as far as I can tell) the exact same arguments.

A param parse failure should go up the chain and cause mecab_new to return 0 instead of the tagger, as far as I can tell reading the code, but that's clearly not the case.

[polm]

For reference, while the code paths do look the same, this isn't the first inconsistency like this to come up - by default errors in the Tagger don't give output when called via the API because the error message is cleared somewhere, and there's a ridiculous workaround involving the Model class to make that work at the moment.

Another note since several issues have come up: my good arm is in a cast right now, and while I have use of my fingers I have less bandwidth than usual.

[aehlke]

fyi also, if the path has whitespace in it, mecab will not accept it

[polm]

@aehlke That isn't the same issue, and you can get around it with quoting, see here.