develooper Front page | perl.perl5.porters | Postings from December 2017

Re: Urgent subroutine signatures problems

Thread Previous | Thread Next
From:
Eirik Berg Hanssen
Date:
December 24, 2017 19:22
Subject:
Re: Urgent subroutine signatures problems
Message ID:
CAHAeAG6-3j1tzKUsoAvHnV5GOrPoW1tm1BG=iJoK0gm4S-e-7Q@mail.gmail.com
On Sun, Dec 24, 2017 at 7:04 PM, Sawyer X <xsawyerx@gmail.com> wrote:

>
> On 12/23/2017 08:23 PM, Eirik Berg Hanssen wrote:
> > On Sat, Dec 23, 2017 at 5:38 PM, Sawyer X <xsawyerx@gmail.com
> > <mailto:xsawyerx@gmail.com>> wrote:
> >
> >
> >     We can document that every compilation-affecting subroutine attribute
> >     should be used before. Another way is to add a mechanism to
> >     register an
> >     attribute as "requiring compilation," allowing us to croak about
> >     them if
> >     we see them after signatures. Not an optimal solution, to say the
> >     least.
> >
> >
> >   If you're really considering this, please go the other way: Require
> > such registration of the attribute before allowing it after the
> signature.
>
> Wouldn't it depend on how likely attributes are to affect or not affect
> compilation?
>

  Does it matter if there's a 10% or a 90% chance of messing up an
unregistered attribute, when the alternative is not messing it up?


Eirik

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About