7 commits

Author	SHA1	Message	Date
Jason Volk	a4f55b4627	ircd::mods: Reorganize and distill interface.	2016-11-25 19:23:49 -08:00
Jason Volk	da78598d86	ircd::mapi: Rectify linkage of the header symbol name string.	2016-11-13 16:33:25 -08:00
Jason Volk	1da6aa2b93	ircd::mapi: Improve the stuck-module message by showing it immediately.	2016-09-27 02:20:42 -07:00
Jason Volk	417594d0cd	mapi: Add check for "stuck modules" and display warning for developer.	2016-09-21 16:29:30 -07:00
Jason Volk	0096a4a8c6	mapi: Reincarnate MAPI III key-value metadata, C++ style.	2016-09-21 16:29:30 -07:00
Jason Volk	68a1d161b9	mapi: Add alternate simple constructor.	2016-09-09 16:17:03 -07:00
Jason Volk	9d0a959bb5	MAPI IV. This iteration leverages the C++11 standardized RTTI. ... * Simplifies the export declarations for module developers. While MAPI III utilized a flexible key-value vector to eliminate positional arguments in a header initializer, now the developer simply makes a list of pointers to what they want to export for injection into IRCd. Example: mapi::header IRCD_MODULE { "mymod", "My module adds a command, a hook, and a CLICAP", &my_cmdtab, &some_hook, &clicaptab }; * Distributes the handlers for items passed to the above vector. Anyone can add a type-handler to the module system from anywhere in IRCd (and other modules?) When your type is encountered a handler is called providing the symbol name to read out of the module. Example in parser.cc: mods::add_loader<Message>([] (mod &loading, const std::string &symbol) { auto &msg(get<Message>(loading, symbol)); add_command(msg.name, msg); });	2016-09-09 16:17:01 -07:00