<refentry id="classname.element">
<?dbhtml filename="classname.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>

<refmeta>
<indexterm><primary>elements</primary>
<secondary>classname</secondary></indexterm>
<refentrytitle>classname</refentrytitle>
<refmiscinfo>Element</refmiscinfo>
</refmeta>
<refnamediv>
<refname>classname</refname>
<refpurpose>&classname.purpose;</refpurpose>
</refnamediv>

&classname.synopsis.gen;
<refsect1 condition='ref.description'><title>Description</title>

<para>
The <sgmltag>ClassName</sgmltag> tag is used to identify the name of a
class.  This is likely to occur only in documentation about
object-oriented programming systems, languages, and architectures.
</para>

<para>
DocBook does not contain a complete set of inlines appropriate for
describing object-oriented programming environments.  (While it has
<sgmltag>ClassName</sgmltag>, for example, it has nothing suitable for
methods.)  This will be addressed in a future version of DocBook.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.inline;
</para>
</refsect2>




&classname.parents.gen;
&classname.children.gen;
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&classname.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>

<informalexample role="example-source">
<programlisting>&classname.example.1.txt;</programlisting>
</informalexample>

<anchor id="ex.os.classname.1" role="HACK-ex.out.start"/>
&classname.example.1.gen;
<anchor id="ex.oe.classname.1" role="HACK-ex.out.end"/>

&classname.example.seealso.gen;
</refsect1>
</refentry>

