I gave that a try with the following result:
user@pt--d830:/data/finder$ perl finder.pl
Operator or semicolon missing before &__inline at (eval 117) line 1 (#
+1)
(S ambiguous) You used a variable or subroutine call where the par
+ser
was expecting an operator. The parser has assumed you really mean
+t to
use an operator, but this is highly likely to be incorrect. For
example, if you say "*foo *foo" it will be interpreted as if you s
+aid
"*foo * 'foo'".
Operator or semicolon missing before &__inline at (eval 117) line 1.
at finder.pl line 9
main::__ANON__('Operator or semicolon missing before &__inline
+ at (eval 117) ...') called at (eval 117) line 1
eval 'sub __extern_inline () { &extern &__inline;}
;' called at /usr/lib/perl/5.14/sys/cdefs.ph line 288
require sys/cdefs.ph called at /usr/lib/perl/5.14/features.ph
+line 196
require features.ph called at /usr/lib/perl/5.14/sys/ioctl.ph
+line 7
require sys/ioctl.ph called at finder.pl line 21
Ambiguous use of & resolved as operator & at (eval 117) line 1 (#2)
(W ambiguous) %, &, and * are both infix operators (modulus,
bitwise and, and multiplication) and initial special characters
(denoting hashes, subroutines and typeglobs), and you said somethi
+ng
like *foo * foo that might be interpreted as either of them. We
assumed you meant the infix operator, but please try to make it mo
+re
clear -- in the example given, you might write *foo * foo() if you
really meant to multiply a glob by the result of calling a functio
+n.
Ambiguous use of & resolved as operator & at (eval 117) line 1.
at finder.pl line 9
main::__ANON__('Ambiguous use of & resolved as operator & at (
+eval 117) line 1.\x{a}') called at (eval 117) line 1
eval 'sub __extern_inline () { &extern &__inline;}
;' called at /usr/lib/perl/5.14/sys/cdefs.ph line 288
require sys/cdefs.ph called at /usr/lib/perl/5.14/features.ph
+line 196
require features.ph called at /usr/lib/perl/5.14/sys/ioctl.ph
+line 7
require sys/ioctl.ph called at finder.pl line 21
I think this must be an internal thing.
"This is perl 5, version 14, subversion 2 (v5.14.2) built for x86_64-linux-gnu-thread-multi
".
Thanks for the help...
It is always better to have seen your target for yourself, rather than depend upon someone else's description.
-
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.
|