NAME
    Interpreter::Info - Get information about rakudo interpreter

VERSION
    This document describes version 0.001 of Interpreter::Info (from Perl
    distribution Interpreter-Info), released on 2023-12-07.

FUNCTIONS
  get_bash_info
    Usage:

     get_bash_info(%args) -> [$status_code, $reason, $payload, \%result_meta]

    Get information about bash interpreter.

    This function is not exported by default, but exportable.

    Arguments ('*' denotes required arguments):

    *   path => *filename*

        Choose specific path for interpreter.

    Returns an enveloped result (an array).

    First element ($status_code) is an integer containing HTTP-like status
    code (200 means OK, 4xx caller error, 5xx function error). Second
    element ($reason) is a string containing error message, or something
    like "OK" if status is 200. Third element ($payload) is the actual
    result, but usually not present when enveloped result is an error
    response ($status_code is not 2xx). Fourth element (%result_meta) is
    called result metadata and is optional, a hash that contains extra
    information, much like how HTTP response headers provide additional
    metadata.

    Return value: (any)

  get_nodejs_info
    Usage:

     get_nodejs_info(%args) -> [$status_code, $reason, $payload, \%result_meta]

    Get information about nodejs interpreter.

    This function is not exported by default, but exportable.

    Arguments ('*' denotes required arguments):

    *   path => *filename*

        Choose specific path for interpreter.

    Returns an enveloped result (an array).

    First element ($status_code) is an integer containing HTTP-like status
    code (200 means OK, 4xx caller error, 5xx function error). Second
    element ($reason) is a string containing error message, or something
    like "OK" if status is 200. Third element ($payload) is the actual
    result, but usually not present when enveloped result is an error
    response ($status_code is not 2xx). Fourth element (%result_meta) is
    called result metadata and is optional, a hash that contains extra
    information, much like how HTTP response headers provide additional
    metadata.

    Return value: (any)

  get_perl_info
    Usage:

     get_perl_info(%args) -> [$status_code, $reason, $payload, \%result_meta]

    Get information about perl interpreter.

    This function is not exported by default, but exportable.

    Arguments ('*' denotes required arguments):

    *   path => *filename*

        Choose specific path for interpreter.

    Returns an enveloped result (an array).

    First element ($status_code) is an integer containing HTTP-like status
    code (200 means OK, 4xx caller error, 5xx function error). Second
    element ($reason) is a string containing error message, or something
    like "OK" if status is 200. Third element ($payload) is the actual
    result, but usually not present when enveloped result is an error
    response ($status_code is not 2xx). Fourth element (%result_meta) is
    called result metadata and is optional, a hash that contains extra
    information, much like how HTTP response headers provide additional
    metadata.

    Return value: (any)

  get_python_info
    Usage:

     get_python_info(%args) -> [$status_code, $reason, $payload, \%result_meta]

    Get information about python interpreter.

    This function is not exported by default, but exportable.

    Arguments ('*' denotes required arguments):

    *   path => *filename*

        Choose specific path for interpreter.

    Returns an enveloped result (an array).

    First element ($status_code) is an integer containing HTTP-like status
    code (200 means OK, 4xx caller error, 5xx function error). Second
    element ($reason) is a string containing error message, or something
    like "OK" if status is 200. Third element ($payload) is the actual
    result, but usually not present when enveloped result is an error
    response ($status_code is not 2xx). Fourth element (%result_meta) is
    called result metadata and is optional, a hash that contains extra
    information, much like how HTTP response headers provide additional
    metadata.

    Return value: (any)

  get_rakudo_info
    Usage:

     get_rakudo_info(%args) -> [$status_code, $reason, $payload, \%result_meta]

    Get information about rakudo interpreter.

    This function is not exported by default, but exportable.

    Arguments ('*' denotes required arguments):

    *   path => *filename*

        Choose specific path for interpreter.

    Returns an enveloped result (an array).

    First element ($status_code) is an integer containing HTTP-like status
    code (200 means OK, 4xx caller error, 5xx function error). Second
    element ($reason) is a string containing error message, or something
    like "OK" if status is 200. Third element ($payload) is the actual
    result, but usually not present when enveloped result is an error
    response ($status_code is not 2xx). Fourth element (%result_meta) is
    called result metadata and is optional, a hash that contains extra
    information, much like how HTTP response headers provide additional
    metadata.

    Return value: (any)

  get_ruby_info
    Usage:

     get_ruby_info(%args) -> [$status_code, $reason, $payload, \%result_meta]

    Get information about Ruby interpreter.

    This function is not exported by default, but exportable.

    Arguments ('*' denotes required arguments):

    *   path => *filename*

        Choose specific path for interpreter.

    Returns an enveloped result (an array).

    First element ($status_code) is an integer containing HTTP-like status
    code (200 means OK, 4xx caller error, 5xx function error). Second
    element ($reason) is a string containing error message, or something
    like "OK" if status is 200. Third element ($payload) is the actual
    result, but usually not present when enveloped result is an error
    response ($status_code is not 2xx). Fourth element (%result_meta) is
    called result metadata and is optional, a hash that contains extra
    information, much like how HTTP response headers provide additional
    metadata.

    Return value: (any)

HOMEPAGE
    Please visit the project's homepage at
    <https://metacpan.org/release/Interpreter-Info>.

SOURCE
    Source repository is at
    <https://github.com/perlancar/perl-Interpreter-Info>.

AUTHOR
    perlancar <perlancar@cpan.org>

CONTRIBUTING
    To contribute, you can send patches by email/via RT, or send pull
    requests on GitHub.

    Most of the time, you don't need to build the distribution yourself. You
    can simply modify the code, then test via:

     % prove -l

    If you want to build the distribution (e.g. to try to install it locally
    on your system), you can install Dist::Zilla,
    Dist::Zilla::PluginBundle::Author::PERLANCAR,
    Pod::Weaver::PluginBundle::Author::PERLANCAR, and sometimes one or two
    other Dist::Zilla- and/or Pod::Weaver plugins. Any additional steps
    required beyond that are considered a bug and can be reported to me.

COPYRIGHT AND LICENSE
    This software is copyright (c) 2023 by perlancar <perlancar@cpan.org>.

    This is free software; you can redistribute it and/or modify it under
    the same terms as the Perl 5 programming language system itself.

BUGS
    Please report any bugs or feature requests on the bugtracker website
    <https://rt.cpan.org/Public/Dist/Display.html?Name=Interpreter-Info>

    When submitting a bug or request, please include a test-file or a patch
    to an existing test-file that illustrates the bug or desired feature.