[GsiX]

@BAIL
This might out topic..
I just curious to know a little more about your background.
Beside fall in love with your signature, I also love and quite entainment with every post you made. There is hidden knowledge behind those engineering language (tho Google translate always involved with me).

Curiously to know what made of you..?

Later edit:
The only thing I know about you is your name when I hit the donate button, noting more noting less.
Seem like your legacy more legend than fact.
Interesting to know if you have some kind of blog.

[Mathias.]

Cannot use the socket extension...

http://gyazo.com/140e92a5522b55634ed842a6b4f1957a

it compile fine on older compiler.

the code is simply

#include <socket>

[puga4off]

Cool

[nergal]

just a quick question.

Is there anything regarding Natives and Forwards with the new API and syntax?

What about the old native rule where you can't return a float? Do they still require the _: empty tag to return a float?

[sarysa]

Yanno, I come from an OOP background and for awhile I've thought it would be a bad idea to move Pawn to OOP for compatibility reasons.

But now that I've read this, it sounds like you guys know your stuff and are taking a cautious approach with the endeavor, so all the power to you. I hope it goes well, as I'll be eagerly awaiting to stop needing to make messes like this:

Spoiler

// ROTT monitored rockets
#define MAX_ROCKETS 30
#define FIREBOMB_EXPLOSION_RADIUS "150" // it's input as a string, so...lol
#define FIREBOMB_EXPLOSION_DISTANCE_BETWEEN 100.0
new RMR_Spec[MAX_ROCKETS];
new RMR_RocketEntRef[MAX_ROCKETS];
new Float:RMR_NextDeviationAt[MAX_ROCKETS];
new Float:RMR_HomingPerSecond[MAX_ROCKETS];
new Float:RMR_RandomDeviationPerSecond[MAX_ROCKETS];
new RMR_CurrentHomingTarget[MAX_ROCKETS];
new bool:RMR_CanRetarget[MAX_ROCKETS];
new Float:RMR_RocketVelocity[MAX_ROCKETS];
new bool:RMR_HasTargeted[MAX_ROCKETS];
new RMR_FirebombCount[MAX_ROCKETS];
new RMR_FirebombsActivated[MAX_ROCKETS];
new RMR_FirebombDamage[MAX_ROCKETS];
new RMR_RocketOwner[MAX_ROCKETS];
new Float:RMR_FirebombInterval[MAX_ROCKETS];
new Float:RMR_ChainExplosionStartedAt[MAX_ROCKETS];
new Float:RMR_LastPosition[MAX_ROCKETS][3];
new Float:RMR_LastAngle[MAX_ROCKETS][3];

also...

Originally Posted by Zephyrus why, just why? at least before it was a language that was used by some other stuff like samp, but now this just makes it a new language to learn for a lot of ppl. javascript would be a better choice overall, as its the most widespread scripting language with the fastest JITs out there. also countless libraries have been written in js already...

I don't know if it's the most widespread, but web based apps and native apps have always been two different worlds, and C++/C#/Java tend to dominate native apps. (and TF2 is definitely a native app) I for one would be uncomfortable if Pawn went in a more JS direction, as my background is strongly in native development.

[Aderic]

I love the new object oriented approach! I can't wait to rewrite my plugins on the new API!

[LambdaLambda]

I don't mean to spam, but when SM 1.7 will be out (stable ver)?

[asherkin]

Originally Posted by LambdaLambda I don't mean to spam, but when SM 1.7 will be out (stable ver)?

When it's ready.

[eXemplar]

Apologies if this is a stupid or repeated question but are there any reasons why, if pawn is being troublesome, that a different language like lua or a lisp dialect cannot be used instead?

[BAILOPAN]

eXemplar: Many reasons - it is not so easy a decision to make. There are other projects which embed other languages in Source. Ours is Pawn pretty much by definition, without a complete rewrite.