comparison src/tooltalk.c @ 32:e04119814345 r19-15b99

Import from CVS: tag r19-15b99
author cvs
date Mon, 13 Aug 2007 08:52:56 +0200
parents 859a2309aef8
children 131b0175ea99
comparison
equal deleted inserted replaced
31:b9328a10c56c 32:e04119814345
931 and VALUE can be a string or an integer. Tooltalk doesn't 931 and VALUE can be a string or an integer. Tooltalk doesn't
932 define any semantics for VTYPE, so only the participants in the 932 define any semantics for VTYPE, so only the participants in the
933 protocol you're using need to agree what types mean (if anything). 933 protocol you're using need to agree what types mean (if anything).
934 Conventionally \"string\" is used for strings and \"int\" for 32 bit integers. 934 Conventionally \"string\" is used for strings and \"int\" for 32 bit integers.
935 Arguments can initialized by providing a value or with 935 Arguments can initialized by providing a value or with
936 `set-tooltalk-message-attribute'. The latter is neccessary if you 936 `set-tooltalk-message-attribute'. The latter is necessary if you
937 want to initialize the argument with a string that can contain 937 want to initialize the argument with a string that can contain
938 embedded nulls (use 'arg_bval). 938 embedded nulls (use 'arg_bval).
939 */ 939 */
940 (msg, mode, vtype, value)) 940 (msg, mode, vtype, value))
941 { 941 {