Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: $escmode in libraries
Date: Fri, 18 Mar 2005 10:27:09 +1100
Message-ID: <D5451858F628E44EB6CF3789645ED87804F21F@jess.oriel.com.au>
Thread-Topic: $escmode in libraries
Thread-Index: AcUq9eq7akz/1caRSJaSs3jBvxmL6gAUVbbQ
From: "Andrew O'Brien" <andrewo@oriel.com.au>
To: <embperl@perl.apache.org>


> From: Luiz Fernando B. Ribeiro [mailto:luiz@engenhosolucoes.com.br]=20
>
> On Wed, 16 Mar 2005 20:58:37 -0800, Daniel=20
> <embperl@7thfire.com> wrote:
>=20
> > Is this what you use? I'm a little curious what others do=20
> to easily see
> > what variables contain. Maybe there's a good way I'm missing.
>=20
>=20
> In fact I wrote a module using Data::Dumper that writes=20
> variables and =20
> traceback information to a debug file. Send debug information=20
> to screen =20
> may not always be possible and using a debug file allow you=20
> to debug a =20
> production system without bothering your users.

Yep. Even something as simple as the following is easy to find in the
embperl logfile if you've configured it.

Generally I'm turning on the logfile for debugging live systems anyway -
you get a lot more context  that way and its easy enough to break out
each request based on the pid. The '::' is just a random delimiter -
it's not special in any way.

 sub debug {
   my $self =3D shift;
   return unless $some_package_or_whatever_global_saying_I_should_debug;
   print HTML::Embperl::LOG "[$$]DBG: ".join('::',@_)."\n";
 }

Cheers,

Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org