Stats

  • Locked Locked
  • Replies 29
  • Subscribers 153
  • Views 31798
  • 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

Text editor or framework for SKILL...

ToMWUT
Hello All,

I've got some general questions about tools which could be used to write programs in SKILL. First of all could you recommend some text editor which highlights the SKILL syntax. Right now my main problems concerns syntax errors based on the problem that I'm for example passing wrong argument types to my procedures... Is there maybe a tool which could help me with this problem in SKILL, such as for example Eclipse for J2EE or Visual Studio for .Net? If not – even some text editor with the right syntax highlight for SKILL will be sufficient.

Thanks,

ToM
Parents
  • dmay

    I use NEdit which has syntax highlighting and the ability to setup calltips and tags (ctags) files. You can find a Skill syntax highlighting setup file on the web. If you are not familiar with tags and calltips, here is what they do and how we use them.

    Tags or ctags files are essentially index files that list the names of functions and the corresponding file where these functions can be found. You can get more details by doing a man on ctags in Unix or reading about them in the NEdit documentation. We have a cronjob that builds a tags file for all of our Skill code and we load the tags file when we start NEdit. When we come across a function call in some code, we can highlight the function name and run the "Find Definition" command from the NEdit menus or a bindkey and it will either jump within your code to the function definition, or open a separate file containing the function and jump to the definition. Very handy. We even make it work with Cadence functions by jumping to the entry in the skill finder reference file.

    Sample tags entries:
    cad.tags:dbGetTrueOverlaps      /cad/ic/5141_500.4.66/doc/finder/SKILL/DFII_SKILL/skdfref.fnd   /^("dbGetTrueOverlaps"$/;"      r
    cad.tags:MTdbGetTrueOverlaps  /home/dmay/sw/df2/skill/db/MTdbTransform.il     /^procedure(MTdbGetTrueOverlaps($/;"    r

    Calltips are those pop-up bubbles that tell you what the arguments are for a function. In NEdit, these work off the tags file and when you show a calltip, it will use the tag to find the function and then display the first few lines of the function in the pop-up bubble.

    Derek

Reply
  • dmay

    I use NEdit which has syntax highlighting and the ability to setup calltips and tags (ctags) files. You can find a Skill syntax highlighting setup file on the web. If you are not familiar with tags and calltips, here is what they do and how we use them.

    Tags or ctags files are essentially index files that list the names of functions and the corresponding file where these functions can be found. You can get more details by doing a man on ctags in Unix or reading about them in the NEdit documentation. We have a cronjob that builds a tags file for all of our Skill code and we load the tags file when we start NEdit. When we come across a function call in some code, we can highlight the function name and run the "Find Definition" command from the NEdit menus or a bindkey and it will either jump within your code to the function definition, or open a separate file containing the function and jump to the definition. Very handy. We even make it work with Cadence functions by jumping to the entry in the skill finder reference file.

    Sample tags entries:
    cad.tags:dbGetTrueOverlaps      /cad/ic/5141_500.4.66/doc/finder/SKILL/DFII_SKILL/skdfref.fnd   /^("dbGetTrueOverlaps"$/;"      r
    cad.tags:MTdbGetTrueOverlaps  /home/dmay/sw/df2/skill/db/MTdbTransform.il     /^procedure(MTdbGetTrueOverlaps($/;"    r

    Calltips are those pop-up bubbles that tell you what the arguments are for a function. In NEdit, these work off the tags file and when you show a calltip, it will use the tag to find the function and then display the first few lines of the function in the pop-up bubble.

    Derek

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.