10568f49bSmrg<?xml version="1.0" encoding="UTF-8" ?> 20568f49bSmrg<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"> 30568f49bSmrg 49e7bcd65Smrg<preface id='About_This_Manual'> 59e7bcd65Smrg<title>About This Manual</title> 69e7bcd65Smrg 79e7bcd65Smrg<para> 80568f49bSmrgX Toolkit Intrinsics — C Language Interface is intended to be read by both application programmers 99e7bcd65Smrgwho will use one or more of the many widget sets built with the Intrinsics and by widget 109e7bcd65Smrgprogrammers who will use the Intrinsics to build widgets for one of the widget sets. Not all the 119e7bcd65Smrginformation in this manual, however, applies to both audiences. That is, because the application 129e7bcd65Smrgprogrammer is likely to use only a number of the Intrinsics functions in writing an application and 139e7bcd65Smrgbecause the widget programmer is likely to use many more, if not all, of the Intrinsics functions 149e7bcd65Smrgin building a widget, an attempt has been made to highlight those areas of information that are 159e7bcd65Smrgdeemed to be of special interest for the application programmer. (It is assumed the widget programmer 169e7bcd65Smrgwill have to be familiar with all the information.) Therefore, all entries in the table of 179e7bcd65Smrgcontents that are printed in <emphasis role='strong'>bold</emphasis> indicate the information that 189e7bcd65Smrgshould be of special interest to an application programmer. 199e7bcd65Smrg</para> 209e7bcd65Smrg<para> 219e7bcd65SmrgIt is also assumed that, as application programmers become more familiar with the concepts discussed 229e7bcd65Smrgin this manual, they will find it more convenient to implement portions of their applications 239e7bcd65Smrgas special-purpose or custom widgets. It is possible, nonetheless, to use widgets without 249e7bcd65Smrgknowing how to build them. 259e7bcd65Smrg</para> 269e7bcd65Smrg 279e7bcd65Smrg<bridgehead><emphasis role='strong'>Conventions Used in this Manual</emphasis></bridgehead> 289e7bcd65Smrg<para>This document uses the following conventions:</para> 299e7bcd65Smrg<itemizedlist spacing='compact'> 309e7bcd65Smrg <listitem> 319e7bcd65Smrg <para> 329e7bcd65SmrgGlobal symbols are printed in <function>this special font</function>. These can be either 339e7bcd65Smrgfunction names, symbols defined in include files, data types, or structure names. Arguments to 349e7bcd65Smrgfunctions, procedures, or macros are printed in italics. 359e7bcd65Smrg </para> 369e7bcd65Smrg </listitem> 379e7bcd65Smrg <listitem> 389e7bcd65Smrg <para> 399e7bcd65SmrgEach function is introduced by a general discussion that distinguishes it from other functions. 409e7bcd65SmrgThe function declaration itself follows, and each argument is specifically explained. 419e7bcd65SmrgGeneral discussion of the function, if any is required, follows the arguments. 429e7bcd65Smrg </para> 439e7bcd65Smrg </listitem> 449e7bcd65Smrg <listitem> 459e7bcd65Smrg <para> 469e7bcd65SmrgTo eliminate any ambiguity between those arguments that you pass and those that a function 479e7bcd65Smrgreturns to you, the explanations for all arguments that you pass start with the word 489e7bcd65Smrgspecifies or, in the case of multiple arguments, the word specify. The explanations for all 499e7bcd65Smrgarguments that are returned to you start with the word <emphasis>returns</emphasis> or, in 509e7bcd65Smrgthe case of multiple arguments, the word <emphasis>return</emphasis>. 519e7bcd65Smrg </para> 529e7bcd65Smrg </listitem> 539e7bcd65Smrg</itemizedlist> 549e7bcd65Smrg</preface> 55