|
The parameters entries in the REMOTE
PROCEDURE file are for documentation purposes only. They frequently do not get
updated when the RPC signature changes. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse I don't think I'm quite sure what you are asking. In MUMPS, if a
parameter is not supplied, the corresponding variable is undefined in the
called routine. In cases where the parameters you wish to omit are at the end
of the list, you can simply leave them out D CALL(X,Y) but if they are not at the end, you need to supply a "slot"
for the missing parameter as in D CALL(X,,Z) Now, if the code being called was something like CALL(V1,V2,V3) ; ;do stuff Q then, in the first case V3 would be undefined, and in the second, V2
would be undefined. Of course, it goes without saying that if the variable
bound to the actual parameter (in this case, X, Y or Z) is undefined, you will
get a run time error. === Gregory Woodhouse "Nothing is as powerful than an idea whose time has come." -- Victor Hugo On Jul 15, 2005, at 11:06 AM, James Gray wrote:
Are there
any issues if there is a mismatch between the number of input parameters listed
in file 8994 for an RPC call and the number of parameters in the formal list on
the line tag. Here is what the line tag looks like: URG(Y,GMRCO) ;new urgency from
101.42 Here
is the info from the Remote Procedure file NUMBER:
859
NAME: ORQQCN URGENCIES
|
- RE: [Hardhats-members] RPC MISMATCH Doug Martin
- Re: [Hardhats-members] RPC MISMATCH James Gray
