Optional local variables and attributes, mainly handy to define intermediate values based on the arguments. Locals are not visible from outside (in the software) or by the designer. The locals are evaluated from top to bottom and can combine the parameters, the globals as well as earlier defined locals. Attributes are key/value pairs that are intended mostly as flags in the software. They are defined in the PDAFlow API and are intended for software internal use. Aspects like "being default" or "not yet placed" as well as "schematic versus layout mismatch" type of attributes can be aligned on between software vendors to support designers further.


This element does not have attributes. The elements are shown below, in a sorted per type fashion.
In case a list is printed after an element, it indicates that you can have many, otherwise it should be a single element. With a optional it tells the element is not required.

<locals> ...
attribute> ... </attribute>   list
  <local> ... </local>   list


The schema file can be downloaded or viewed at xPDK_Base.



Type pdaAttributeType documentation: Attributes are key/value pairs to annotate building blocks and views with information that is likely to be software specific. So it is more a 'flag' then a value. The value is just a string and not something with an expression in it.


Type pdaNamedValue documentation: Create a named value with expression / type support.