What is the difference in the way these variables are declared?

Leech_v2 · **Author**

What is the difference between adding 'new' and removing 'new'?

What I want to know is the purpose of using 'new' in combination with other specifier.
As far as I know, the feature of 'new' is that it allows declared variables to use runtime expressions as initialization expressions. However, runtime expressions cannot be used outside of a function, so I am wondering why it can be combined with other specifier?

Code:

new stock gVar;
stock gVar;

new static gVar;
static gVar;

new public gVar;
public gVar;

new static stock gVar;
static stock gVar;

**Bugsy**

See page 61 (PDF page 65)

https://raw.githubusercontent.com/co.../pawn-lang.pdf

Leech_v2 · *Last edited by Leech_v2; 10-07-2023 at 01:31.*

Quote:

Originally Posted by Bugsy

See page 61 (PDF page 65)

https://raw.githubusercontent.com/co.../pawn-lang.pdf

? The file you sent did not explain my problem.
What I want to know is the purpose of using 'new' in combination with other specifier.
As far as I know, the feature of 'new' is that it allows declared variables to use runtime expressions as initialization expressions. However, runtime expressions cannot be used outside of a function, so I am wondering why it can be combined with other specifier?

fysiks · *Last edited by fysiks; 10-07-2023 at 02:45.*

"new" just creates a new variable of local scope. If it's used on the top-level, it's effectively a global variable with respect to the plugin's own code. When declared in this scope, there is no runtime execution happening so only constant expressions are allowed. When you create a variable in a local scope that is processed at runtime (like inside of a function) then you can initialize it with any normal code.

"new", "static", and "public" are mutually exclusive expressions so I'm not sure why you have any combination of those. References:

Quote:

Originally Posted by Pawn Language Guide

To declare a global variable as static, replace the keyword new by static.

Quote:

Originally Posted by Pawn Language Guide

Global “simple” variables (no arrays) may be declared “public”
in two ways:
⋄ declare the variable using the keyword public instead of new;
...

Leech_v2

Quote:

Originally Posted by fysiks

"new" just creates a new variable of local scope. If it's used on the top-level, it's effectively a global variable with respect to the plugin's own code. When declared in this scope, there is no runtime execution happening so only constant expressions are allowed. When you create a variable in a local scope that is processed at runtime (like inside of a function) then you can initialize it with any normal code.

"new", "static", and "public" are mutually exclusive expressions so I'm not sure why you have any combination of those. References:

Because in actual testing, 'new' can be combined with 'public', 'static', and 'stock'.
That's why I have questions

Jhob94

Pawn is a dead language for several years and it happens because this is not the most reliable language.
The deeper you look the more senseless stuff you'll find.
AMXX, SourceMod and SA:MP are the only ones using it. We still use it because it's a choice from many many years when Pawn could still improve and now it is kinda too late to change because of the massive work that the community has been doing all those years.

thEsp

Quote:

Originally Posted by Leech_v2

Because in actual testing, 'new' can be combined with 'public', 'static', and 'stock'.
That's why I have questions

static allocates a variable but doesn't guarantee to free it in the end of the body. public does what it says - exposes the variable to the virtual machine. stock is nothing special it just tells the compiler to discard the following identifier if it's never used.

Quote:

Pawn is a dead language for several years...

Since you're that smart guy why don't you go ahead and create a new magnificent language, compiler and runtime?