Thought I'd share something funny with ye fellow monks...

$ ./server.pl 3000
given is experimental at ./server.pl line 86.
when is experimental at ./server.pl line 87.
when is experimental at ./server.pl line 88.
Bareword "shit" not allowed while "strict subs" in use at ./server.pl line 46.
Execution of ./server.pl aborted due to compilation errors.

The culprit:

sub process_get {
  my $client = shit;
  my $url = shift;
  my $data = shift;

Come to think of it, this should actually be pretty common but it's the first time that's ever happened to me in about 20 years of Perl hacking!

Good thing I use strict and warnings in all my code ;-)

Replies are listed 'Best First'.
Re: One of those odd compiler messages...
by Laurent_R (Canon) on Aug 30, 2018 at 17:59 UTC
    There used to be a time, decades ago, when, if you issued the following command at the shell prompt:
    make love
    the make utility would reply:
    Sorry. Do not know how to make love

      I used a version that replied to make love with:

      not war?

        Still easily achievable by creating a Makefile consisting of
        love: @echo not war\?

        ($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord }map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
Re: One of those odd compiler messages...
by stevieb (Canon) on Aug 30, 2018 at 03:25 UTC

    Definitely ++ good sir... I needed a good laugh :)

Re: One of those odd compiler messages...
by Anonymous Monk on Aug 30, 2018 at 04:36 UTC