use Perl

Hi Salva, I assume your post was to me, it made me look at SO4 abouth phasers WOW that's a lot. I done it again, talk/write first without thinking. My construct were more of documentary purpose and to tie code together. And since I did it mostly for myself I didn't have to take care of every edge case e.g. when an empty loop mattered I did the check in the 'phasers'. As for setting LAST just be one step ahead, it's not a big deal for finit resources. I had good use for my construct, but that was not even a pee in the pond compared with Perl6 phasers. Next time I have opinions about Perl6 I read the specs first. P.S. I have followed Perl6 development for the last 3-4 years and I'm VERY impressed with what you are creating. I hope to get some time to late this year to attempt to do something serious in Perl6.

Hi Carl, I do not know if this is the right forum for this. I like the phasers, they are really programmer friendly as many other novel Perl6 constructs. But I find the name of the phasers a bit missleading. FIRST and LAST are executed BEFORE and AFTER the first resp last iteration of the loop and is not directly associated with the logic of a loop iteration. Long time ago (in 360 assembler macros) I did similar loop constructs and used the words INITIALIZE, TERMINATE and NEXT and used Booleans FIRST and LAST flagging the first and last iteration in a loop. I always exceuted my INITIALIZE and TERMINATE routines nomatter if the loop was executed or not.

Hi, I found this sentence at page 19. One access to many? Sometimes you don't want to access access an array or hash as a whole, but rather extract some of the values.