On Thu, Dec 9, 2021 at 4:57 PM Dan Book <grinnz@gmail.com> wrote: > On Thu, Dec 9, 2021 at 3:49 PM Paul "LeoNerd" Evans < > leonerd@leonerd.org.uk> wrote: > >> On Thu, 09 Dec 2021 21:45:13 +0100 >> Tomasz Konojacki <me@xenu.pl> wrote: >> >> > On Thu, 9 Dec 2021 20:32:10 +0000 >> > Dave Mitchell <davem@iabyn.com> wrote: >> > >> > > So by your logic, we're not allowed to change the behaviour of @_ in >> > > signature subs (the main thrust of this thread)? >> > >> > As I said in the "getting signatures out of experimental" thread, I'm >> > OK with @_ removal because I don't consider it a dramatic change. >> > Overwhelming majority of signatured subs don't use @_ and those that >> > do can be modified to stop using it. >> > Oops, cut out too much, this was supposed to be a response to this statement from Paul: > Having read the prior arguments, I'm kinda with Dave on this one. > @DB::args is already shockingly broken in a lot of ways. Making it > always appear empty when called within a signatured sub is, honestly, > not the worst of its already-current breakages. This isn't going to be much consolation to users who are currently relying on it and have not experienced the bugs. -DanThread Previous | Thread Next