Change terminal write usage message to accommodate long double
This commit is contained in:
parent
b02cce38d7
commit
901d49c4e6
11
src/term.c
11
src/term.c
|
@ -574,11 +574,12 @@ static int cmd_write(PROGRAMMER * pgm, struct avrpart * p,
|
||||||
"Ellipsis ... writes <len> bytes padded by repeating the last <data> item.\n"
|
"Ellipsis ... writes <len> bytes padded by repeating the last <data> item.\n"
|
||||||
"\n"
|
"\n"
|
||||||
"<data> can be hexadecimal, octal or decimal integers, double, float or\n"
|
"<data> can be hexadecimal, octal or decimal integers, double, float or\n"
|
||||||
"C-style strings and chars. For numbers, an optional case-insensitive suffix\n"
|
"C-style strings and chars. For integers, an optional case-insensitive suffix\n"
|
||||||
"specifies the data size: HH: 8 bit, H/S: 16 bit, L: 32 bit, LL: 64 bit, F:\n"
|
"specifies the data size: HH: 8 bit, H/S: 16 bit, L: 32 bit or LL: 64 bit.\n"
|
||||||
"32-bit float. Hexadecimal floating point notation is supported. The\n"
|
"Floating point types follow the C convention (add F for 32-bit float or L for\n"
|
||||||
"ambiguous trailing F in 0x1.8F makes the number be interpreted as double;\n"
|
"long double). Hexadecimal floating point notation is supported. The ambiguous\n"
|
||||||
"use a zero exponent as in 0x1.8p0F to denote a hexadecimal float.\n"
|
"trailing F in 0x1.8F makes the number be interpreted as double; use a zero\n"
|
||||||
|
"exponent as in 0x1.8p0F to denote a hexadecimal float.\n"
|
||||||
"\n"
|
"\n"
|
||||||
"An optional U suffix makes a number unsigned. Ordinary 0x hex numbers are\n"
|
"An optional U suffix makes a number unsigned. Ordinary 0x hex numbers are\n"
|
||||||
"always treated as unsigned. +0x or -0x hex numbers are treated as signed\n"
|
"always treated as unsigned. +0x or -0x hex numbers are treated as signed\n"
|
||||||
|
|
Loading…
Reference in New Issue