On Sun Nov 28 12:15:12 2010, sprout wrote: > On Sun Nov 21 22:25:19 2010, sprout wrote: > > On Sun Nov 21 18:50:56 2010, schmorp@schmorp.de wrote: > > > On Sun, Nov 21, 2010 at 06:38:20PM -0800, Father Chrysostomos via RT > > > <perlbug-followup@perl.org> wrote: > > > > Sorry, I was not clear enough. If tie $self is changed to tie *$self > > > and > > > > tied ${...} is changed to tied *{...}, it will work in blead and in > > > > older perls. > > > > > > > > The problem is that in older perls there is no way to see whether a > > > > scalar is tied if a glob has been assigned to it. I thought that was > > > a > > > > bug, so I ‘fixed’ it. > > > > > > > > I’m hoping you will consider it a bug, too. > > > > > > Well, whether that is a bug or not doesn't really have anything to do > > > with > > > the code, as the code doesn't rely on that bug directly. > > > > > > The important question for me would be how much code breaks, and > > > whether > > > this change in behaviour warrants a depreciation. > > > > > > Maybe I am a burned child, but it seems every major perl release > > > breaks > > > some of my modules (and often even when following documentation), so > > > I'd > > > appreciate if perl gave more choice and more (not longer) depreciation > > > periods. > > > > How about I revert it and add a ‘Use of tie on a handle without * is > > deprecated’ warning? > > How about this patch (plus a perldiag entry)? These three commits will > need to be reverted first: > > 830748013f81bcc28d145baf4024efd1b6537704 > 9aa8b00892d81bb5e94565d3cb9841dd57b7b9cf > 8752206e276cffe588c0932b5a9f2331640e8447 > > Since this is a run-time check, I could not make it warn once per op. So > it warns once per GV. Now done as: 84b9ac853508aaff52254b6cf2b95a2a6783ff00 7850f4d6b732ab5f426cd3bcd9757c70a46cfda1 b029825916bf29623e00b45fa4226fab0d52d217 6cd32d3b3481cbe3a38da6bbdf70e01ffe99d05a 7c7df8124bbdd7a0091f8ed82589548c8182f624 5609d5f90089ffe65a35ff268181e98d43914790Thread Previous | Thread Next