SKILL doc

[RolfK]

Dear ALL,

can somebody help me on this:
Where (in the cadence doc) do I find the possible values for the types
described by Finder tool.
I guess there are a lot of emums I would like to see. Is there a list
of types and possible values and explanation about each value
somewhere ?

E.G. the "t_propType"described by

dbCreateProp(
g_object
t_name
t_propType <=======
g_value
)
=> d_prop / nil

Thanks a lot

Rolf

 

[Riad KACED]

Hi Rolf,

The best doc I know that answers your question is :
The CadenceŽ Design Framework II SKILL Functions Reference
UNIX> acroread $CDSHOME/doc/skdfref/skdfref.pdf
I would advice to read the first and last sections of Chapter 2. They
are about understanding the DFII database: Objects, Attributes,
Properties ... etc.

Back to your specific question.
There is a section named 'Access Function Argument Types' in Chapter
as explained earlier, it states:
"A function argument is of a particular type, which are generally
obvious from the name of the argument. The following list describes
those types that are not obvious from the function description."
Unfortunately, the "t_propType" wasn't in that list :-( It's been
assumed as an obvious apparently.
Well, according to the name of this argument, "t_propType" is very
likely to be a 'Property Attribute' of type 'string' (the t_ prefix
stands for a string dataType). Assuming that, one can then go into the
'property attributes' table as detailed in the above doc at Chapter 2 -

Description of Database Objects -> property attributes. It is at
page 711 of my doc (Version 6.31 of July 2007). This table shows an

attributes called 'valueType' which is of type string and whose values
are:
---
“boolean” Boolean
“fileName” file name string
“float” Floating-point integer
“hierProp” Property list
“ILExpr” IL expression string
“ILList” IL list
“int” Integer
“NLPExpr” NLP expression string
“string” String
“time” Time-valued string
---

This kind of exercise becomes obvious when you get that thing named
after 'experience' Most of experienced people just need to look at
the doc of the function itself. I'm not there yet, the DFII pdf is
always somewhere at the corner of my descktop

Hope this help !
Regards,
Riad.

 

[Andrew Beckett]

Riad KACED wrote, on 11/04/08 23:28:

Hi Rolf,

The best doc I know that answers your question is :
The CadenceŽ Design Framework II SKILL Functions Reference
UNIX> acroread $CDSHOME/doc/skdfref/skdfref.pdf
I would advice to read the first and last sections of Chapter 2. They
are about understanding the DFII database: Objects, Attributes,
Properties ... etc.

Back to your specific question.
There is a section named 'Access Function Argument Types' in Chapter
as explained earlier, it states:
"A function argument is of a particular type, which are generally
obvious from the name of the argument. The following list describes
those types that are not obvious from the function description."
Unfortunately, the "t_propType" wasn't in that list :-( It's been
assumed as an obvious apparently.
Well, according to the name of this argument, "t_propType" is very
likely to be a 'Property Attribute' of type 'string' (the t_ prefix
stands for a string dataType). Assuming that, one can then go into the
'property attributes' table as detailed in the above doc at Chapter 2 -
Description of Database Objects -> property attributes. It is at
page 711 of my doc (Version 6.31 of July 2007). This table shows an
attributes called 'valueType' which is of type string and whose values
are:
---
“boolean” Boolean
“fileName” file name string
“float” Floating-point integer
“hierProp” Property list
“ILExpr” IL expression string
“ILList” IL list
“int” Integer
“NLPExpr” NLP expression string
“string” String
“time” Time-valued string
---

This kind of exercise becomes obvious when you get that thing named
after 'experience' Most of experienced people just need to look at
the doc of the function itself. I'm not there yet, the DFII pdf is
always somewhere at the corner of my descktop

Hope this help !
Regards,
Riad.

The key point is that the cdsFinder tool is intended to be a quick reference and
NOT the entire documentation of the function.

So for more details, you would look in the full documentation, under cdsdoc (or
cdnshelp in newer releases) - search for the function you're aiming to use.

Regards,

Andrew.