RE: Starting out with sub-procedures

["Andy Holmer" <aholmer@xxxxxxxxxx>]

Dave,

>I am confused, I should say more confused than normal.  Looking back at
the
>last time I used QCMDEXEC, I cannot find that I used the PI specs.  Why
are
>they needed?

CallP had no bearing on whether or not you needed PI specs.  You need PI
specs anytime you write your own procedure.  If I call any compiled
procedure, then I will do not need to worry about PIs.  PI specs are
looked at during compiling the module containing a procedure.  The
person that wrote the command QCMDEXC worried about the PI spec, you
don't need to.  You only concern is that your prototype exactly matches
the PI.

Buck wrote a wrapper for the QCMDEXC called DoCmd.  Because he wrote a
new and complete procedure, he needed to include the PI spec.  If he had
called QCMDEXC from the mainline, rather than the wrapper procedure,
there would have been no PI specs.  If the wrapper procedure was
compiled into an existing module or service program, then there would
have been no PI specs.  By writing a wrapper, and IMO adding a tad bit
more confusion, he also eliminated a couple parameters, which made the
wrapper call a little easier.  While this _may_ be overkill in the case
of QCMDEXC, in cases where there are half a dozen parameters, half of
them data structures, this can be MUCH easier.

Lastly, you can also have PI specs that would replace the *Entry PList
in your program.  These would have no bearing on you calling other
programs or procedures from your mainline.

HTH, Andy

                        
Andy Holmer
1095 Nimitzview Drive
Suite 403
Cincinnati, OH 45230
(513) 232-9100
f-(513) 232-9249