CfgFunctions parser fails on some macros combinations

[AlexTriada]

Great module, I really like it, man, you can deal with the functions, or suggest how to prescribe them in .hpp so that they do not create notifications of type "Possibly undefined variable some_fnc_name_function" - it's very distracting

[SkaceKamen]

Functions need to be defined in description.ext (or the definition must be included there) and the expected format is described here:
https://community.bistudio.com/wiki/Arma_3_Functions_Library#Adding_a_Function

there is also limited support for macros, so there's posibility your functions wont get recognized properly if the definitions rely on macros.

[AlexTriada]

Functions define in file functions.hpp, mission https://github.com/AlexTriada/A3-AntiStaki

[Wyqer]

Similar to: #20
Current Version: 0.10.0

Description
We're also getting the "possibly undefined variable" on each of our own created functions, which worked fine (even with header as tooltip for parameters, etc.) some versions ago.

Way to reproduce:

• Clone https://github.com/KillahPotatoes/KP-Liberation
• Switch to branch v0.97S13
• Open cloned repo at root directory (right click KP-Liberation folder, Open with Code)
• Wait until the indexing is finished
• You'll get about 645 warnings about possibly undefined own functions

Structure of project explained

• In the repository is the missionframework folder, which will be the root folder of a mission.
• So there is the important description.ext located, which includes here Link To File our overall CfgFunctions
• That includes the functions of each module like this module function declaration
• So a function like KPLIB_fnc_common_createUnit is declared.
• In older version this worked without any issues, even the header was parsed right and gave nice parameter and example tooltips on the functions in the code. We have this issues like maybe 2 or 3 versions, when the Autocompletion suggestions no longer work #52 came up.

Screenshot

[SkaceKamen]

Thanks for detailed info, I'll look into it when I have time

[SkaceKamen]

@Wyqer: This issue with your description.ext is usage of __EVAL()
That is really complicated macro in terms of parsing ... I'll try to work around it.

[Wyqer]

Ok, good to know the possible cause of the issue.
So when you've removed the __EVAL(), it was fine so far?
We've a similar issue also on the old framework. There it seems that the indexing can't finish fully and therefore the whole linting and the functions/commands tooltips aren't working.
If you've some time to spare, you could have a look at it with the master branch of the liberation repository. Maybe you find something useful to improve anything.
But in the end the old framework isn't that important and it could also be just bad code which causes the issue, even if it worked fine earlier also in the old framework.

In any case many thanks for your support and work on sqflint, you're making our work so much easier.

[SkaceKamen]

Yes, when you remove the __EVAL, it's fine. I've already wrote a fix and will publish it soon, I just want to test if it doesn't break anything else.

@AlexTriada Your description.ext has multiline macros, which aren't supported yet, let me see if I can do anything about it.

[SkaceKamen]

@AlexTriada sorry, but the usage of macros in your description.ext (and correlating hpp files) is way too complicated right now, maybe when I have time to completely rewrite the preprocessor :'(

@Wyqer the issue with __EVAL should be fixed now (0.10.1)

[Wyqer]

Works perfect now again. Just some other thing, but I'll create a new issue for that. Thanks for adding the feature to support the __EVAL() in description.ext

[Wyqer]

Edit, the leftover now is just what I reported in #55

[jonathan-richer]

Are the functions getting parsed in the config.cpp?

class CfgFunctions {
	class JRS_VehicleDeploy {
		tag = "JRS";
		class vehicle {
			file = "\jrs_vehicle_deploy\functions\vehicle";
			class deployObjects { };
			class initVehicle { };
		};
		class utils {
			file = "\jrs_vehicle_deploy\functions\utils";
			class createObject { };
		};
	};
};

Or am I doing something wrong?