mingw/info/stabs/Nested-Symbols.html

   1 <html lang="en">
   2 <head>
   3 <title>STABS</title>
   4 <meta http-equiv="Content-Type" content="text/html">
   5 <meta name="description" content="STABS">
   6 <meta name="generator" content="makeinfo 4.3">
   7 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
   8 </head>
   9 <body>
  10 <div class="node">
  11 <p>
  12 Node:<a name="Nested%20Symbols">Nested Symbols</a>,
  13 Next:<a rel="next" accesskey="n" href="Basic-Cplusplus-Types.html#Basic%20Cplusplus%20Types">Basic Cplusplus Types</a>,
  14 Previous:<a rel="previous" accesskey="p" href="Class-Names.html#Class%20Names">Class Names</a>,
  15 Up:<a rel="up" accesskey="u" href="Cplusplus.html#Cplusplus">Cplusplus</a>
  16 <hr><br>
  17 </div>
  18
  19 <h3 class="section">Defining a Symbol Within Another Type</h3>
  20
  21    <p>In C++, a symbol (such as a type name) can be defined within another type.
  22
  23    <p>In stabs, this is sometimes represented by making the name of a symbol
  24 which contains <code>::</code>.  Such a pair of colons does not end the name
  25 of the symbol, the way a single colon would (see <a href="String-Field.html#String%20Field">String Field</a>).  I'm
  26 not sure how consistently used or well thought out this mechanism is.
  27 So that a pair of colons in this position always has this meaning,
  28 <code>:</code> cannot be used as a symbol descriptor.
  29
  30    <p>For example, if the string for a stab is <code>foo::bar::baz:t5=*6</code>,
  31 then <code>foo::bar::baz</code> is the name of the symbol, <code>t</code> is the
  32 symbol descriptor, and <code>5=*6</code> is the type information.
  33
  34    </body></html>
  35