[Dubya]

No it isn't. In fact, doing this would be a great way to organize your code. Just remember one thing, don't name the includes for your CMDs, or stocks with a .inc, do a .pwn, and include them like this:

pawn Код:

(REAL SCRIPT)

#include <a_samp>
#include <sscanf2>
#include <streamer>
#include <zcmd> // or whichever processor.
// other normal includes,

// now, your includes for better script optimization

// first, make a folder where you will be placing your includes.
// in this instance, i will name the folder 'script'
// place colors first, as you might use them in your other ones, then right after, stocks, as you would use them
// then publics, as you will also use them.
#include "script\stocks.pwn"
#include "script\publics.pwn"
#include "script\commands.pwn"
#include "script\other.pwn"

Now, inside of the stocks.pwn would look like:

pawn Код:

stock GetPlayernameEx(playerid)
{
    // Code.
}
// any other stocks in here.

And publics.pwn would look the same, only you would be placing the publics that you would have in there.
And commands.pwn would look the same, only you would be placing your self-made commands in there. etc (zcmd) CMD:blabla, etc.

You can have a lot more if you want, it would be easier to find a stock if you did it like this, or a public, and so there forth.