[Vergil333]

Wow, thanks for explaining that to me, WildCard65. I wouldn't find this anywhere else.

But what about getAnInt() function? It returns an int form first plugin without any natives, forwards or anything?

[WildCard65]

Your example code doesn't register getAnInt as a native, so the SP compiler expects a normal method, your example code does expose a native_getAnInt but it'll never be called.

[Vergil333]

I just copied the code from EasSidezz... But you are right, I don't know how I couldn't see it before...

If I correct the example this way, will it work? :

first plugin:

PHP Code:

new anInt;

//We call this because OnPluginLoad() is apparently called too late. I  mean just look at the name of this, it honestly looks like it belongs in  here.
public APLRes:AskPluginLoad2(Handle:myself, bool:late, String:error[], err_max)
{
    CreateNative("setAnInt", native_setAnInt);
    CreateNative("getAnInt", native_getAnInt);

    RegPluginLibrary("uselessnatives.inc");
    return APLRes_Success;
}


public native_getAnInt(Handle:plugin, numParams)
{
    return anInt;
}


public native_setAnInt(Handle:plugin, numParams)
{
    //setAnInt(value);
    new set = GetNativeCell(2); //First param, the value we'll be setting int to.

    anInt = set;
    return;
} 


include file:

PHP Code:

#if defined _uselessnatives_included
 #endinput
#endif
#define _uselessnatives_included

native native_setAnInt(int, value);
native native_getAnInt(int, value); 


second plugin:

PHP Code:

#include <uselessnatives>

public OnPluginStart()
{
    RegConsoleCmd("sm_nativeprint", command_printNatives, "Print what you set");
}

public Action:command_printNatives(client, args)
{
    setAnInt(50);

    getAnInt();

    return Plugin_Handled;
} 


[DJ Tsunami]

You should name your natives so they they won't conflict with other plugins. For example:

PHP Code:

    CreateNative("uselessnatives_setAnInt", native_setAnInt);
    CreateNative("uselessnatives_getAnInt", native_getAnInt); 


Then you need to use the same names in your include file. Also, setAnInt only uses one parameter, and getAnInt does not use any.

PHP Code:

native uselessnatives_setAnInt(value);
native uselessnatives_getAnInt(); 


Then of course use GetNativeCell(1) inside native_setAnInt.


Edit: Also, to actually print the int:

PHP Code:

public Action:command_printNatives(client, args)
{
    uselessnatives_setAnInt(50);

    ReplyToCommand(client, "Int: %i", uselessnatives_getAnInt());

    return Plugin_Handled;
} 


[Phil25]

uselessnatives = use-less-natives

You can pass a third parameter which will tell your plugin whether to return an already set value or set it to the new one.

This can be also achieved by having a certain value of the "value" parameter to do it. For example, if you can't have the int less than 0, you can pass -1 which would you could make it return the value instead of setting it, a non-negative value does the latter.

Don't forget that you could set default values of parameters in the .inc file.

Just my two cents...

[Vergil333]

Whohohooo, it works like a charm! Thanks DJ Tsunami for your correction. Now everything makes sense to me

[Powerlord]

When naming natives, I've found it best to have the plugin name at the start.

So, if my plugin name is GreatestPluginEver, it'd be Greatest_DoGreatThing

[sdz]

Originally Posted by Powerlord When naming natives, I've found it best to have the plugin name at the start. So, if my plugin name is GreatestPluginEver, it'd be Greatest_DoGreatThing

That's how I go about it.
I figure that if people feel comfortable about implementing natives into their plugins, they have enough sense to go read documentation but of course I can see I'm proven wrong time and time again.

[zeroibis]

Also lets not forget the view_as<int>() function to help avoid a tag mismatch toss if your trying to return something other than int and your prototype is a float or bool for example.