Tony Bowden wrote:
... but I think that there should be a certain level of ability that
should be assumed when coding commercially ...
My current situation is somewhat unusual because Perl is not the
language that the people I am coding with were hired to write. They are
mostly Java program
I know it has been a while since this thread was active but I am also
having the problem with posted variables being losed & it is also
consistant with the problems below - ie if I wait 15 sec (keepalive
setting) then the variable are posted ok.
I took the script that you posted (which I have inc
I just read the POD for Apache::DBI, and then rewrote it.
Hope no-one is offended, that no meaning is lost, and that
the revision is worth looking at and perhaps including on CPAN.
Cheers
lee (now offlist)
=head1 NAME
Apache::DBI - Initiate a persistent database connection
=head1 SYNOPSIS
# Co
From: "Steven Lembark" <[EMAIL PROTECTED]>
> One quick way to deal with testing things is to tag the releases
> with something meaningful and pass the tag to Q/A. They do an
> update -d -P -r yourtag and test it. If things work then the update
> gets run again in production and life goes on. Since
> "Tony" == Tony Bowden <[EMAIL PROTECTED]> writes:
Tony> We're drifting further and further off topic here, but the trick to the
Tony> Schwartzian Transform is the caching, not the maps. The maps are just a
Tony> convenient construct that allows the whole thing to be written in one
Tony> com
On Sun, Nov 03, 2002 at 11:48:55AM -0600, Steven Lembark wrote:
> >I'm not sure anyone has actually posited using map for performance, but
> >in most cases that would indeed be a pretty stupid reason to use it.
> See the Schwartzian Transform for an excellent example of
> where you would use map fo
-- Rob Nagler <[EMAIL PROTECTED]>
We are transitioning (slowly) between perl 5.005 and 5.6.1. Our trick
is to have separate 5.005 and 5.6.1 build/test (and sometimes dev)
machines. I'm not sure this solves your problem.
Simplest fix is to have two trees. One way to do this is take
everythin
Michael Schout writes:
> example, one time we upgraded Apache::Filter between releases.
> Unfortunately, the old version was not compatible with the new version,
> so a single machine could run either the current release branch, or the
> development branch, but not both simultaneously (because A
-- Tony Bowden <[EMAIL PROTECTED]>
On Sat, Nov 02, 2002 at 12:13:19PM -, Jeff wrote:
It sounds like you're saying that you should only use a subset of Perl
as some programmers may not understand the other parts of it?
That is what I'm saying. I'm aware that this is a controversial
opin
On Fri, Nov 01, 2002 at 01:42:45PM -0500, Perrin Harkins wrote:
> >It sounds like you're saying that you should only use a subset of Perl
> >as some programmers may not understand the other parts of it?
> That is what I'm saying. I'm aware that this is a controversial opinion
> in the Perl world.
On Sat, Nov 02, 2002 at 12:13:19PM -, Jeff wrote:
>>>It sounds like you're saying that you should only use a subset of Perl
>>>as some programmers may not understand the other parts of it?
>> That is what I'm saying. I'm aware that this is a controversial
>> opinion in the Perl world. Howev
11 matches
Mail list logo
