hi, > > So how is that different from: > > > > do BLOCK1 until do BLOCK2 > > It's the same. > But the real fun starts when blocks and functions can suspend and > resume. > > { ... > # Return value and suspend. > suspend $i; > # Next iteration will resume here > ... > } andthen { ... }; > > -- Johan ]- <BIG GREEN> .... hmmmmm.... I will say wrong point of view. Why ? You are looking at this code at "Procedure semantic side" of view. Let'see how this look to me... "declarative guy" :") "Suspend" works for me like "INBLOCK CUT". I will ask what will happen in recursive block if you place the "end conditions" before suspend :") ===== iVAN [EMAIL PROTECTED] =====
- Re: RFC 104 (v1) Backtracking Jonathan Scott Duff
- Re: RFC 104 (v1) Backtracking Damian Conway
- Re: RFC 104 (v1) Backtracking Jonathan Scott Duff
- Re: RFC 104 (v1) Backtracking raptor
- Re: RFC 104 (v1) Backtracking Jeremy Howard
- Re: RFC 104 (v1) Backtracking Jonathan Scott Duff
- Re: RFC 104 (v1) Backtracking:example raptor
- Re: RFC 104 (v1) Backtracking Johan Vromans
- Re: RFC 104 (v1) Backtracking Jeremy Howard
- Re: RFC 104 (v1) Backtracking John Porter
- Re: RFC 104 (v1) Backtracking :ref raptor
- Re: RFC 104 (v1) Backtracking John Porter
- Re: RFC 104 (v1) Backtracking Nathan Torkington
- Component wise || and RFC 82 (was Re: RFC 104 (v1... Jeremy Howard
- Re: Component wise || and RFC 82 (was Re: RFC... Nathan Torkington
- Re: Component wise || and RFC 82 (was Re:... Damien Neil
- Re: RFC 104 (v1) Backtracking Mark Cogan
- Re: RFC 104 (v1) Backtracking Jeremy Howard
- Re: RFC 104 (v1) Backtracking Mark Cogan
- Re: RFC 104 (v1) Backtracking Chaim Frenkel