• 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. Sending SKILL commands to a running instance of ICFB

Stats

  • Locked Locked
  • Replies 18
  • Subscribers 145
  • Views 29736
  • 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

Sending SKILL commands to a running instance of ICFB

gsimard
gsimard over 16 years ago

Hi all !

 

 I was wondering if it would be possible to send SKILL instructions to a running instance of ICFB, just as if I was typing them in the console of the ICFB, but from an external process. The idea is to use my favorite editor (emacs) and being able to interact with the ICFB process (sending code, retrieving replies, in the best scenario).

 

Thank you for any advice !

Guillaume

  • Cancel
Parents
  • gsimard
    gsimard over 16 years ago

     Same here for "vi", never went past the tutorial :)

     

    I have a seemingly obvious question related to ports in SKILL, when invoking (infile "/tmp/skill-pipe") in the icfb, one usually has to keep the return value in a variable for later usage with reading and writing functions. In the icfb, however, the result of invoking (infile ...) is something like port:"/tmp/skill-pipe". Isn't it possible to use this string as a variable in itself to access the file ? ie:

    (infile "/tmp/skill-pipe") => port:"/tmp/skill-pipe"

    (lineread port:"/tmp/skill-pipe")

    This will fail because clearly it thinks I'm trying to do a range between unbound variable "port" and string "/tmp/skill-pipe".

    In Lisp (but not SKILL it seems), port:"/tmp/skill-pipe" would be something called a READ synthax, which means you could use it as the port itself instead of using a variable holding the value of the port as in:

     p = (infile "/tmp/skill-pipe") => port:"/tmp/skill-pipe"

    (lineread p)

     

    I hope this is a bit clear to you guys,

    Guillaume

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • gsimard
    gsimard over 16 years ago

     Same here for "vi", never went past the tutorial :)

     

    I have a seemingly obvious question related to ports in SKILL, when invoking (infile "/tmp/skill-pipe") in the icfb, one usually has to keep the return value in a variable for later usage with reading and writing functions. In the icfb, however, the result of invoking (infile ...) is something like port:"/tmp/skill-pipe". Isn't it possible to use this string as a variable in itself to access the file ? ie:

    (infile "/tmp/skill-pipe") => port:"/tmp/skill-pipe"

    (lineread port:"/tmp/skill-pipe")

    This will fail because clearly it thinks I'm trying to do a range between unbound variable "port" and string "/tmp/skill-pipe".

    In Lisp (but not SKILL it seems), port:"/tmp/skill-pipe" would be something called a READ synthax, which means you could use it as the port itself instead of using a variable holding the value of the port as in:

     p = (infile "/tmp/skill-pipe") => port:"/tmp/skill-pipe"

    (lineread p)

     

    I hope this is a bit clear to you guys,

    Guillaume

    • 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