Stats

  • Locked Locked
  • Replies 8
  • Subscribers 145
  • Views 32498
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SKILL if statement

nosaj

Can anyone point out why doesn't the if statement below return YES since argType is a string?

Code : if.il
;=============================
a="a"
argType=type(a)
printf("argType=(%s)\n" argType)

if( argType=="string" then
        printf("YES (%s)\n" argType)
else
        printf("NO   (%s)\n" argType)
)
;=============================


CIW Output :

load("if.il")
argType=(string)
NO   (string)
t

Parents

  • Your parentheses are all messed up. Why have you got a close parenthesis after the "then"?

    if() is a function call - it needs to be:

    if(expression then statement1 statement2 ... statementN else elseStatement1 ... elseStatementN)

    (can be over multiple lines).

    Rather than writing nested if-then-else statements, this might be better as a cond:

    cond(
      (geGetSelSet()~>lpp=='("M1" "drawing")  geGetSelSet()~>lpp='("M2" "drawing"))
      (geGetSelSet()~>lpp=='("M2" "drawing")  geGetSelSet()~>lpp='("M3" "drawing"))
    ...
      (t  geGetSelSet()~>lpp='("LB" "drawing"))
    )

    Personally I'd probably write it a bit differently - probably:

    geGetSelSet()~>layerName=
      case(car(geGetSelSet())~>layerName
        ("M1" "M2")
        ("M2" "M3")
        ("M3" "M4")
       ...
        (t "LB")
      )

    This is not checking that the purpose is drawing, but you could always add a when() or if() around it to check that the purpose is "drawing" first if that matters. As you can see, the above is very concise and clear. I'm only checking the first layer, but your code would only work with a single shape anyway - in my case it will work for multiple shapes, but only look at the layer of the first shape to determine the layer to change to.

    SKILL is a functional programming language - so case, cond, if etc all have a return value that you can do something useful with, rather than always have to think in terms of "statements". In this example, each branch of the case is returning the layer you want to change to - which avoids lots of duplication of the code which sets the layer (or lpp).

    Regards,

    Andrew.

Reply

  • Your parentheses are all messed up. Why have you got a close parenthesis after the "then"?

    if() is a function call - it needs to be:

    if(expression then statement1 statement2 ... statementN else elseStatement1 ... elseStatementN)

    (can be over multiple lines).

    Rather than writing nested if-then-else statements, this might be better as a cond:

    cond(
      (geGetSelSet()~>lpp=='("M1" "drawing")  geGetSelSet()~>lpp='("M2" "drawing"))
      (geGetSelSet()~>lpp=='("M2" "drawing")  geGetSelSet()~>lpp='("M3" "drawing"))
    ...
      (t  geGetSelSet()~>lpp='("LB" "drawing"))
    )

    Personally I'd probably write it a bit differently - probably:

    geGetSelSet()~>layerName=
      case(car(geGetSelSet())~>layerName
        ("M1" "M2")
        ("M2" "M3")
        ("M3" "M4")
       ...
        (t "LB")
      )

    This is not checking that the purpose is drawing, but you could always add a when() or if() around it to check that the purpose is "drawing" first if that matters. As you can see, the above is very concise and clear. I'm only checking the first layer, but your code would only work with a single shape anyway - in my case it will work for multiple shapes, but only look at the layer of the first shape to determine the layer to change to.

    SKILL is a functional programming language - so case, cond, if etc all have a return value that you can do something useful with, rather than always have to think in terms of "statements". In this example, each branch of the case is returning the layer you want to change to - which avoids lots of duplication of the code which sets the layer (or lpp).

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.