Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 13535
  • 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

Syntax_rules in Skill++

MatthewLove

I read a forum post from a few years ago where a user mentioned that syntax_rules was partially implemented in Skill++. Just wondering if anyone knows if it's more stable these days and can be used?

It seems like a fairly core part of scheme so it's a bit odd to not include it.

Parents

  • Thanks Matthew. I made a mistake in my previous reply - it was IC617 that this was marked public (I think I misread 2015 as IC615 for some reason) - which is why you didn't find it in the docs.

    I see from your example why it's useful although personally I tend to avoid the extra syntactic keywords - although that does help with making the human comprehension of the new form clearer. I have historically used defmacro - but I can see how this could be useful. That said, I generally advise against overuse of macros. Peter Norvig makes a good point in Paradigms of Artificial Intelligence Programming about this: "The first step in writing a macro is to recognize that every time you write one, you are defining a new language that is just like Lisp except for your new macro. The programmer who thinks that way will rightfully be extremely frugal in defining macros. Introducing a macro puts much more memory strain on the reader of your program than does introducing a function, variable or data type, so it should not be taken lightly. Introduce macros only when there is a clear need, and when the macro fits in well with your existing system."

    Apologies to anyone who's seen me cite Peter Norvig before on this topic!

    Regards,

    Andrew.

Reply

  • Thanks Matthew. I made a mistake in my previous reply - it was IC617 that this was marked public (I think I misread 2015 as IC615 for some reason) - which is why you didn't find it in the docs.

    I see from your example why it's useful although personally I tend to avoid the extra syntactic keywords - although that does help with making the human comprehension of the new form clearer. I have historically used defmacro - but I can see how this could be useful. That said, I generally advise against overuse of macros. Peter Norvig makes a good point in Paradigms of Artificial Intelligence Programming about this: "The first step in writing a macro is to recognize that every time you write one, you are defining a new language that is just like Lisp except for your new macro. The programmer who thinks that way will rightfully be extremely frugal in defining macros. Introducing a macro puts much more memory strain on the reader of your program than does introducing a function, variable or data type, so it should not be taken lightly. Introduce macros only when there is a clear need, and when the macro fits in well with your existing system."

    Apologies to anyone who's seen me cite Peter Norvig before on this topic!

    Regards,

    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.