RE: Procedure with multiple fields computed

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>Procedures can only export 1 value, however.  For the
>present, I have made 2 procedures and call them
>back-to-back.  It seems wasteful to me, however, as
>they will _always_ be used together.

Commonly, procedures that return a value are called "functions", like
X=SIN(90).  That's certainly one way to look at procedures, but not the only
way.  Sometimes you legitimately need to return multiple values, say
converting a street address to latitude/longitude.  My parameter convention
is input, modify, output, status, so I would have something like

callp cvtToLatLong (inpAddressStruc: outLat: outLon: errCode)

There's no right/wrong, but I strongly advise against EXPORT/IMPORT in
favour of explicit parameter declarations.  It makes future maintenance,
debugging and re-use so much easier.
  --buck