It’s not Moose, it’s specifically Catalyst’s handling of the information. Probably your Catalyst code is either wonky or relies on the presence of the base packages to already be loaded in such a way that sub packages will fail because they are missing dependent information. Compare these two–
perl -c -e 'sub taco :Chained("/") :PathPart("foo") : CaptureArgs(0) {
+}'
Invalid CODE attributes: Chained("/") : PathPart("foo") : CaptureArgs(
+0) at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
perl -c -e 'use parent "Catalyst::Controller"; sub taco :Chained("/")
+:PathPart("foo") : CaptureArgs(0) {}'
-e syntax OK
Side-note about the -c flag. It’s not just a syntax check, it has to compile code and that means running some of it and there is no way to know what that might include without stepping through it. For example–
# emacs/vi UseMe.pm
package UseMe;
print STDERR "rm -rf /";
perl -c UseMe.pm
UseMe.pm syntax OK
perl -c -e 'use UseMe'
rm -rf /-e syntax OK
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|