|
On Feb 5, 2018, at 10:57 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
John Erps,
I didn't say never use a subroutine. I said that I personally went
hardcore on only using subprocedures for a year. And stated my reason.
You can see that below in the thread. Once I broke the habit of falling
back to what was easy and comfortable I used subroutines where
appropriate. I really thought I was quite clear on that.
One thing to keep in mind is to always think of the future.
What may be a subroutine in an existing program could evolve.
- First into a subprocedure
- Next moved out of the main program into a service program.
- Then someone could create a UDF from that service program subprocedure
- That UDF could be called by SQL with stuff like Select item_number,
onhand(item_number)...
- That UDF could be imbedded into an SQL view Create view Item_user as
(select item_number, onhand(item_number)...
and thus making user queries easier.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: john erps <jacobus.erps@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/05/2018 10:31 AM
Subject: Re: What is a Modern RPG Programmer???
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I don't see any reason why you would not want to use subroutines, and only
procedures.
Like Justin said, subroutines still have their use sometimes, within a
procedure.
It sometimes seems to me that for the ones wanting to be a "modern" RPG
programmer everything that relates to "old" RPG is bad (like RLA) and
everything else (coming from open source world e.g.) is good.
This is dogmatic thinking.
Just use what works well in you situation, as long as the code is clear,
maintanable etc etc.
Sometime ago there was a discussion about how to represent some data in an
RPG program.
RPG supports that you can put data at the end of an RPG program after **.
This is old school RPG but sometimes still handy to easily and clearly
define some data.
In that discussion the use of ** was dismissed, just for the reason that
it's old school RPG and thus shouldn't be used anymore.
But the alternative, using datastructs / constants was more convoluted,
and
using ** would have been more clear.
On Mon, Feb 5, 2018 at 3:27 PM, Rob Berendt <rob@xxxxxxxxx> wrote:
Subroutines may still have their place but I went hardcore for over ayear
and used subprocedures only. Even for the littlest of things. Just toand/or
ensure that I wasn't using a subroutine instead of a subprocedure as a
fall back to something "easier" and more comfortable.
Sometimes it takes this kind of discipline. Like disconnecting your
external keyboard and mouse from your laptop and storing them away from
the laptop to force yourself to become adept with the mouse pointer
pad to see if, after the curve to train your fingers, you really dobecome
more productive. I sure have.list
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/05/2018 09:23 AM
Subject: RE: What is a Modern RPG Programmer???
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Off-the-cuff...
Free format C-specs are mandatory. **free would be a plus.
Prefer SQL but RLA does have its uses.
Procedures instead of subroutines.
I'm not sure 5250 programming can be considered "modern".
-----Original Message-----
From: Thomas Burrows [mailto:thomas.burrows.1957@xxxxxxxxx]
Sent: Saturday, February 03, 2018 1:08 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: What is a Modern RPG Programmer???
Been asked to show how I am programming as a MODERN RPG PROGRAMMER.
Would it be using completely FREE FORMAT from F specs to C specs.
Embedded SQL that is just dropped in the code.
No /Free statements.
Would like the groups thoughts.
Thomas Burrows
cell 469 693 2533
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
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.