|
|
|
|
Creating Static Software Libraries with armar
Conventions and feedback
The following describes the typographical conventions and
how to give feedback: - Typographical
conventions
The following typographical conventions
are used: monospaceDenotes text that can be entered at the keyboard,
such as commands, file and program names, and source code. monospaceDenotes a permitted abbreviation for a command or
option. The underlined text can be entered instead of the full command
or option name. monospace
italicDenotes arguments
to commands and functions where the argument is to be replaced by
a specific value. - monospace bold
Denotes language keywords when used outside example
code. - italic
Highlights
important notes, introduces special terminology, denotes internal
cross-references, and citations. - bold
Highlights
interface elements, such as menu names. Also used for emphasis in
descriptive lists, where appropriate, and for ARM® processor signal names.
- Feedback on this product
If you have any comments and suggestions about this
product, contact your supplier and give: your name and company the serial number of the product details of the release you are using details of the platform you are using, such as the
hardware platform, operating system type and version a small standalone sample of code that reproduces
the problem a clear explanation of what you expected to happen,
and what actually happened the commands you used, including any command-line
options sample output illustrating the problem the version string of the tools, including the version
number and build numbers.
- Feedback on content
If you have comments on content then send an e-mail to errata@arm.com.
Give: the title the number, ARM DUI 0590B if viewing online, the topic names to which your
comments apply if viewing a PDF version of a document, the page
numbers to which your comments apply a concise explanation of your comments.
ARM also welcomes general suggestions for additions and improvements.
ARM periodically provides updates and corrections to its documentation
on the ARM Information Center, together with knowledge articles
and Frequently Asked Questions (FAQs).
|
|
|