TipcMsgFieldUpdateReal16ArrayPtr

Name

TipcMsgFieldUpdateReal16ArrayPtr — update the pointer of the message field returned by TipcMsgAppendReal16ArrayPtr

Synopsis

T_BOOL TipcMsgFieldUpdateReal16ArrayPtr(field, *real16_array, array_size) 
T_IPC_MSG_FIELD field; 
T_REAL16 *real16_array; 
T_INT4 array_size;

Arguments

field — message pointer field to update

real16_array — data for new message field

array_size — number of elements in real16_array

Return Values

TRUE if the pointer was successfully updated, FALSE otherwise.

Diagnostics

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

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.

Description

TipcMsgFieldUpdateReal16ArrayPtr updates the pointer of the message field returned by TipcMsgAppendReal16ArrayPtr. The contents of the pointer are not copied. Instead, the supplied pointer is entered directly into the message field's internal data structure. The caller is responsible for making sure that the pointer remains valid for the lifetime of the message field, and for freeing it, if necessary, when the message field has been destroyed.


	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 pointer of the REAL16_ARRAY field:

T_REAL16 *ptr1, *ptr2; 
T_INT4 size1, size2; 
T_IPC_MSG_FIELD field; 
 
if (!TipcMsgAppendReal16ArrayPtr(msg, ptr1, size1, &field)) { 
  return;  /* error */ 
} 
 
if (!TipcMsgFieldUpdateReal16ArrayPtr(field, ptr2, size2)) 
  return;  /* error */  
}