• 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. Custom IC SKILL
  3. regarding float to string conversion

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 18609
  • 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

regarding float to string conversion

fazul
fazul over 14 years ago

Hi everybody

i am very new to SKILL programming, so this might be a very simple question ... Actually i want to do

Float to String converstion . I am working on IC5.1 framework.

upon searching i found this method

strVar  = 1.23e4

ftVar = sprintf( nil "%.2e" strVar)

is there any other neater way of doing ? the problem i found with the above method is that even smaller float values say 23.4 will be

forcibly converted to scientific notation "2.34e+01" .. which looks pretty ugly(aestically)  on my ReportField.

background :

It seems like ReportField in IC51 doesnt support scientific notation for float values.. So i am stuck on doing the Float2String conversion

before displaying it in the ReportField...

hope i made my problem clear. Please advice me if there is a better way of doing this.

thanks in advance,

Have a great day

Fazul 

 

 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    You could also use the functions aelEngNotation(), aelSuffixNotation() or aelScientificNotation() - depending on what you want.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    You could also use the functions aelEngNotation(), aelSuffixNotation() or aelScientificNotation() - depending on what you want.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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