[nergal]

I'm not sure how complicated this process would be but how would I be able to automatically index subplugins for a core plugin and give them a SerialID to easily track them?

As well as Strings for plugin information?

[friagram]

Use the library system?

[rswallen]

@friagram, I believe the intent is to do it without the use of the library system

@nergal, Its complicated but doable

In the core plugin, you need a native that sub-plugins must call to register and receive an ID (and another to de-register in the event that the sub-plugin unloads). When the registration native is called, store the plugin handle of the sub-plugin with the new ID (suggest ADT array for this) and return the ID:

Spoiler

PHP Code:

new g_lastID;
new Handle:g_registeredPlugins;  // CreateArray(2);

public NativeCall_Register(Handle:plugin, numParams)
{
    // first do some checking that the plugin is not already registered (ie try to find plugin handle in the array)
    
    if (bNewPlugin)
    {
        new index = PushArrayCell(g_registeredPlugins, plugin);
        SetArrayCell(g_registeredPlugins, index, ++g_lastID, 1);
        return g_lastID;
    }
    return -1;
} 


You will also need to set a max limit for the value of g_lastID, and return it to 0 when it is reached. When registering new plugins, you should also check that an ID is not already in use (loop through the array)

When the de-registration native is called, look for the plugin handle in the array, and remove it:

Spoiler

PHP Code:

public NativeCall_Deregister(Handle:plugin, numParams)
{
    new index = FindInArray(g_registeredPlugins, plugin);
    if (index != -1)
    {
        RemoveFromArray(g_registeredPlugins, index);
        return 1;
    }
    return 0;
} 


If at any time you want to check if sub-plugin is loaded (or if a sub-plugin was unloaded and did not de-register), create something like this:

Spoiler

Core plugin:

PHP Code:

new Handle:g_fwdPluginPingTest;

public OnPluginStart()
{
    g_fwdPluginPingTest = CreateGlobalForward("AreYouStillThere", ET_Event, Param_Cell);
}

bool:IsPluginActive(Handle:plugin)
{
    new bool:result = false;
    Call_StartForward(g_fwdPluginPingTest);
    Call_PushCell(plugin);
    Call_Finish(result);
    
    return result;
} 


Sub-plugin (add to include):

PHP Code:

public bool:AreYouStillThere(Handle:plugin)
{
    return (plugin == GetMyHandle());
} 


WORD OF WARNING:
This system relies on all participating plugins being honest (ie returning the correct value in the forward). If a plugin contains a modified forward (such that it always returns true), bad things will happen :s

[nergal]

Originally Posted by friagram Use the library system?

ok that actually made me lol but I'm asking this as a serious question as I don't know how and I'm stumped on making it....

[nergal]

Originally Posted by rswallen @friagram, I believe the intent is to do it without the use of the library system @nergal, Its complicated but doable In the core plugin, you need a native that sub-plugins must call to register and receive an ID (and another to de-register in the event that the sub-plugin unloads). When the registration native is called, store the plugin handle of the sub-plugin with the new ID (suggest ADT array for this) and return the ID: Spoiler PHP Code: new g_lastID; new Handle:g_registeredPlugins;  // CreateArray(2); public NativeCall_Register(Handle:plugin, numParams) {     // first do some checking that the plugin is not already registered (ie try to find plugin handle in the array)          if (bNewPlugin)     {         new index = PushArrayCell(g_registeredPlugins, plugin);         SetArrayCell(g_registeredPlugins, index, ++g_lastID, 1);         return g_lastID;     }     return -1; }  You will also need to set a max limit for the value of g_lastID, and return it to 0 when it is reached. When registering new plugins, you should also check that an ID is not already in use (loop through the array) When the de-registration native is called, look for the plugin handle in the array, and remove it: Spoiler PHP Code: public NativeCall_Deregister(Handle:plugin, numParams) {     new index = FindInArray(g_registeredPlugins, plugin);     if (index != -1)     {         RemoveFromArray(g_registeredPlugins, index);         return 1;     }     return 0; }  If at any time you want to check if sub-plugin is loaded (or if a sub-plugin was unloaded and did not de-register), create something like this: Spoiler Core plugin: PHP Code: new Handle:g_fwdPluginPingTest; public OnPluginStart() {     g_fwdPluginPingTest = CreateGlobalForward("AreYouStillThere", ET_Event, Param_Cell); } bool:IsPluginActive(Handle:plugin) {     new bool:result = false;     Call_StartForward(g_fwdPluginPingTest);     Call_PushCell(plugin);     Call_Finish(result);          return result; }  Sub-plugin (add to include): PHP Code: public bool:AreYouStillThere(Handle:plugin) {     return (plugin == GetMyHandle()); }  WORD OF WARNING: This system relies on all participating plugins being honest (ie returning the correct value in the forward). If a plugin contains a modified forward (such that it always returns true), bad things will happen :s

Thx RSWallen!

I've heard from Bailopan that the natives and forwards system will be removed in the future when the API and Syntax goes into higher phase than now.
What are your thoughts on that? Just curious.

[rswallen]

Originally Posted by nergal Thx RSWallen! I've heard from Bailopan that the natives and forwards system will be removed in the future when the API and Syntax goes into higher phase than now. What are your thoughts on that? Just curious.

I'm happy with natives/forwards as they are. I can only hope that if/when they are retired, the system that replaces them is just as good.

[nergal]

Originally Posted by rswallen I'm happy with natives/forwards as they are. I can only hope that if/when they are retired, the system that replaces them is just as good.

If I remember correctly, Bail said the natives and forwards stuff was added because of Pawns faulty memory and how inter-plugin communication was corrupting plugin memory? Something like that.