[PurposeLessx]

Hey friends, I see lots of plugins. Authors use "#include <xs>"
but I searched, there have just some stocks in xs include. Not natives or anything.

Is it optimized to use include xs instead of using stock in plugin?
Which type is the most optimized?

Spoiler

PHP Code:

#include <amxmodx>
#include <fakemeta>
//#include <xs>

public plugin_init() {
    register_plugin("Blabla", "1.0", "PurposeLess");

    register_clcmd("blabla", "blabla");
}

public blabla(id)
{
    new Float:origin[3], Float:orig[3];
    pev(id, pev_origin, origin);

    //xs_vec_copy(origin, orig);
    origin[0] = orig[0];
    origin[1] = orig[1];
    origin[2] = orig[2];

    //xs_vec_len(origin);
    floatsqroot(orig[0] * orig[0] + orig[1] * orig[1] + orig[2] * orig[2]);

    //blabla
}

//XS Stock    
/*
stock xs_vec_copy(const Float:vecIn[], Float:vecOut[])
{
    vecOut[0] = vecIn[0];
    vecOut[1] = vecIn[1];
    vecOut[2] = vecIn[2];
}

stock Float:xs_vec_len(const Float:vec[])
{
    return xs_sqrt(vec[0]*vec[0] + vec[1]*vec[1] + vec[2]*vec[2]);
}

stock Float:xs_sqrt(Float:x)
{
    return floatsqroot(x);
}
*/ 


[klippy]

It's exactly the same whether you include it or copy the code in your plugin. So, logically, you should always just include xs.

[maqi]

It's the exact same thing. If you want to define the stocks everytime you want to use em then go for it.

[PurposeLessx]

Isn't bad thing to use stock in plugin? A friend said to me that and I stopped using stock

[shauli]

Originally Posted by PurposeLessx Isn't bad thing to use stock in plugin? A friend said to me that and I stopped using stock

That's not a bad "thing", maybe just a bad habit. If you're 100% sure you're going to use the function in your plugin then it shouldn't be a stock, and if you're not going to use it - it shouldn't be there at all.