Re: bleadperl v5.13.2-282-g57b20d1 spits zillions of warnings

On Sun, Jul 18, 2010 at 06:22:53PM +0100, Dave Mitchell wrote:
> On Sun, Jul 18, 2010 at 12:44:22PM -0400, David Golden wrote:> > On Sun, Jul 18, 2010 at 11:28 AM, Nicholas Clark <n...@ccl4.org> wrote:> > > On Sun, Jul 18, 2010 at 04:15:12PM +0200, Rafael Garcia-Suarez wrote:> > >> On 18 July 2010 15:59, Dave Mitchell <dav...@iabyn.com> wrote:> > >> > I'm strongly tempted to take Nicholas's approach of making assignment to> > >> > CvGV a compile-time error and provide a separate CvGV_set() macro. This will> > >> > have the effect of unambiguously breaking Sub::Name and everything that> > >> > depends on it (rather than just appearing to work while possibly doing the> > >> > wrong thing). Thus everything will get broken until a fixed Sub::Name is> > >> > released.> > >>> > >> I think that this is a very good idea.> > >> > > It looks like the only way to ensure sanity.> > > > I'll flag it in the "Known Issues" for v5.13.3.> > Give me another 15 minutes and I'll should be able to push commits that> make using CvGV as an lvalue a compile-time error;

Now pushed as

    b3f91e9158d8a5c05627eba1c2848f35528571d2

along with a couple of other tweaks to the new CvGV code:

    c794ca97ff43be078aabf556aa282af208d9c38c
    cfc1e951d98ba2b9a0e066aba9aadba4cd919eec

Togther with a fix I have for Sub::Name (shortly to be forwarded to its
author), all the noisy/failing modules described earlier now pass.

-- 
You're only as old as you look.