Re^4: Using use itself -- file scope !?

What does the above quote from perldoc -f use try to say?

Some modules are pragmas. pragams affect the behaviour of code scope in which they are used rather than provide subs.

What kind of ordinary modules has file scope!?

Since you're using "ordinary" to mean not like a pragma, none do by definition.

What exactly might effective through the end of file refer to?

It equates end of file with end of the package, and thus to the end of the visibility of the imported functions.

Comment on Re^4: Using use itself -- file scope !?

Replies are listed 'Best First'.
Re^5: Using use itself -- file scope !? by jakobi (Pilgrim) on Oct 29, 2009 at 21:09 UTC
Thanx, ikegami. Reading your #3 finally makes sense of the paragraph; implicit assumption of the most simple usage style of the package statement of one per file, never to reoccur in any other file (probably this 'file scope' shouldn't even be mentioned in this section at all). Provided that this tripped at least me for sure, do you think this large enough to warrant trying a patch/rewrite of this documentation section? I wouldn't mind trying myself for (hubris &) learning experience, but I'd certainly need some hand holding when I've found the source pods and did some reading on p5p and patch submission (`warn "non-native speaker combined with utter lack of p5p experience...\n"`). cu & HTH, Peter -- hints may be untested unless stated otherwise; use with caution & understanding.	[reply] [d/l]
Re^6: Using use itself -- file scope !? by ikegami (Patriarch) on Oct 29, 2009 at 21:23 UTC
Latest version: pod/perlfunc.pod in perl.git (click on "raw") How to write patches: perlrepository But in this case, a `diff -u` against the original should be sufficient.	[reply] [d/l]