[Maccer]

pawn compiler version in RC4-4 - 3.2.3664 (2006-08-15)
on compuphase.com - 3.3.4127 (2009-07-03)

Update:
New features (not all) - http://compuphase.com/pawn/pawnhistory.htm
Full history - http://depositfiles.com/files/uirb1t5uo

[gotenks918]

and the point in this is??

[DiDok]

It's old?

[Daem]

Quote:

Originally Posted by Maccer pawn compiler version in RC4-4 - 3.2.3664 (2006-08-15)

they forgot

[Correlli]

Quote:

Originally Posted by Daem they forgot

No, they didn't.

[daalsdaals]

There's nothing to forget or update, it works perfectly.

[BlackFoX]

I think it is better to Update Pawn for fixed Bugs or something

[gijsmin]

this is a good idea
maby there are new functions for it (from the compuphase)

[Woet]

There are no new functions and no bug fixes that involve the way it's used in SA-MP.
Backwards compatibility would fail, a spam of topics will be created due to different pawno versions so it will only cause problems.
Just because something has a newer version doesn't mean you should update.

[Tenshi]

Most likely new version of pawno would probally just glitch the way samp/pawno will be complied.
ever thought about that?

[Remis]

Quote:

Originally Posted by Tenshi ™ Most likely new version of pawno would probally just glitch the way samp/pawno will be complied. ever thought about that?

samp and pawno can be compiled? Thats something new.

And what is about security fixes? This is the most important reason to update.

Quote:

SECURITY FIX ("arbitrary code execution" vulnerability): the CALL.pri and JUMP.pri instructions were removed, because one could use them to force a jump out of the virtual sand box of the abstract machine and call arbitrary code that is carefully laid out in the data section of the script.

Quote:

..Just because something has a newer version doesn't mean you should update.

Your statemant is reasonable for major updates. Like updating from xyz 1.0 to 2.0. Its useless to update to 2.0 if 1.0 already worked fine.
But its important to have the latest revision of the major release you want to have. Like updating from xyz 1.1 to 1.1.1 is important.
There aren't any new major releases for pawn since 2006, just smaller updates within 3.x.


Edit: Fixed the quote.
minor means something different, I meant "major"

[Kalcor]

Updating pawn is likely to introduce unwelcome incompatibilities. We have also made many patches to the pawn runtime ourselves that would need to be reimported in to the latest base.

Security concerns in terms of pawn are mild because scripts only run on the server, not the client, and most server owners aren't accepting random amx files from people they don't trust. Most servers run their own scripts which they compiled themselves. Server owners have to accept that, even without vulnerabilities in the pawn runtime, there is always a chance a script you don't have the source for or didn't compile yourself could contain something malicious.

That being said, it's possible for us to fix that reported vulnerability without updating pawn. The guy who found the vulnerability is actually the same guy who wrote the pawn decompiler and I think I was the first person he reported the problem to.