EPICS_driver_modules/StreamDevice
0
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

make docu for %r converer more specific about %.2r versus %2r

Browse Source
This commit is contained in:
zimoch
2016-07-01 10:56:46 +02:00
parent 0ba674a341
commit 3acf791409
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/formats.html
View File

@ -370,6 +370,9 @@ With the <code>0</code> flag, the value is unsigned, otherwise signed.
In output, the <em>precision</em> (or sizeof(long) whatever is less) least In output, the <em>precision</em> (or sizeof(long) whatever is less) least
significant bytes of the value are sign extended or zero extended significant bytes of the value are sign extended or zero extended
(depending on the <code>0</code> flag) to <em>width</em> bytes. (depending on the <code>0</code> flag) to <em>width</em> bytes.
The default for <em>precision</em> is 1. Thus if you do not specify
the <em>precision</em>, only the least significant byte is written!
It is common error to write <code>out "%2r";</code> instead of <code>out "%.2r";</code>.
</p> </p>
<p> <p>
In input, <em>width</em> bytes are read and put into the value. In input, <em>width</em> bytes are read and put into the value.
@ -380,7 +383,7 @@ the value is sign extended or zero extended, depending on the
<code>0</code> flag. <code>0</code> flag.
</p> </p>
<p> <p>
Example: <code>out "%.2r"</code> Examples: <code>out "%.2r"; in "%02r";</code>
</p> </p>
<a name="rawdouble"></a> <a name="rawdouble"></a>