• 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. Running perl from skill and getting output one at a tim...

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 144
  • Views 19832
  • 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

Running perl from skill and getting output one at a time

Pawandeep
Pawandeep over 13 years ago

Hi

I would like to run a perl program from my Allegro PCB Skill code.

I have skill code like below
procedure(test()
        cid=ipcBeginProcess("perl C:/test.pl")
        ipcReadProcess(cid 5)
)

The perl program(test.pl) is reading data/values from text files containing multiple lines and printing out values using foreach loop(till EOF)

I would like to have some kind of blocking method to pass the values to skill code one at a time(and then returning to perl to run next) so as to manupulate in skill.

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

    You could just use parseString() on the result of ipcReadProcess - e.g. parseString(ipcReadProcess(cid 5) "\n") to split the strings on the carriage return. Other than that you'll have to create some kind of handshaking protocol between the two - and make sure you flush the output in perl after writing each line. By handshaking I mean you'd have to read a line in SKILL, and then send a message back using ipcWriteProcess, and have your perl script wait until it gets the message back before writing the next string. 

    It's not that clear what you really want to do here or why it needs to do this one at a time. In fact if you only want to read the file and print it out, just doing printf("%s" ipcReadProcess(cid 5)) would be sufficient. So you could do:

    procedure(test()
      cid=ipcBeginProcess("perl C:/test.pl")
      ipcWaitForProcess(cid)
      while(ipcIsAliveProcess(cid)
        printf("%s" ipcReadProcess(cid 5))
      )
    )

    BTW - not sure why you posted this in the Custom IC SKILL forum if  you're using Allegro SKILL - there's a PCB SKILL forum which would be more appropriate. However, the code above should work in both Virtuoso and Allegro environments, I believe.

    Regards,

    Andrew.

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

    You could just use parseString() on the result of ipcReadProcess - e.g. parseString(ipcReadProcess(cid 5) "\n") to split the strings on the carriage return. Other than that you'll have to create some kind of handshaking protocol between the two - and make sure you flush the output in perl after writing each line. By handshaking I mean you'd have to read a line in SKILL, and then send a message back using ipcWriteProcess, and have your perl script wait until it gets the message back before writing the next string. 

    It's not that clear what you really want to do here or why it needs to do this one at a time. In fact if you only want to read the file and print it out, just doing printf("%s" ipcReadProcess(cid 5)) would be sufficient. So you could do:

    procedure(test()
      cid=ipcBeginProcess("perl C:/test.pl")
      ipcWaitForProcess(cid)
      while(ipcIsAliveProcess(cid)
        printf("%s" ipcReadProcess(cid 5))
      )
    )

    BTW - not sure why you posted this in the Custom IC SKILL forum if  you're using Allegro SKILL - there's a PCB SKILL forum which would be more appropriate. However, the code above should work in both Virtuoso and Allegro environments, I believe.

    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