Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 16383
  • 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

Save variables to a file and load them later

zmleitao

Is there an easy way in SKILL to save variables to a file so as to be able to later loading them from that same file.

I am interested in saving tables and lists, for instance.

Parents
  • tweeks

    tweeks said:

    Note the code would be way simpler if SKILL had a read syntax for tables.

    Actually this brings up an interesting point: In SKILL, the only types whose default print syntax is also a useful read syntax are:

    • symbols
    • lists (including DPLs and assoc lists)
    • fixnums
    • flonums
    • strings
    • ports (but only the filename, not whether it was input or output)

    Anything else does not (by default) print out enough information to recreate the object, so you have to do extra work to either

    1. Generate code that recreates the object (e.g. makeTable() for a table), or
    2. Convert the object into one of the above types, then convert back.

    Footnotes:

    • You can print structs, tables, and arrays with printstruct, if you have a skillDev license, but the output will not eval back into the objects when read with readline--you need to parse it.
       
    • You can print function objects using pp(), and they will eval to a new function object when read with readline. 
      • Comments and formatting are lost, though if you had the debugger on when the code was loaded, you can find the line number in the file the procedure was loaded from by getting functionName._loadFile and functionName._loadLine

     

Reply
  • tweeks

    tweeks said:

    Note the code would be way simpler if SKILL had a read syntax for tables.

    Actually this brings up an interesting point: In SKILL, the only types whose default print syntax is also a useful read syntax are:

    • symbols
    • lists (including DPLs and assoc lists)
    • fixnums
    • flonums
    • strings
    • ports (but only the filename, not whether it was input or output)

    Anything else does not (by default) print out enough information to recreate the object, so you have to do extra work to either

    1. Generate code that recreates the object (e.g. makeTable() for a table), or
    2. Convert the object into one of the above types, then convert back.

    Footnotes:

    • You can print structs, tables, and arrays with printstruct, if you have a skillDev license, but the output will not eval back into the objects when read with readline--you need to parse it.
       
    • You can print function objects using pp(), and they will eval to a new function object when read with readline. 
      • Comments and formatting are lost, though if you had the debugger on when the code was loaded, you can find the line number in the file the procedure was loaded from by getting functionName._loadFile and functionName._loadLine

     

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.