Perhaps. But this thread evolved into a "best practices" discussion. That is a
wide gamut which conceivably extends down to Rexx coding suggestions.
For example, my PROFILE XEDIT checked the first line of the file and if it found
a lower-case character, it 'SET CASE MIXED RESPECT', otherwise it accepted the
XEDIT default (from memory, apologies in advance for flaws):
Address XEDIT
...
'COMMAND EXTRACT /CASE'
caseopts = case.1 case.2
lc = 'abcdefghijklmnopqrstuvwxyz'
'COMMAND LOCATE :1 EXTRACT /CURLINE'
If Verify(curline.3, lc, 'Match', 1) > 0 Then caseopts = 'MIXED RESPECT'
...
'COMMAND SET CASE' caseopts /* In an alphabetical list of SET cmds */
...
It was sort of an inadvertent echo of the UNIX shebang line, which itself
(inadvertently?) mimicked the CMS EXEC interpreter discriminator.
-Chip-
On 1/29/10 04:25 P S said:
On Thu, Jan 28, 2010 at 10:55 PM, Les Koehler <vmr...@tampabay.rr.com
<mailto:vmr...@tampabay.rr.com>> wrote:
Using WORDPOS() would be a *lot* more efficient and easier to type!
And so the wars resume...
