I've been using Opcode and Opcodes to grok B and the opcodes. For example,
#!/usr/bin/perl use strict; use Opcodes; use Opcode qw(opdump); use Data::Dumper::Concise; print Dumper (opdump), "\n", (scalar opcodes), "\n", (opname2code('gv')), "\n", (opdesc(7)), "\n", (opclass(7)), "\n", (opdesc(opclass(7))), "\n"; (opdump) lists all the opcodes. (scalar opcodes) the number of opcodes for your version of perl (opname2code('gv')) gives the number('code') of gv. (opdesc(7)) the number for gv. Gives a short description (opclass(7)) - classes such as OP, COP, UNOP, BINOP, etc. - here, gv is a svop_or_padop which is 6 (opdesc(opclass(7))) - tells you that it's a scalar variable

In reply to Re: Where to find info on low level perl internals names? by Khen1950fx
in thread Where to find info on low level perl internals names? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.