TipcMsgUpdateNamedReal16ArrayPtr

Name

TipcMsgUpdateNamedReal16ArrayPtr — update a pointer to the value of a named field containing an array of REAL16 fields

Synopsis

T_BOOL TipcMsgUpdateNamedReal16ArrayPtr(msg, name, value, size, 
field_return) 
T_IPC_MSG msg; 
T_STR name; 
T_REAL16 *value; 
T_INT4 size; 
T_IPC_MSG_FIELD *field_return;

Arguments

msg — message to update field in

name — name of the field

value — value of the field

size — number of elements in the field

field_return — optional value to return field (use NULL if not needed)

Return Values

TRUE if the update was successful, FALSE otherwise.

Diagnostics

If TipcMsgUpdateNamedReal16ArrayPtr fails, it returns FALSE and sets the global SmartSockets error number to one of:

T_ERR_NULL_PTR — msg, name or value is null

T_ERR_MSG_INVALID — msg was not a valid message

T_ERR_FT_MISMATCH — the message type grammar did not match the fields in the message

T_ERR_READ_ONLY — the message was marked read-only. This happens if the message is a field in another message.

T_ERR_VALUE_INVALID — value was not a valid value

Description

TipcMsgUpdateNamedReal16ArrayPtr updates a field containing an array of REAL16 fields in a message, associating that field with a name. The value given is used as a pointer to the value, so the copy is made when the message is actually sent, not when the call is made. You must ensure that the data pointed to remains valid until the message is sent.


	Not all platforms fully support the REAL16 type. While some platforms can manipulate them as uninterpreted bytes, they can neither manipulate nor interpret them as numbers.

Examples

This example changes the value of the named field "data":

T_REAL16 *data; 
T_INT4 size; 
if (!TipcMsgUpdateNamedReal16ArrayPtr(msg, "data", data, size, 
T_NULL)) { 
  return;  /* error */ 
}