Re: converting perl stuff to v5.36

2023-05-09 Thread Marc Espie
On Mon, May 08, 2023 at 01:23:25AM -0400, George Koehler wrote: > On Sun, 7 May 2023 19:21:11 -0700 > Philip Guenther wrote: > > > On Sun, May 7, 2023 at 6:13 AM Marc Espie > > wrote: > > > > > I'm actually wondering whether keeping the prototype is worth it. > > ... > > For plain subs, I would

Re: converting perl stuff to v5.36

2023-05-09 Thread Marc Espie
On Sun, May 07, 2023 at 07:21:11PM -0700, Philip Guenther wrote: > Yeah, the downside of signatures is that by default it makes adding > parameters a breaking change and can thus calcify the interface. Something > for authors of shared modules that have callbacks to carefully consider. :/ So far

Re: converting perl stuff to v5.36

2023-05-07 Thread George Koehler
On Sun, 7 May 2023 19:21:11 -0700 Philip Guenther wrote: > On Sun, May 7, 2023 at 6:13 AM Marc Espie > wrote: > > > I'm actually wondering whether keeping the prototype is worth it. > ... > For plain subs, I would only keep them if they _really_ help the calls look > for more perl-ish, by whate

Re: converting perl stuff to v5.36

2023-05-07 Thread Philip Guenther
On Sun, May 7, 2023 at 6:13 AM Marc Espie wrote: > It is generally a good thing, I'm mostly talking about > the "signatures" stuff that allows functions with stuff that looks like > usual languages. > Other benefits include somewhat "cheap" check for correct number of > parameters > and generally

converting perl stuff to v5.36

2023-05-07 Thread Marc Espie
It is generally a good thing, I'm mostly talking about the "signatures" stuff that allows functions with stuff that looks like usual languages. Other benefits include somewhat "cheap" check for correct number of parameters and generally making code shorter. Basically this converts very perlish cod