Allison Randal wrote: > Garrett Goebel wrote: > > > > I guess the next question in the context of the following is: > > > > Larry Wall wrote in Apocalypse 4: > > > > > > It should be possible to make user-extensible syntax look > > > just like built-in syntax. > > > > How would I create a user-extensible construct that works > > like given/when? I'm guessing the answer is: you don't. > > I sure hope you can. I intend to use it.
Hmm... Out of curiosity what kind of user-extensible topicalizer aware constructs would you make? And thinking of this in the context of user defined functions, am I correct in assuming that we would need to be able to specify per-parameter topicalizer awareness? So this would impact whatever replaces function prototypes? If topicalizers aren't going to be limited to given/when, but may slowly creep in wholesale, then I have a few more questions... Larry Wall in Apocalypse 4 writes: > A when is the only defaulting construct that pays attention > to the current topicalizer regardless of which variable it > is associated with. Which is fine when there's only one topicalizer. But is the C<when> EXPR's current topicalizer awareness limited to the current C<given> scope? Or the scope of any topicalizer which might be later introduced? I.e., will we be able to specify which topicalizers a topicalizee pays attention to? Or will all topicalizees be aware of all topicalizers?
