Mark - it definitely is not just you. Module reloading is frustrating precisely because it works much of the time but not all of the time. This is just the nature of Perl modules - they can do too many funky things that depend on compilation order or on things that can only reliably run once per process.
I do encourage you to check out Catalyst and the auto-restarting server. I was skeptical of this at first, but if you've got a reasonably fast machine, then it works well. By the time you hit "save" in your editor and move over to your browser to reload, Catalyst has generally finished restarting. Jon > 2. When I want to be able to work on a function, and get it right, > without restarting the webserver every time. It may be just me, but > I have not been able to get mod_perl to force recompliation of > changed .pm modules reliably, even in our dev environment. That > means that when we change code in modules, we have to restart the > webserver, but when we change code in Mason components we don't. > Obviously, this gives a big incentive to leave code in Mason modules, > at least during debugging. > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Mason-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mason-users > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
