```{index} single: _v; Config function ``` ```{index} single: Config::_v; Perl function ``` # _v Print the full `perl -V` report to `STDOUT`. ## Synopsis ```perl use Config; Config::_V(); ``` ## What you get back Nothing. Side effects only: a multi-section dump covering the `myconfig` summary, compile-time options (sorted), the host OS, the compile-date line, every `PERL*`/`PPERL*` entry in `%ENV`, and the contents of `@INC`. ## Examples ```perl ## Equivalent of the command-line `pperl -V`: use Config; Config::_V(); ``` ## Edge cases - Output goes to the OS `STDOUT` directly; Perl-level `STDOUT` redirection with `local *STDOUT` does not affect it. - `@INC` entries are written verbatim, including any non-UTF-8 bytes. ## Differences from upstream - Lines describing the compiler and compile date reflect pperl's Rust-based build. - `%ENV` probe includes `PPERL*` in addition to `PERL*` so pperl-aware environments are visible in the dump.