They're opcode specific, and occur less often than the public ones, so
they're represented by short mnemonics instead of single-chars; see
-L<op.h> for gory details, or try this quick 2-liner:
+F<op.h> for gory details, or try this quick 2-liner:
$> perl -MB::Concise -de 1
DB<1> |x \%B::Concise::priv
Only some of these are used by the standard styles, the others are
provided for you to delve into optree mechanics, should you wish to
add a new style (see L</add_style> below) that uses them. You can
-also add new ones using L<add_callback>.
+also add new ones using L</add_callback>.
=over 4
representation of a compiled piece of code, I hope. If you have prior
knowledge of all the code refs that your data structures are likely
to have, you can use the C<Seen> method to pre-seed the internal reference
-table and make the dumped output point to them, instead. See L<EXAMPLES>
+table and make the dumped output point to them, instead. See L</EXAMPLES>
above.
The C<Useqq> and C<Deparse> flags makes Dump() run slower, since the
Returns EXPR on success for convenience. You may neglect the
return value and manipulate EXPR as the filehandle directly if you prefer.
+=back
+
=head1 CAVEATS
While it is permissible to C<close> a FileCache managed file,