in reply to Re: Experiences With Mason
in thread Experiences With Mason

Thanks, you actually had real experience with Mason, which was helpful

>> The downsides are that it's difficult (and I've never gone to the effort of discovering exactly how) to run a debugger on a broken page.

I've noticed one issue which occurs when there is a failure in a dependent module from "use" (not the first level include in, say the .html component, but a secondary module). It gives a very generic "failed to load" name-of-primary-module. You could find this by having a dummy program which loads the same modules, and invoke it from the command-line to find these problems (but it is odd Mason doesn't find them).

I've also noticed a little weirdness with the caching when there is a failure in a unit to compile. Things get unhappy, and well, you just have to restart Apache. The only way to know this is you get this odd feeling that not all is right with the world.

Replies are listed 'Best First'.
Re^3: Experiences With Mason
by blogical (Pilgrim) on Feb 03, 2009 at 02:44 UTC

    If you follow the Very Good Advice of keeping most of your non-display code in external libraries and you run under mod_perl, make sure you fully stop&start apache whenever you make a change, to ensure you see the results.

    Consider developing in CGI mode (no mod_perl,) with a single apache process, with code_cache_max_size => 0 (disabled, no caching) to avoid some such weirdness and speed development.