LanX has asked for the wisdom of the Perl Monks concerning the following question:
I wan't to disable access to a variable and throw an exception if it's tried.
I was thinking of implementing it with Tie::Scalar and already found Tie::Watch after googling duck'ing for "tie watch" (sic)
Another approach might be keeping the variable undefined and to catch the warning in $SIG{__WARN__}
Questions:
I'm migrating a rather complicated CGI and am gradually introducing new abstractions/variables especially for SQL table names.
Since I have to test the code little by little I want to avoid accidental execution of parts which are still under construction.
That's why I already did a general search and replace and introduced global dummy variables like s/table_X_Y_tree/table_${TABLE_FAMILIY}_tree/g
This "works" already, I get warnings and SQL-queries fails.
A watch expression might be better though.
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Monitoring a variable during refactoring
by haj (Vicar) on Jul 03, 2019 at 17:29 UTC | |
by LanX (Saint) on Jul 03, 2019 at 19:22 UTC | |
by karlgoethebier (Abbot) on Jul 04, 2019 at 15:48 UTC | |
by bliako (Abbot) on Jul 05, 2019 at 01:06 UTC | |
by LanX (Saint) on Jul 04, 2019 at 16:57 UTC | |
by karlgoethebier (Abbot) on Jul 04, 2019 at 17:28 UTC | |
| |
|
Re: Monitoring a variable during refactoring
by Anonymous Monk on Jul 04, 2019 at 20:32 UTC |