in reply to Re: Monitoring a variable during refactoring
in thread Monitoring a variable during refactoring

Thanks good to know.

It might be overkill in my case but handy in others. :)

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

  • Comment on Re^2: Monitoring a variable during refactoring

Replies are listed 'Best First'.
Re^3: Monitoring a variable during refactoring
by karlgoethebier (Abbot) on Jul 04, 2019 at 15:48 UTC

    I just wondered what Uncle Bob might say about all this magic stuff.

    «The Crux of the Biscuit is the Apostrophe»

    perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

      Perhaps the word "magic" pre-disposes a programmer against it. Especially us non-tolkien fans. But thinking about it more I say it aids transparency as far as I can know who reads or modifies my variablles. However, if by "magic", variables are unxplainedly altered then that's ACME territory.

      Is this "magic" not the same as having a private variable within a class only accessible via magic hooks aka getter and setter methods which may spawn many actions in addition to getting and setting a variable?

      I have no idea and never heard of Bob before.

      But I wonder what you think. Care to elaborate?

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

        Probably he would recommend Damnatio ad bestias? Who nows what else. May be i‘ll write him an email and ask for support 🤪. I‘ve recently read that his current favorite language is Clojure. Best regards, Karl

        «The Crux of the Biscuit is the Apostrophe»

        perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help