I’m just wondering how you guys deal with persistance while developing.
I find it extremly hard to deal with different behaviour depending on
which process of apache is currently running and has loaded my changes
to a class. Consequtive reloads will randomly yield the desired results,
but with apache running it’s 5 processes, they are far between. I find
that I often give up and run apachectl graceful to be able to see my
results immediatly.
How do you guys deal with this?
db
···
–
Feb 13* Be happy, It’s Adar !
Feb 13* Rosh Chodesh Adar (Beginning of the month of Adar)
> I find it extremly hard to deal with different behaviour
> depending on which process of apache is currently running and has
> loaded my changes to a class.
Look in the ruby lib dir. There’s a nice module called ‘autoload’, I
think it does what you want.
···
On Thu, 13 Feb 2003 15:02:43 +0900 Daniel Bretoi lists@debonair.net wrote:
My upload script also restarts apache. It’s the easiest way I know of to
make sure your changes get made everywhere.
For a while I spent a lot of time using load' instead ofrequire’,
depending on whether $DEBUG was true or not… but that added restrictions
on how I could code (since some things I want run once only). Restarting
apache is really the easiest thing.
Chris
···
----- Original Message -----
From: “Daniel Bretoi” lists@debonair.net
To: “ruby-talk ML” ruby-talk@ruby-lang.org
Sent: Wednesday, February 12, 2003 10:02 PM
Subject: persistance again
Hi,
I’m just wondering how you guys deal with persistance while developing.
I find it extremly hard to deal with different behaviour depending on
which process of apache is currently running and has loaded my changes
to a class. Consequtive reloads will randomly yield the desired results,
but with apache running it’s 5 processes, they are far between. I find
that I often give up and run apachectl graceful to be able to see my
results immediatly.
How do you guys deal with this?
db
–
Feb 13* Be happy, It’s Adar !
Feb 13* Rosh Chodesh Adar (Beginning of the month of Adar)
When I’m debugging mod_perl I’ll use apache’s -X flag so that there’s
only one server process responding to requests. Once I think I’m happy
then I try a “normal” run.
I’m just wondering how you guys deal with persistance while developing.
I find it extremly hard to deal with different behaviour depending on
which process of apache is currently running and has loaded my changes
to a class. Consequtive reloads will randomly yield the desired results,
but with apache running it’s 5 processes, they are far between. I find
that I often give up and run apachectl graceful to be able to see my
results immediatly.