On Fri, Apr 13, 2001 at 06:24:24AM -0700, Randal L. Schwartz wrote: > Michael> Why? What do you use it for? > > Is that the appropriate question? Yes. Any feature which mucks up control flow this badly has to defend itself. > If it's not keeping you from writing code, and there's little or no > support cost to keeping it working, then it doesn't need to be > deprecated in Perl5. It is keeping me from *re*writing code. Its keeping me from being able to lexically scan a piece of old Perl code (by eye or by program), having a good idea what it does, and being able to rewrite it with a fair amount of assurance that it doesn't have nasty side effects. Of course, I'm not going to lock myself up in my bedroom and hide under the covers keeping all digital equipment outside a 500 foot exclusion zone because of this. Its just very, very, very disquieting. > After all, it's been around since Perl1 (or Perl2?). Warn yes. > Change no. Somebody might still be counting on it working. What > good does it do to break that? Oh, sorry, misunderstanding (or perhaps overzealousness on my part). A deprecation will do. I have this tendency to see something bad and immediately say KILL IT! KILL IT, ITS EVIL! -- Michael G. Schwern <schwern@pobox.com> http://www.pobox.com/~schwern/ Perl6 Quality Assurance <perl-qa@perl.org> Kwalitee Is Job One <GuRuThuG> make a channel called #Perl, and infest it with joking and fun.... it doesnt make alot of sense. ==== Want to unsubscribe from Fun With Perl? Well, if you insist... ==== Send email to <fwp-request@technofile.org> with message _body_ ==== unsubscribe