Firestorm preprocessor not parsed/linted correctly about sublime-lsl HOT 8 CLOSED

Ok, a clean install fixed it.
Thanks for your support.

from sublime-lsl.

SublimeLinter runs lslint with these flags:

• i
• m
• w
• z

Compare:

https://github.com/Makopo/lslint/blob/8c29d5ff36d47395932477a7514b3ca729a0a8f3/lslmini.cc#L855-L883

https://github.com/XenHat/SublimeLinter-contrib-lslint/blob/6674409782a32113e724a1b1e44967bcd5b43989/linter.py#L179-L191

Currently the syntax file at ./.sublime/syntaxes/LSL.sublime-syntax doesn't support the preprocessor code. However that shouldn't be a problem, as that only gives the visual feedback. I'll fix that in the next release.

Looking at your firestorm preprocessor code, I noticed two things. Keep in mind, I do not use this so here's a guess:

• You are missing a default statement within the switch. Compare the firestorm preprocessor docs.
• The switch parameter compared to the value in one of the statements results in an integer as that is the condition passed to the built if ... else if ... else construct. So you might be able call a function there that returns whatever, but I haven't tested that. In your case function could be an integer function which is then compared to the constants in the built conditional statements as in if (function == RNDGETINT) { .... }. I'm also not sure if your RNDGETINT is a user declared function in your case, and I'm not sure if the firestorm preprocessor can handle that. But you'd have to test.

from sublime-lsl.

As a follow up:

• adding a default to the switch, lslint only reports variables as undeclared in your code.
• If the missing default statement error was your syntax error, I cannot reproduce your error.

Sublime Text:

    channel: dev
    build: 3156
    portable: True
    platform: Windows
    architecture: x64

from sublime-lsl.

Hi,
I got the same errors with the example from the firestorm's page: http://wiki.phoenixviewer.com/fs_preprocessor

I'm a bit perplex...

from sublime-lsl.

@MisterFoxi I cannot reproduce your errors with the examples either.

Could you try with SublimeLinter v4.0.0 (or later) as there's a lot of work being done on that currently?

https://github.com/SublimeLinter/SublimeLinter

via:

//  in 'Packages/User/Package Control.sublime-settings'

    "install_prereleases":
    [
        "SublimeLinter"
    ]

The stable 4.0 release should be out soonish, in case you want to wait for that.

from sublime-lsl.

@MisterFoxi SublimeLinter v4 and later has an output panel for easier reference.

from sublime-lsl.

Still the same...
BB=LSL is v1.4.1
Linter is V4.0.0-rc9
contribution-lslint is v1.4.0
Tooltip is v1.0.3

and I don't have the outputs you seems to have.

Thanks.

from sublime-lsl.

@MisterFoxi Are you sure your issue is related to the =BB= LSL package?

Please run SublimeLinter in debug mode.

You have redundant packages in your setup.

Of which SublimeLinter-contrib-lslint and =BB= LSL both run lslint via SublimeLinter. To be sure your output for lslint is from this package, please check via the debug output to the console (View > Show Console).

For the following packages, see their own repo:

• SublimeLinter-contrib-lslint: https://github.com/XenHat/SublimeLinter-contrib-lslint
• TooltipLSL: https://github.com/makopo/sublime-text-tooltip-lsl

from sublime-lsl.