$ perl -Mstrict -e '$test = "foo"'
[download]

Global symbol "$test" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.
[download]

$ perl -Mstrict -e '$test = "foo"' 2> error.log
[download]

hope this helps,

Update: as for using syslog to log the errors, I don't know if you can do this, since as far as I can remember, you use a specific system call to do that: syslog(3).

Update #2: a quick question in #debian @ freenode.net and I have something else: check the logger command, which is a "shell command interface to the syslog(3) system log module" (from the manpage).

I use perl module Sys::Syslog for sending any messages to syslog, it work great. I only want to catch perl errors (from within my scripts not by redirecting it from the command line)and send them to syslog the same way.

Hotshot

oh. I understood something else from your first post...

There are many ways to catch exceptions. You could use eval(), but using eval() will not work for warnings from the compiler, from the POD:

Beware that using "eval" neither silences perl from printing warnings 
+to STDERR, nor does it stuff the text of warning messages into $@.
[download]

Or you can use Error as nite_man suggests, but I just made a couple of tests and read the docs and compiler warnings don't seem to be handled by it.

hope this helps,

use Error qw(:try);

  try {
    some code;
    code that might thrown an exception;
    more code;
    return;
  }
  catch Error with {
    my $ex = shift;   # Get hold of the exception object
    handle the exception;
  }
  finally {
    cleanup code;
  };  # <-- Remember the semicolon
[download]

Updated:
For insert message into Apache log you can use module Apache::Log or Sys::Syslog, Net::Syslog for console applications.

      
--------------------------------
SV* sv_bless(SV* sv, HV* stash);

Take a look at the __WARN__ and __DIE__ signal handlers in perlvar for one way to catch die & warn messages.

However, be careful of the die handler since it can cause problems in shared environments like mod_perl. If used incorrectly it can also foul up people using die for exception handling. Read the docs in perlvar and on die carefully.

It may be simpler to override the CORE::GLOBAL::die() routine and substitute your own that does the appropriate logging calls.