[Sellize]

I've set up sublime to compile from the location of the compiler, however when I compile in sublime I get 65+ errors:

Код:

warning 219: local variable "i" shadows a variable at a preceding level

However, when I compile using pawno it compiles just fine

[Sellize]

Bumping this

[Threshold]

Have you tried solving the warning instead? I don't see this being an issue with sublime.

Just to test something, try typing something in pawno that would normally create an error and see if it actually gives you a warning.

[iiNzTicTx]

Quote:

Originally Posted by Threshold Have you tried solving the warning instead? I don't see this being an issue with sublime. Just to test something, try typing something in pawno that would normally create an error and see if it actually gives you a warning.

Don't bother solving the issues. They're not your script.


Seems to be an issue with Sublime.
Tried every method with build systems.

Works fine in pawno.
Works fine with bare.pwn.
Works fine using pawncc in command line.

Getting these errors too.

[raydx]

Nothing strange, you are using "i" everywhere (local and global). That's not correct.
And it's warning, not error.

[X337]

Make sure compiler you used to compile in sublime text is correct one. You can check that in Pawn.sublime-build file.

[Threshold]

Quote:

Originally Posted by iiNzTicTx Don't bother solving the issues. They're not your script. Seems to be an issue with Sublime. Tried every method with build systems. Works fine in pawno. Works fine with bare.pwn. Works fine using pawncc in command line. Getting these errors too.

Well without seeing the script, nobody can determine anything at all.

I don't have this issue with sublime and never have, so it must be script-related or you haven't setup sublime properly.

[ikkentim]

Make sure you're using the right pawncc arguments. iirc I had issues like these before, turned out I used wrong compiler arguments.