Re: Code reuse - best practices

["Walcker, Paul" <pwalcker@ISD.SBCOUNTY.GOV>]

My biggest suggestion (that PeopleSoft is now starting to do) is pass all
data via parameters to the procedure.  I've clobbered a few chunks of data
by using a variable that PeopleSoft decided to use in one of their
subroutines.

Another complaint that I have about the PeopleSoft sqc's is their naming
convention.  We have a naming convention in our programs to help identify
the function happening in a paragraph.  For example,
A**** are main loop paragraphs
P**** are initialization paragraphs
Q**** are termination paragraphs
etc.

It would be nice if PeopleSoft had prefaced paragraph names in their SQC's
with something that identified which SQC it came from.  So instead of using
Rotate-Name you would have something like Rot3-Rotate-Name.  This would make
it a little easier to track back to where the function exists.

Paul

-----Original Message-----
From: Bergeron, Hugo [mailto:Hugo.Bergeron@MICROCELL.CA]
Sent: Monday, September 16, 2002 1:02 PM
To: SQR-USERS@list.iex.net
Subject: Code reuse - best practices


Hello SQR users of the world,

I work with 10 or so programmers and analysts who use SQR's with PeopleSoft
and I would like to improve code reuse within the team. I would appreciate
if the SQRUG could share advices on setting up the right kind of standards
and environment to improve code reuse. My first idea was to go over our
current SQC's (PeopleSoft and custom) and document the procedures in a
public file that members of the team could refer to and maintain. I'm
thinking that in the best case scenario, a script could even scan the SQC's
and update such a file, that is if everybody would follow standards in
describing the procedures in the SQC's.

Another thing, what about sqc vs sqh? I've never seen a sqh, but I see it as
the naming standard on ontko.com. Is sqc the standard for PeopleSoft
delivered programs?

I was wondering if some of you had experiences to share, success stories or
pathetic failures, on that topic?

TIA.

Hugo.