17:46 <nickrw> before I embark on a project, please save my sanity - is it going to be relatively simple to redefine matches at runtime? Context: I'm putting i18n into my bot, and I'd like to be able to change the matchers against the selected language

17:51 <dominikh> nickrw: it's easy to *create* and *remove* matchers at runtime. I'll have to check if changing them is possible. but in all cases you'd be dealing with the low-level objects, on-handlers, not really matchers

17:52 <dominikh> well, instances of Handler specificall

17:52 <nickrw> depends how easy it is to locate the appropriate Handler I suppose

17:52 <dominikh> and no, you cannot change handlers at runtime

17:53 <dominikh> only add and remove

17:53 <dominikh> nickrw: I'm curious why you want to change them, instead of just using the right ones at startup

17:54 <nickrw> because I have a command which changes the language on demand

17:54 <dominikh> you'd be facing a lot of pain in that case

17:54 <nickrw> it just changes the locale it passes to the I18n.translate command

17:54 <dominikh> also, is that local to channels or global to the bot?

17:55 <nickrw> the bot is only designed to sit in one channel at the moment

17:55 <dominikh> you could find the correct instances of Matcher in the plugin classes, change them, unload the plugin and reload the plugin

17:55 <dominikh> but actually knowing which matchers to change is again cumbersome

17:57 <waxjar> you could construct a plugin class on the fly maybe, mix in a generic module with all the methods, mix in a module that holds the actual calls to match (in the right language)

18:00 <waxjar> nvm, stupid idea, that wouldn't help with the output at all

18:00 <nickrw> output?

18:01 <waxjar> the messages you send, i assume you'd want them in the right language as well

18:01 <nickrw> ah, I've already done that part

18:02 <nickrw> that's the easy bit :P

18:05 <nickrw> hm

18:15 <nickrw> ah, it can be quite easy to identify which Handlers to unregister if I register them all with a group

18:18 <dominikh> hm, I suppose

19:15 <nickrw> I've got it half working by doing self.class.match(blah) ; __register_matchers

19:15 <nickrw> but unregistering is problematic because I don't think I can write to @matchers

19:16 <nickrw> so if I switch languages the new command is registered, but then the old one gets registered again

19:19 <dominikh> why don't you modify the existing matchers

20:21 <nickrw> you said I'd have to unload/load the plugin after that, and I don't want to cancel timers

20:22 <nickrw> also identifying the matchers seems a difficult, unless I'm missing something

20:50 <dominikh> ah

20:50 <dominikh> well, all ways of "solving" this will be rather painful…