On investigation the Clipper BEGIN SEQUENCE ... END structure seems to
act like a VFP TRY ... CATCH ... FINALLY ... ENDTRY, would that be
right?
So maybe:
Try
Do While .t.
* -- Some code.
If !whatever
Do While whatever
If !fnc1() Or whatever
* -- Exit jumps to the EndTry statement.
Exit
EndIf
EndDo
Endif
Catch to loException
*-- Handle the exception if you want.
EndTry
Function Fnc1()
Local llRet
llRet = iif(something, .t., .f.)
Return llRet
On Thu, 18 Mar 2010 09:33 +0000, "Tormey"
<[email protected]> wrote:
> BEGIN SEQUENCE - END SEQUENCE IN CLIPPER PROVIDES AN ABSOLUTE LOOP EXIT
> AS IN
> BEGSEQ
> DO WHILE .T.
> IF .NOT. WHATEVER
> DO WHILE WHATEVER
> IF .NOT. CALL FNC1() .OR. WHATEVER
> EXIT
> ENDIF
> ENDDO
> WHATEVER
> MORE CONDITIONAL EXITS AND BREAKS
> ENDDO
> ENDSEQ
>
> FUNCTION FNC1()
> CONDITIONAL
> BREAK
> END CONDITIONAL
> RET .T.
> ENDFNC
>
> A DO WHILE IN CLIP AND FOX GET YOU ONLY TO ITS OWN ENDDO, BUT THE BREAK
> CARRIES YOU TO ITS END SEQ NO MATTER WHAT. SUPER FOR DEEPLY NESTED STUFF
> WE USE FOR PROCESS CONTROL.
>
> PLEASE HOW DOES FOX DO THIS. MY SOLUTIONS ARE NOT ELEGANT AND THEREFORE
> ERROR PRONE.
> SEPAPHORES: - MESSY
> LOOP AND SEMAPHORES:- NOT NICE EITHER
> GOTO:- HEAVEN AND FOX FORBID
> CALL TO C: WOULD BE NICE WE HAVE USED CLIPPER -C EXTENSIVELY, BUT THAT
> ROUTE IS IN FOX EITHER.
>
> IF NOT FOX OR CLIPPER WHAT HOPE IT THERE ???
> WILLIAM TORMEY.
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
