[Release] GScyntax

[SuperNovaAO]

Checks your GSc-Syntax.

If this tool says that everything is fine, this is not necessarily true (why didn't IW make brackets after function calls necessary, for example, now it's impossible to check if something is a function that returns an object that again could have functions so "self a b c d();" is accepted...)

If it finds an error, that isn't necessarily true either.

Also the tool does not check on functionnames/initialized variables anywhere.

To use, drag a GSc onto the exe and wait.

Download:
  GScyntax_v0.11.zip (Size: 24.94 KB / Downloads: 479)

Bug reports are VERY welcome. Post the code AROUND the place that got detected wrong and the error the tool gave and I will look into it.

Related links

[d0h!]

thanks mr. Awesom-O

[iAegle]

Yay now I dont have to restart Black Ops after every Bad Syntax crash

[Pozzuh]

I can't just drag and drop the file on it, when I do that it just crashes. I have to do it via cmd.exe. Also I think it doesn't ignore text/code in /* and */.
Oh, and good job on the program!

Edit: Drag and dropping seems to work now, i've no idea what I did wrong.

Edit 2: Mhh, I have no idea why but it crashes sometimes... *testing*

Edit 3:
C:\Program Files (x86)\Activision\Call of Duty 4 - Modern Warfare\raw\maps\backup\mp\gametypes>GScyntax.exe _tweakables.gsc
Exception EConvertError in module GScyntax.exe at 000064BE.
'1.0' is not a valid floating point value.
And then it crashes. Also, it's a false positive because this is a stock cod4 .gsc.

Edit 4:
C:\Program Files (x86)\Activision\Call of Duty 4 - Modern Warfare\raw\maps\backu
p\mp\gametypes>GScyntax.exe _teams.gsc
Exception EConvertError in module GScyntax.exe at 000064BE.
'0.05' is not a valid floating point value.
It seems to crash with syntax errors about floats? (False positive again)

C:\Program Files (x86)\Activision\Call of Duty 4 - Modern Warfare\raw\maps\backu
p\mp\gametypes>GScyntax.exe _shellshock.gsc
Exception EConvertError in module GScyntax.exe at 000064BE.
'0.5' is not a valid floating point value.
Again, it's about a float. And a false positive!

I'm seeing a pattern here

Related links

[blackout612]

This is much needed thank you so much

[SuperNovaAO]

It ignores comments.

[Sh0tGuN2197]

(03-18-2011 22:06)SuperNovaAO Wrote:  It ignores comments.

This is nice Thanks! can't wait to see how helpful this will be

[Pozzuh]

Yes, it's really about the floats (Read my edits above).

Code:

init()
{
    if(1)
    {
        shit = true;
        float = 0.5;
    }
}

Makes it crash.
Remove the float = 0.5; and it doesn't crash. Or add another syntax error in front of the float and it works.

Related links

[SuperNovaAO]

Floats worked before. Than I changed it to work with lazy floats (.5) and apparently didn't try it on normal floats.

Also you having 64bit can be the problem

Also read the 1st post about bug reports

[Pozzuh]

What do you mean post the code around it?

http://pastebin.com/4vLR3FhE And the small code I posted above.

I also have a suggestion, maybe you can add line numbers on errors.