Skill Lint: Using global variables, form name

[Suresh Jeevanandam]

Hi,
The skill form is always stored as a global variable, But is there a
way to tell SKILL Lint that this particular variable is used to store a
skillForm?

Thanks in advance,

regards,
Suresh

 

[Andrew Beckett]

On Tue, 29 Nov 2005 15:39:38 +0530, Suresh Jeevanandam
<sureshj@DELETETHISti.com> wrote:

Hi,
The skill form is always stored as a global variable, But is there a
way to tell SKILL Lint that this particular variable is used to store a
skillForm?

Thanks in advance,

regards,
Suresh

Give the form global variable a sensible prefix - (I would use (say) "AB").
Then in the SKILL Lint form you can specify the prefixes you're using - and it
will tolerate correctly named global variables.

Regards,

Andrew.

 

[Bernd Fischer]

As far as I'm aware of every form data structure has to
be stored in a global variable.

There are a two keyword arguments that I know to tell
sklint that specific globals are allowed:

?prefixes l_prefixList; you can define a list of prefixes for your globals
?globals l_globals; list of allowed globals


I believe the ?prefixes argument is equivalent to the 'Package Prefixes' in
the SKILL Lint form.

Bernd


Suresh Jeevanandam wrote:

Hi,
The skill form is always stored as a global variable, But is there a
way to tell SKILL Lint that this particular variable is used to store a
skillForm?

Thanks in advance,

regards,
Suresh

 

[Svenn Are Bjerkem]

In article <0omoo11gvoaghkp64144ufcv4ltm4n0gjg@4ax.com>,
andrewb@DcEaLdEeTnEcTe.HcIoSm says...

Give the form global variable a sensible prefix - (I would use (say) "AB").


But code from you originates from Cadence and therefore you use "ab"?

--
Svenn

 

[Andrew Beckett]

On Wed, 30 Nov 2005 12:06:02 +0100, Svenn Are Bjerkem <svenn.are@bjerkem.de>
wrote:

In article <0omoo11gvoaghkp64144ufcv4ltm4n0gjg@4ax.com>,
andrewb@DcEaLdEeTnEcTe.HcIoSm says...
Give the form global variable a sensible prefix - (I would use (say) "AB").


But code from you originates from Cadence and therefore you use "ab"?

Svenn,

I'm a bit naughty, to be honest. I starting writing lots of code before we
introduced the convention that non-Cadence code should use a prefix which
begins with a capital letter. I tended to interpret this as "I'm Cadence so
I can get away with the prefix I always used, 'ab'" - but a stricter
interpretation of the guidelines would mean that I'd use "Ab" or "AB".

These days, if I'm writing a solution, I often convert my "ab" prefixed code to
use "CCS" instead (Cadence Customer Support) as in customer support we have
some guidelines about SKILL code in solutions.

Anyway, R&D should not use functions that begin with upper case, so that's
the reason why we recommend customers using a prefix starting with upper case.

There you are. Clear as mud ;-)

Andrew.