Re: Why $File::Find::prune = 1 returns used only once error

The difference is that use executes the module's code at compile time, basically making $File::Find::prune known earlier than with require, which executes at runtime. One really simple workaround is to use the variable twice: $File::Find::prune = $File::Find::prune = 1; (Update: Of course this removes typo protection if you happen to make the same typo twice, e.g. if you used copy&paste on the variable name.)

Comment on Re: Why $File::Find::prune = 1 returns used only once error Select or Download Code

Replies are listed 'Best First'.
Re^2: Why $File::Find::prune = 1 returns used only once error by h2 (Beadle) on Apr 18, 2021 at 21:49 UTC
This was also a clever little trick, which is likewise good to know as a possible solution. In the end, however, I ended up, basically by accident, using it twice anyway, for an actual reason, so the issue went away, but it's good to be aware of these little intricacies, which actually led me to not use this feature in the past since the warnings were a mystery to me and I just moved on, so now that's all resolved and working fine. It's odd what missing one key bit of information that isn't very intuitive or obvious can do in terms of hindering progress and development.	[reply]

Replies are listed 'Best First'.

Re^2: Why $File::Find::prune = 1 returns used only once error
by h2 (Beadle) on Apr 18, 2021 at 21:49 UTC

This was also a clever little trick, which is likewise good to know as a possible solution. In the end, however, I ended up, basically by accident, using it twice anyway, for an actual reason, so the issue went away, but it's good to be aware of these little intricacies, which actually led me to not use this feature in the past since the warnings were a mystery to me and I just moved on, so now that's all resolved and working fine. It's odd what missing one key bit of information that isn't very intuitive or obvious can do in terms of hindering progress and development.

[reply]