"It depends." 8-)
In WORDPOS I would it expect it to be fussy, since it is indeed a
specific character string you are looking for. With DATE I would expect
it to be more concerned with the format of the date vs case of the
month. I'm not advocating that DATE('B', . . .) be changed to accept any
case. However what I would suggest that either the doc be changed to
inform the user of the month spelling requirement OR the DATE('B', . .
.) function be changed to disregard case.
Respectfully, let me know what the rules are and I'll play by them.
(or if I choose to ignore them I'll accept the consequences).
But, if we want to play CalvinBall then let me know that too. 8-)
(I like "opposite day" the "least".)
Steve
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Chip Davis
Sent: Wednesday, November 19, 2008 5:36 PM
To: [email protected]
Subject: Re: REXX DATE function
One man's "fussy" is another man's "rigorous" or "consistent" ... :-)
It was designed that way because the default output format returns the
month in
mixed case. It was felt that reciprocality demanded that the Date() BIF
accept a
date in the same form that it returned it, as long as it was unambiguous
or, in
the case of 2-digit years, windowable. Once you open the door to
variants,
things get messy, e.g. should "12Oct2008" be allowed?
Remember, Rexx is case-sensitive when it regards data; it is
case-insensitive
only when it comes to how the Rexx code itself is written.
Would you expect that "WordPos('OCT','Jul Aug Sep Oct Nov Dec')" would
return a
"4" or a "0"?
-Chip Davis-
[EMAIL PROTECTED]
On 11/19/08 00:33 Mark Wheeler said:
> The IBM z/VM Operating System <[email protected]> wrote on
11/18/2008
> 03:33:48 PM:
>
>> I am trying to run the following code:
>> <code>
>>
>> /* */
>> date1='12 OCT 2008'
> date1='12 Oct 2008'
>> date2='13 OCT 2008'
> date2='13 Oct 2008'
>
> Fussy, no?
