×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 24 Jul 2013 10:32, rob@xxxxxxxxx wrote:
<<SNIP>> I don't know if I've ever seen it standalone in production.
Why would one? Especially since it doesn't support LEAVE or ITER.
A standalone Do-group normally would appear in an EXEC() of MONMSG, a
THEN() of the IF or WHEN, the CMD() of ELSE or OTHERWISE. However the
non-iterative Do-groups are not prohibited inline elsewhere, and the
primary use is probably always stylistic. That is the primary reason I
have used them [often with a LABEL on the DO], and probably the only
time they would remain in the effective /production/ version. Although
I have also used them occasionally for an emphasized grouping of code,
mostly due to a suspicion that those lines of code might become [or
ughh, even copied to become] embedded within an IF, SELECT, or MONMSG,
or to be redefined within a subroutine defined by SUBR for a CALLSUBR.
But mostly only temporarily remaining a DO, merely pending the eventual
change to become a DOWHILE, DOFOR, or DOUNTIL, after the successive
statements have been tested\validated for the once-through effect while
it remained just DO\ENDDO vs an iterative Do-group.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
