HTTP/2 200 server: nginx content-type: text/plain;charset=UTF-8 content-encoding: gzip content-security-policy: default-src 'self'; connect-src 'self' *.google-analytics.com; img-src 'self' data: www.google-analytics.com www.googletagmanager.com; script-src 'self' 'unsafe-inline' www.google-analytics.com www.googletagmanager.com; style-src 'self'; report-uri /csp-reports accept-ranges: bytes age: 0 date: Wed, 15 Oct 2025 03:19:20 GMT via: 1.1 varnish x-served-by: cache-bom-vanm7210083-BOM x-cache: MISS x-cache-hits: 0 x-timer: S1760498360.206346,VS0,VE771 vary: Accept-Encoding strict-transport-security: max-age=31557600 content-length: 797 =over =item exit EXPR X X X =item exit Evaluates EXPR and exits immediately with that value. Example: my $ans = ; exit 0 if $ans =~ /^[Xx]/; See also L|/die LIST>. If EXPR is omitted, exits with C<0> status. The only universally recognized values for EXPR are C<0> for success and C<1> for error; other values are subject to interpretation depending on the environment in which the Perl program is running. For example, exiting 69 (EX_UNAVAILABLE) from a I incoming-mail filter will cause the mailer to return the item undelivered, but that's not true everywhere. Don't use C to abort a subroutine if there's any chance that someone might want to trap whatever error happened. Use L|/die LIST> instead, which can be trapped by an L|/eval EXPR>. The C function does not always exit immediately. It calls any defined C routines first, but these C routines may not themselves abort the exit. Likewise any object destructors that need to be called are called before the real exit. C routines and destructors can change the exit status by modifying L|perlvar/$?>. If this is a problem, you can call L|POSIX/C<_exit>> to avoid C and destructor processing. See L for details. Portability issues: L. =back