On Fri, May 1, 2009 at 10:18, Gunnar Hjalmarsson <nore...@gunnar.cc> wrote:
> Chas. Owens wrote:
>>
>> On Wed, Apr 29, 2009 at 19:07, Chas. Owens <chas.ow...@gmail.com> wrote:
>>>
>>> On Wed, Apr 29, 2009 at 18:44, Gunnar Hjalmarsson <nore...@gunnar.cc>
>>> wrote:
>>> snip
>>>>
>>>> You are encouraged to include a patch also when submitting a bug report
>>>> - I
>>>> did so in the above example, btw - so I still not quite get the
>>>> distinction.
>>>> Are the bug reports handled by a different group of people compared to
>>>> p5p?
>>>
>>> snip
>>>
>>> No, it is my understanding that the bugs reported by perlbug go to p5p
>>> (I have definitely seen them there including the one you referenced),
>>> so you, in effect, did exactly what you should have done. You did get
>>> one response that disagreed with your change, you then sent back a
>>> modification (not a patch). I don't know if that is why you haven't
>>> received any further replies, or the fact that it seems like a very
>>> small issue in comparison to things like "Yet Unicode Bugbear (or two
>>> (or three))"[1].
>>>
>>> 1.
>>> http://www.nntp.perl.org/group/perl.perl5.porters/2009/04/msg145780.html
>>
>> This
>>
>> perl -Mdiagnostics -Mstrict -e '$c =4;'
>>
>> may also be why nobody really responded to your post.
>
> I agree that perldiag says all that needs to be said. But a common way to
> work with perldiag is to look up cryptic error or warning messages when
> needed rather than using the diagnostics pragma.
>
> Unfortunately the message
>
> Global symbol "%s" requires explicit package name
>
> is not very cryptic, so you are not triggered to check perldiag.
>
> Just to clarify: I have not (at least not yet) reported about the wording of
> the error message. The bug report I was referring to above, and that you
> commented on, is about how the meaning of \n is described in perlport. Guess
> I'm to blame for the confusion. ;-)
snip
No, that is my faulty memory.
But the %s is only cryptic if you are looking in perldiag. You
probably shouldn't look in perldiag yourself, use the diagnostics
pragma (instead of the warnings pragma) to get useful for beginners
warnings/errors:
Global symbol "$c" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors (#1)
(F) You've said "use strict vars", which indicates that all variables
must either be lexically scoped (using "my"), declared beforehand using
"our", or explicitly qualified to say which package the global variable
is in (using "::").
Uncaught exception from user code:
Global symbol "$c" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.
at -e line 1
--
Chas. Owens
wonkden.net
The most important skill a programmer can have is the ability to read.
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
