On Monday, June 3, 2002, at 06:23 , Ron Powell wrote:
> Heya, > > I just read this article -- > http://use.perl.org/articles/02/06/01/1944202.shtml?tid=6 > <http://use.perl.org/articles/02/06/01/1944202.shtml?tid=6> > > Being very new to perl, I don't understand what impact most of these > changes > will have, first off I presume you noted the big caps: "WE DO NOT RECOMMEND USING RELEASE CANDIDATE 1 IN A PRODUCTION ENVIRONMENT. " this is a perlish way of noting 'we feel reasonably sure that we have most of the wackoPerlGeeks out of the 5.7.X world at this point' and hence that you can modestly consider it as a candidate for being your production grade perl code... I presume you also noted: "THIS IS A REAL NEW PERL RELEASE THAT IS BINARY INCOMPATIBLE WITH ANY PREVIOUS PERL RELEASE. THIS MEANS THAT YOUR OLD EXTENSIONS (.xs code, those Perl modules requiring a C compiler) WILL NOT WORK AND WILL HAVE TO BE RECOMPILED. (Pure Perl modules should continue working.)" which is a perlish way of noting - "you will most likely need to do a lot of work to upgrade here" > but I'm particularly interested in the addition of the SWITCH > statement. I presume you mean: cf: http://mirrors.kernel.org/cpan/doc/perldelta.pod and grovel down to 'use Switch' - depending upon your orthodoxy - you either consider leaving the 'branch tree' construction up to the compiler a good thing or merely laziness that allows the mediocre to write more banal code faster.... You may have noticed the recent 300 coin thread - where we have been discussing which is worse - writing a GaGillion lines of canonical if <COND> elsif<COND2> ....... else { die "bad voodo happened";} or would one be better off doing this with using the implicit branch structuring in a Hash - in part because of prior discussions about the merits of building 'branch tables' where we index into functions with something on the order of cf - http://www.wetware.com/drieux/pbl/misc/HashSwitch.txt That we have all been through the misadventures of play as noted in perldoc -q switch that they have opted to simply provide a mechanism for doing this means that it will be 'simpler' in the future to write banal code. > I thought it might be an interesting to discuss which feature(s) > the more advanced users are looking forward to, and what impact that will > have - sort of a learning experience I guess. all upgrades are evil, bad, wrong. True Believers can do perl golf in perl4.... The Apocalypse is Coming, this is a False Start and should not be supported. Do not bend, fold spindle or mutilate. > Anyways, have at it :) never put a challenge like that, "lead me not into temptation for surely I can find it on my own...." - oscar wilde but thank you for asking.... ciao drieux --- Remember boys and girls, the big advantage of having someone on staff who has been kissing wall sockets since their youth is that they are cheaper than owning a volt meter, and way techNoir if they can also tell 50Hz from 60Hz circuitry. The downside is that they are less suceptible to 'electro-shock' therapy, and you may have to find some other form of chemo-therapy to help them on the road to recovery.... -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
