Front page | perl.perl5.porters |
Postings from May 2015
C<bless $x, undef> produces two warnings if used. It is not documented in perlfunc (the single-arg case is, but not an explicit undef). To me, that suggests that the current behaviour is an implementation accident rather than a settled part of the language. The consensus seems to have converged on adding 'unbless' for other reasons, which is fine by me. If you think that C<bless $x, undef> is truly part of the language and should stay with its current semantics, I suggest documenting it in perlfunc and removing the two warnings which it currently produces. -- Ed Avis <eda@waniasset.com>Thread Previous | Thread Next