Scope form name variable

 Hi Paul,

Well, a form symbol has to be global, so you can't avoid that, but what you can do is to make sure that it is named with an appropriate prefix (e.g. PS or MY etc.), and then on the Lint form you enter this for the package prefixes - this should allow Lint to recognise that these are required globals but have the appropriate prefix and so should not reduce your score.

Hope this helps!

Lawrence.

As far as I know the variable which holds the form data structure has to be global.
But you can specify a prefix for the global variables e.g. GB, GBmyFormDataStruc
and follow this solution

 

 Paul,

I forgot to mention that you can have all the code in one file, if that's more convenient.  In fact, the "poor score" items are "diluted" over the length of the file, so as the file gets longer, the effect of the 'poor score' items is reduced, assuming that the rest of the code is good.

Regards,

Lawrence.

Lawrence only ad the prefix to the Package Prefixes will not do the job you also have to disable STRICT checking,

see the solution, I tested it ;-).

It took me a while to figure this out so hopefully I can save someone a few minutes by sharing the info here. The link above doesn't work for me as of June 2019, but here is the usage of sklint to ignore a prefix of "MY_" (such as "MY_GLOBAL_VARIABLE1") with a generic SKILL file name:

;sklint(?file "qscSkill.il" ?prefixes list('MY_))

Note that I'm an Allegro SKILL user so hopefully usage is the same for all SKILL variants.

EvanShultz said:

The link above doesn't work for me as of June 2019

I fixed the link (I think it had mainly been line-wrapped) but if you're using Allegro, I don't think it will help you. In Virtuoso there's a SKILL Interactive Development Environment with a user interface, but in Allegro I believe you just have access to the command-line (function call) interface that you've found...

Regards,

Andrew.