AnsweredAssumed Answered

VRf-Changing_Record_Field_Names

Question asked by VRFuser on Aug 6, 1996
send q VRf-Changing_Record_Field_Names vrf

from: Greg Goebel / HP-MXD
      gvg@lvld.hp.com / 970-679-3030 / FAX 970-679-5971
to:   VRf
date: Tuesday, 06 August 1996 1644 MDT

Hi All:

Slightly to my surprise, the relevant lab person (Casey, who is a "lurker" on
the VRf) says he has had several requests for the ability to change record
field names.  Casey has some suggestions for what to do different ... he
would like some feedback and see how you like them.

Just post responses to the VRf to "Casey" and he will be able to read them.
If he needs to respond, he will do it through me.

[%%] gvg

PS:  I think I nailed the worst broken links on the VRf over the weekend
so I think we won't be getting so many mail returns.

-------------------------------------------------------------------------

buildRecord(text array T, int 0/1, A, B, C...)

A function to build a record.  The function can have 3 or more parameters.
The first parameter must be a of type text array.  The 2nd param is to
specify if the output record is of shape Scalar as on the "Build Record" box.
A value of 0 for this parameter means build Scalar and a non-zero value means
Array.  The 3rd thru nth inputs are any kind of vee container.

There must be at least enough names in "T" to provide for field names
of the record.  Too many names is OK, not enough is an error.

-------------------------------------------------------------------------

changeRecordNames(record aRec, text array T)

Changes the FIRST LEVEL record names to the ones specified in the text
array "T".  There must be enough names in T to provide for every field
in the record.  Too many names is OK, not enough is an error.

I don't want to mess with changing second (or lower) level names.  Is
this OK?

-------------------------------------------------------------------------

I am not stuck on the function names.  If anyone else wants to suggest
better ones I will listen.

-------------------------------------------------------------------------

[<>]

Outcomes