2022-7-9 0:49 Paul "LeoNerd" Evans <leonerd@leonerd.org.uk> wrote: > On Fri, 10 Jun 2022 18:43:02 +0100 > "Paul \"LeoNerd\" Evans" <leonerd@leonerd.org.uk> wrote: > > > On Fri, 21 Jan 2022 15:05:23 +0000 > > "Paul \"LeoNerd\" Evans" <leonerd@leonerd.org.uk> wrote: > > > > > This seems like a fine idea and nobody's objected to it yet. > > > > > > Can you please write it up as a formal RFC on the usual process: > > > > > > https://github.com/Perl/RFCs/ > > > > > > We have allocated the number 0014 for it. > > > > Hi Dan, > > > > A nudge to say we're out of the "5.36 release quiet time" now, so this > > would be a good time to begin looking into this. > > > > Would you be able to write it up? > > Hi all, > > This has sat pending for a number of weeks now. We still think it's a > good idea, but someone still has to write it up as a real RFC. > > A general request, to whomever is interested in having this as a > feature, to have a go at writing this up. If it's still sitting after a > few more weeks we'll call it "Parked" and stop considering it. > > I'm interested in this topic. I have questions. 1. Can this be resolved in tokenizer? This means ${^INPUT_LINE_NUMBER} is replaced with $. in toke.c. 2. Is the brace required? Is $^INPUT_LINE_NUMBER allowed? 3. Can only the aliases that are often used be added? For example, in my experience. I use $., $/, $$, $@, $!, $<, $> etc. If 1 and 3 are ok, I can write RFC.Thread Previous | Thread Next