Re: Standards issue - Comments please.

["Bruce Vining" <bvining@xxxxxxxxxx>]

Depending on how one codes their O-specs, one drawback can be if your
company ever decides to support another language for the users (say for
instance you are currently using English and you now want to provide
Spanish for some users).  With O-specs (assuming hardcoded headings, etc.)
you get to hand over the RPG program (and associated logic) to the
translators; with *PRTFs you just hand over the print file (which is
generally a lot safer).  You also of course don't end up with two (or more
as the language base grows) copies of the RPG programs.

Bruce




                      "DeLong, Eric"
                      <EDeLong@Sallybea        To:       
"'rpg400-l@midrange.com'" <rpg400-l@midrange.com>
                      uty.com>                 cc:
                      Sent by:                 Subject:  Standards issue - 
Comments please.
                      rpg400-l-admin@mi
                      drange.com


                      01/03/2003 02:39
                      PM
                      Please respond to
                      rpg400-l






We will be having a review of shop standards soon, and I've been asked to
assemble a "pros and cons" list for the O-spec -vs- Prtf topic.  Our
current
standard recommends O-spec, but exceptions come up occasionally.

The arguments boil down to the following:
(The group that favors O-spec)
"O-specs are simpler to code and easier to maintain"
"Report programs are self contained"
"Fewer members to check out"

(Now the PRTF group)
"PRTF is simpler to code and easier to maintain"
"Separation of presentation attributes from report logic makes report
layout
changes easier"
"PRTF can support advanced features such as barcoding, font control,
embedded images/graphics, etc."

Obviously, some (most?) of this is just a matter of personal preference, as
the "simpler and easier" is whichever they've used most.  Otherwise, the
argument falls to capability, which PRTF wins without fail.  Some feel that
being self-contained (O-spec in RPG) is an advantage during debug
situations, but again, I'm not sure that this is a real advantage.  I'm
having a hard time imagining other advantages or disadvantages, so if you
have opinions, feel free to tell me.

tia,

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.