How come a certain piece of Perl code runs fine under “regular” perl, but fails under Mason?
Mason is usually a red herring in this situation. Mason IS “regular” perl, with a very simple system to translate Mason component syntax to Perl code. You can look at the object files Mason creates for your components (in the obj/ subdirectory of the Mason data directory) to see the actual Perl code Mason generates.
Related Questions
- Describe the advantages of writing a managed code application instead of unmanaged one. What’s involved in certain piece of code being managed?
- Describe the advantages of writing a managed code application instead of unmanaged one. Whats involved in certain piece of code being managed?
- How come a certain piece of Perl code runs fine under "regular" perl, but fails under Mason?