Standards issue - Comments please.

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

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