TipcMsgAppendReal16

T_BOOL TipcMsgAppendReal16(msg, real16_data) 
T_IPC_MSG msg; 
T_REAL16 real16_data;

Arguments

Return Values

TRUE if the field was successfully appended to the message, FALSE otherwise.

Diagnostics

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

T_ERR_NULL_PTR — msg was null

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

T_ERR_MSG_INVALID — msg was not a valid message

Description

TipcMsgAppendReal16 appends a 16-byte real number (REAL16) field containing real16_data to the end of a message’s data.

See Also

Examples

	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.

T_IPC_MSG mt; 
T_IPC_MSG msg; 
 
#define USER_MT_REAL16_TEST 100 
mt = TipcMtCreate("real16_test", USER_MT_REAL16_TEST,  
                  "real16"); 
if (mt == NULL) { 
  return;  /* error */ 
} 
 
msg = TipcMsgCreate(mt); 
if (msg == NULL) { 
  return;  /* error */ 
} 
 
/* An RTclient would typically set the destination of */ 
/* a message at this point by calling TipcMsgSetDest. */ 
 
if (!TipcMsgAppendReal16(msg, 1e1000)) { 
  return;  /* error */ 
}  
 
/* A process would typically send a message at this point by */ 
/* calling TipcConnMsgSend or TipcSrvMsgSend. */ 
 
/* A process would typically destroy a message at this point by */ 
/* calling TipcMsgDestroy. */