~steering/inspircd++.git/src/modulemanager.cpp, branch v5.0.0dev3 Unnamed repository; edit this file 'description' to name the repository. https://www.cgit.space/~steering/inspircd++.git/atom/src/modulemanager.cpp?h=v5.0.0dev3 2026-03-31T20:20:16Z Merge branch 'insp4' into master. 2026-03-31T20:20:16Z Sadie Powell 2026-03-31T20:19:40Z urn:sha1:02413c35dbfb7fe54e5b2eb83cd09ad8a4abeaf1 Update copyright headers. 2026-03-31T20:16:33Z InspIRCd Robot 2026-03-31T20:16:33Z urn:sha1:c079e220f9f915d829d9f516ac03213cc923f046 Move service types to their own namespace. 2026-03-29T16:38:40Z Sadie Powell 2026-03-29T14:48:47Z urn:sha1:aed47513a5410a10ac9b477c621fbce425593c7f - ServiceProvider is now Service::Provider - DataProvider is now Service::SimpleProvider (the old name does not really make sense now we don't have SERVICE_DATA and the only difference is automatic registration. - Some members of ModuleManager have been elevated to the Service namespace in case other code wants to use them. Switch modules from reference<> to shared_ptr<> and weak_ptr<>. 2026-03-29T00:42:15Z Sadie Powell 2026-03-28T21:32:23Z urn:sha1:cbc5431d62e3fe9166f18395dce3ddf2af0906d3 Add the VF_DEPRECATED flag and warn on load about deprecation. 2026-03-09T15:03:34Z Sadie Powell 2026-03-09T15:03:34Z urn:sha1:911a364280e56c1b84de814e54ee59e5fd0f4a5e Allow contrib modules to specify their own module version. 2024-07-22T15:49:41Z Sadie Powell 2024-07-22T15:23:41Z urn:sha1:4e947b8733980f9d40f781f883b85e6f65bd953f Update copyright headers. 2024-06-07T09:37:56Z InspIRCd Robot 2024-06-07T09:37:56Z urn:sha1:ae3e2db109eecaea25032e218c39a257e736174a Rename some of the Module member variables. 2024-03-04T13:18:04Z Sadie Powell 2024-03-04T13:18:04Z urn:sha1:5f6bf286847550f386324e1e2db6c909cbd9f318 Rename the error log level to critical. 2023-08-11T11:39:49Z Sadie Powell 2023-08-11T11:39:49Z urn:sha1:f73e9e606b61324f4ac34d3f506b7cbaf87713c7 "ERROR" is apparently defined by more than just Windows. Let's pick a different name which is less likely to cause collisions. Simplify the codes that InspIRCd can exit with. 2023-07-13T13:07:26Z Sadie Powell 2023-07-13T12:31:06Z urn:sha1:b4e3e973297db456f0ba8d7fdb8bbfc9c8426ea7 The custom codes that InspIRCd exits with are not very useful and can confuse init systems like systemd which assume that certain exit codes mean certain things. INSPIRCD_BINARY_EXIT was a workaround for this in v3 but considering thatsers have to check the logs anyway so we may as well just use EXIT_SUCCESS and EXIT_FAILURE.