|
many sub procedures with few lines of code in them. I think it's because theI would agree, but I've recently been pulled up a manager for having too
--
On 2012-06-13, at 8:50 AM, Barbara Morris wrote:
I'm a fan of using work variables and extra statements to simplify code.
This is one of those occasions where I'd be tempted to do a variation
of the "old" approach and probably bury it in a subproc. I love the
date functions but speed wise this is going to win every time.
D DS
D MyNewDateField...
D d DatFmt(*USA)
D Month 2s 0 Overlay(MyNewDateField)
D 1a Overlay(MyNewDateField: *next)
D Day 2s 0 Overlay(MyNewDateField: *next)
/Free
If Day >= 16;
Day = 16;
Else;
Day = 1;
EndIf;
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.