• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. A weird result about the function "IF"

Stats

  • Replies 3
  • Subscribers 159
  • Views 753
  • Members are here 0
More Content

A weird result about the function "IF"

stillfish
stillfish over 14 years ago

I run the following line in skill command line :


Skill > if((7.15>7.1+0.05) println("#") println("$"))

and then it shows

"#"
nil

It seems the condition of "IF' was passed, which is not what i expected.

And even i change the syntax to if(greaterp(7.15 7.1+0.05) println("#") println("$"))

it still shows

"#"
nil

Can anyone explain about this result, thanks!

  • Sign in to reply
  • Cancel
  • PCB George
    PCB George over 14 years ago
    Try something like

    if ( ( 7.15 > 7.1+0.05 )

      then

        println(“#”)

      else

        println(“$”)
    )

    ~~

    George
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • fxffxf
    fxffxf over 14 years ago

    Computers are digital machines while floating point math is analog. A floating point number cannot always be represented exactly in a digital representation. This means when you do any logical comparison of floating point numbers, you must either use an Epsilon value or force a rounding operation.

    See the web reference in the documentation for axlGeoEqual.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • stillfish
    stillfish over 14 years ago

    Thanks for your reply.

    I decide to use the rounding function before comparing two floating value, and it works fine.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Cadence Guidelines

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information