• 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. ISO 8601 timestamp

Stats

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

ISO 8601 timestamp

Yaosan Yeo
Yaosan Yeo over 13 years ago

I'm trying to work with timestamp in ISO 8601 format. The timestamp looks like this: "2012-08-07T16:38:45.693245Z". I want to construct a report field which displays this date in one of the columns. I know in SKILL the standard time string looks more like this: "Aug  1 12:00:32 2012". Is there an easy way to convert my input time string to the time string SKILL recognize?

I've tried to format the input time string then use "date" in command line to convert the time stamp but it is really really slow:

date -d "2012-08-07 16:38:45.693245 UTC" "+%b %_d %k:%m:%S %Y"

Is there another way around this problem? Thanks!

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

    For the pcreSubstitute() issue, my guess is that you're using IC614 or earlier. In that version you could only specify the string. From IC615 the definition is:

    pcreSubstitute(
    [o_pcreObject]
    t_string
    )
    => t_result | nil

    If o_pcreObject is not provided, pcreSubstitute copies the input
    string and substitutes all pattern tags in it using the corresponding
    matched strings from the last pcreExecute/pcreMatch* operation.

    So I was passing in the optional pattern object. So missing it out is OK - it will work in both IC614 and IC615.

    As for the daylight saving time - you could initialize the tm structure using timeToTm(stringToTime(getCurrentTime())) rather than timeToTm(0) which should give the current DST setting - but whether that's right for the time in question is another matter...

    I wasn't really sure what the "right" thing to do was here...

    Andrew.

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

    For the pcreSubstitute() issue, my guess is that you're using IC614 or earlier. In that version you could only specify the string. From IC615 the definition is:

    pcreSubstitute(
    [o_pcreObject]
    t_string
    )
    => t_result | nil

    If o_pcreObject is not provided, pcreSubstitute copies the input
    string and substitutes all pattern tags in it using the corresponding
    matched strings from the last pcreExecute/pcreMatch* operation.

    So I was passing in the optional pattern object. So missing it out is OK - it will work in both IC614 and IC615.

    As for the daylight saving time - you could initialize the tm structure using timeToTm(stringToTime(getCurrentTime())) rather than timeToTm(0) which should give the current DST setting - but whether that's right for the time in question is another matter...

    I wasn't really sure what the "right" thing to do was here...

    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