You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By developing a module I expect it to be independent from other modules, or their order. I expect it should not be a problem if different modules call IARM_Bus_Init directly with different name in arbitrary order. The specification of IARM_Bus_Init looks like it should not be a problem either. Nevertheless the code of helpers/UtilsIarm.h expects that IARM is only used with name "Thunder_Plugins" and fails otherwise. I think this logic is a bug. If IARM is once inited and connected with different name all plugins that use helpers/UtilsIarm.h stop working. The problem would not exist if all modules implemented their own meaningful logic that accounts for simple situations like this, instead of relying on helpers/UtilsIarm.h. For example, this would work:
IARM_Bus_Init(__FUNCTION__);
IARM_Bus_Connect();
The text was updated successfully, but these errors were encountered:
By developing a module I expect it to be independent from other modules, or their order. I expect it should not be a problem if different modules call
IARM_Bus_Init
directly with different name in arbitrary order. The specification ofIARM_Bus_Init
looks like it should not be a problem either. Nevertheless the code of helpers/UtilsIarm.h expects that IARM is only used with name "Thunder_Plugins" and fails otherwise. I think this logic is a bug. If IARM is once inited and connected with different name all plugins that use helpers/UtilsIarm.h stop working. The problem would not exist if all modules implemented their own meaningful logic that accounts for simple situations like this, instead of relying on helpers/UtilsIarm.h. For example, this would work:The text was updated successfully, but these errors were encountered: