Beefy Boxes and Bandwidth Generously Provided by pair Networks Ovid
Perl: the Markov chain saw
 
PerlMonks  

Re^6: Strict isn't strict enough

by davies (Vicar)
on Jan 01, 2012 at 11:39 UTC ( #945787=note: print w/ replies, xml ) Need Help??


in reply to Re^5: Strict isn't strict enough
in thread Strict isn't strict enough

It must depend on declare's documented behaviour.

I think you're trying to have a Socratic dialogue with me, for which I'm grateful, but I'm not clear where it's leading, meaning that my confusion is increasing. Tye has given me a workaround, but no-one has answered outright my original question "Is there anything that will report the use of undeclared fully qualified variable names?". From the help I have received, I'm pretty sure that the answer is "no". I'm used to having to use fully qualified names to avoid "Bill Gates knows best" problems, so I was not expecting the behaviour I experienced until I read the docs, and I was expecting it to be the sort of issue that had been resolved by others. If (as seems to be the case) not, I shall have different expectations in future. But as I say, I'm not certain where this is leading. If it's somewhere useful, I shall be duly grateful.

Regards,

John Davies

Update: fixed minor typo


Comment on Re^6: Strict isn't strict enough
Download Code
Re^7: Strict isn't strict enough
by BrowserUk (Pope) on Jan 01, 2012 at 12:12 UTC

    The simple fact is that not only do you not have to declare global variables -- "fully qualified variable names" are always globals --, you cannot declare them. Perl has no mechanism for doing that.

    You seem to be equating the action of our with that of my, but they are in not equivalent. my actually creates new variables, but our simply allows you silent, unqualified access to them in the current lexical scope.

    One possibility that might in some way meet your requirement would be to use Hash::Util::lock_keys() to restrict the package hash to just those keys you require.

    Update: A little explanation of the idea:

    use Hash::Util qw[ lock_keys ];; $My::Space::fred = 12345;; %My::Space::hash = 1 .. 10;; @My::Space::array = 1 .. 10;; lock_keys( %My::Space:: );; print $My::Space::fred;; 12345 print $My::Space::fred = 23456;; 23456 print $My::Space::fred;; 23456 print $My::Space::freddy = 1234;; Attempt to access disallowed key 'freddy' in a restricted hash at (eva +l 18) line 1, <STDIN> line 10.

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

    The start of some sanity?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://945787]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (9)
As of 2014-04-19 01:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (475 votes), past polls