On Wednesday, March 30, 2016 at 1:45:09 PM UTC-7, Robby Findler wrote: > Perhaps we should improve the syntax-parse documentation? I found the > overview and examples to be pretty good, tho. > > Robby > > > On Wed, Mar 30, 2016 at 3:42 PM, Neil Van Dyke <[email protected]> wrote: > > Oops, I usually end up typing one of the names wrong. Summary: > > > > * syntax-case -- good one to start with, smooth path to syntax-parse > > > > * syntax-parse -- best thing ever, but documentation is intimidating, so > > maybe start with syntax-case instead > > > > * syntax-rules -- old, limited, no smooth path, you probably don't want to > > ever use this, though you'll occasionally you'll see an old-timer use it > > when they're in a hurry > > > > > > Neil V. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Racket Users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/d/optout.
Thank you for the feedback. Indeed I am not using macros just for learning them but for generating code that I will run later. The example I gave here was a toy one. However, my problem is still not resolved because in all the suggestions above, I still need to explicitly pass all the arguments to mysyn such as: (mysyn 1 2 3). Is there a way to pass a list l by its name and not its values. For instance, If l is '(1 2 3) I want to be able to call the macro as (mysyn l) and not (mysyn 1 2 3). Is this possible? -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
