On Sun, 29 Jul 2001, Philip Mak wrote:
I have a site running mod_perl that I'm constantly making changes to.
What do I have to do in order to make it so that when I edit any file
(either a .pl script directly called on the site, or a .pm module that my
perl script uses), then the changes
On Mon, 30 Jul 2001, Stas Bekman wrote:
no (re-)?read the manpage. it's all there.
It's possible that Matt wants to add other options to the SYNOPSIS
section, as not everybody bothers to read the manpage. I think people are
used to see all of the functionality covered in SYNOPSIS.
In
--On 30/07/01 06:43 -0400 Philip Mak wrote:
In perldoc Apache::Reload, the DESCRIPTION has the following sections:
- StatINC Replacement
- Register Modules Implicitly
- Register Modules Explicitly
- Special Touch File
I just re-read it again and realized that StatINC Replacement is what
I have a site running mod_perl that I'm constantly making changes to.
What do I have to do in order to make it so that when I edit any file
(either a .pl script directly called on the site, or a .pm module that my
perl script uses), then the changes will take effect automatically? I
would rather
I actually was nearlly successful in accomplishing some sort of mechanism by
which developer packages can be mapped to a virtual package which the real
package points to (did this make sense?). Anyway, it needed to tap into the
symbol table way too extensively and ran into several problems.
I
Hello,
STI was wondering if anyone has successfully setup a development
STenvironment to allow for multiple development copies of modules used
STwithin Mason components. Also, to have the appropriate changes to the
STmodules shown within the development environment.
This can also be a general
Hi Andrew,
On Wed, 31 Jan 2001, Andrew Ho wrote:
What if there are 20 mod_perl developers at your company? You either need
to do admin work to partition the developers by what modules they write,
or run 20 Apache instances, which may be very expensive.
Yes, it's a lot of work to set up an
don't have workstations of their own? You can
build a development environment on a workstation just as easily as you
can on a server...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.Khera Communications, Inc.
Internet: [EMAIL
VKbuild a development environment on a workstation just as easily as you
VKcan on a server...
Not if there are platform-specific dependencies. Say your servers are
heavy duty Sparc machines, and you maintain code for Solaris Sparc only.
Buying workstations for everybody can be quite expensive
:
AH What if there are 20 mod_perl developers at your company? You either need
AH to do admin work to partition the developers by what modules they write,
AH or run 20 Apache instances, which may be very expensive.
And these 20 developers don't have workstations of their own? You can
build a development e
I was wondering if anyone has successfully setup a development environment
to allow for multiple development copies of modules used within Mason
components. Also, to have the appropriate changes to the modules shown
within the development environment.
Thanks,
Stathy Touloumis
Coder
if ( eval
Hi there,
On Tue, 30 Jan 2001, Stathy Touloumis wrote:
I was wondering if anyone has successfully setup a development environment
to allow for multiple development copies of modules used within Mason
components. Also, to have the appropriate changes to the modules shown
within
12 matches
Mail list logo
