Stats

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

Using toplevel('ils) in an ocean script causes undefined variable errors

MatthewLove

I'm trying to run a load pull test using Ocean. If I set the toplevel environment to Scheme mode (ils), the script generated by ADE breaks due to scoping errors. Is there any way around this?

This is valid ocean code.

    constantPowerContours = cPwrContour(...)
    plot( constantPowerContours ?expr '( "Constant Power Contours" ) )

while this code breaks

    toplevel('ils)

    ...

    constantPowerContours = cPwrContour(...)
    plot( constantPowerContours ?expr '( "Constant Power Contours" ) )

and gives the following error on IC 6.1.6

    *Error* eval: unbound variable - myVar1

Any ideas?

  • This is because plot() in IC616 is a macro which internally calls eval (for strange historical reasons). Unfortunately because of that, it's trying to evaluate the variable in the SKILL top-level (not SKILL++/Scheme top-level). 

    You'd have to surround the plot with a call to inSkill() - however, then your variable lookup wouldn't work. 

    I'd say it's best not to use Scheme mode (ils mode) in an OCEAN script. Either way, you shouldn't really use toplevel('ils) in a script anyway - you either should give the file the ".ils" suffix, or wrap with inScheme(). You could always wrap the bits you want to be evaluated in Scheme mode that way.

    Note that in IC617, plot() is now a normal function and this no longer seems to be a problem.

    Regards,

    Andrew.

  • Thanks for the explanation.

    I'd say it's best not to use Scheme mode (ils mode) in an OCEAN script. Either way, you shouldn't really use toplevel('ils) in a script anyway - you either should give the file the ".ils" suffix, or wrap with inScheme(). You could always wrap the bits you want to be evaluated in Scheme mode that way.

    That's fair enough. I'll avoid using SKILL++ internally within ocean scripts then.

    Can you give an ocean script the suffix .ils and it'll still run ok then?

    Is the .ocn identifier more for humans than for Virtuoso?

  • Matthew,

    The only suffix (for SKILL/OCEAN files) that makes a difference is ".ils" - that causes the file to be treated with Scheme/SKILL++ semantics. Anything else is in SKILL language mode. So yes, the ".ocn" suffix is for human consumption (as is the .il suffix, in fact).

    I think you'll have the same problem with plot if you use the .ils suffix too (at least in IC616 and before) - the macro would need to call eval(... theEnvironment()) for it to work in both language modes - this is assuming there aren't any other things that needed fixing.

    Regards,

    Andrew.

  • Ah, that's pretty interesting. I'll isolate all my SKILL++ code in .ils files then, thanks again.

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.