• Subject: Re: last day of month
  • From: Mark Lazarus <mlazarus@xxxxxxxx>
  • Date: Mon, 18 Oct 1999 21:05:38

Peter,

At 11:43 PM 10/17/99 -0700, you wrote:
>> > SetDate(Datefield:*D:01)
>> > SetDate(Datefield:*M:12)
>> > SetDate(Datefield:*Y:2001)
>>
>>  I like this suggestion.  It says exactly what you'd like to do.  I would
>> also hope that we could combine descriptors, i.e. *MD, *MY, *DY, etc.
>> Also, *Y and *YY or *CY.   *JD would be Julian days.
>>
>>  -mark
>
>After reading your suggestion Mark, it occurred to me that ILE RPG already
>has the op code and the syntax, just not the specific descriptors. Consider
>this example from the manual:
>
>    C     *DMY          MOVE      210991        DATE_ISO
>    C     *DMY          MOVE      NUM_DATE1     DATE_ISO
>
>Now just allow some more descriptors and you could have
>
>    C      *D               MOVE      01                 datefield
>    C      *M               MOVE      12                 datefield
>    C      *Y                MOVE      2001            datefield
>
>It's in keeping with what IBM has already done and seems just as
>understandable as the others, especially if you've already learned to use
>MOVE for date, time & timestamp fields.

 I agree to a point - the functionality is there.  But since RPG seems to
be going in the direction of BIFs and free-form, SETDATE would fit that
model better.

 -mark

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].