Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13106
  • 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

Can macros be lexically-bound?

tweeks

When I try to defmacro within a let, I get a warning:

*WARNING* (def): treated as top-level definition - localMacro

and the macro is bound at the top-level. Is there any way to hide a macro definition?

I thought about using namespaces, but I don't want all the identifiers in my code looking like:::this. Also, you can only import names into the toplevel namespace! Yes, you can un-import them when done, but this implies you need an unwind-protect to make sure the unuseNamespace() happens if there's an error, and I doubt it even works with SKILL++ environments anyway....

On a related subject: are syntax transformers created by define_syntax always global?

Parents
  • Andrew Beckett

    Tom,

    No - there is an enhancement CCR, 813051, asking for an implementation of macrolet in SKILL. You should contact customer support and request an enhancement (which can be duplicated with that CCR) since currently the only requester is internal.

    I suspect that define_syntax (which is private as I've pointed out before) is also not using lexical scoping (I didn't check, since it's private and there are already some limitations, as has been discussed before). It's only really used by SKILL Lint at the moment.

    Andrew.

Reply
  • Andrew Beckett

    Tom,

    No - there is an enhancement CCR, 813051, asking for an implementation of macrolet in SKILL. You should contact customer support and request an enhancement (which can be duplicated with that CCR) since currently the only requester is internal.

    I suspect that define_syntax (which is private as I've pointed out before) is also not using lexical scoping (I didn't check, since it's private and there are already some limitations, as has been discussed before). It's only really used by SKILL Lint at the moment.

    Andrew.

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.