Re: Best Practice for Replacing Globals

This is hard to tell by a verbal description and without seeing an SSCCE.

Basically: The more you need to refactor, the riskier.

Some thoughts:

Is it a one file project?
If you use file scoped my lexicals instead, you won't have to change the code using those vars.
If it's multi-file project,
you could use a tie interface to implement those methods (in FETCH and STORE) with my vars, while sticking with the old syntax.
Those methods will come with a speed penalty, but you can also use it to monitor where your vars are actually used and gradually replace them with real lexicals.
Regarding modperl,
I'm not sure if that's still state of the art, I'd rather look for fastcgi or similar first.

Cheers Rolf
_{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)

Wikisyntax for the Monastery}

Comment on Re: Best Practice for Replacing Globals

Replies are listed 'Best First'.
Re^2: Best Practice for Replacing Globals by marto (Cardinal) on Apr 19, 2023 at 13:43 UTC
" I'm not sure if that's still state of the art, I'd rather look for fastcgi or similar first." Alternatively, Mojolicious -> Porting from CGI:: Application.	[reply]
Re^2: Best Practice for Replacing Globals by beaker121 (Novice) on Apr 19, 2023 at 15:42 UTC
It's a large project with many files. I don't really know what you mean by replacing them with real lexicals as I don't see that as being possible, these values need to be used across the program as a whole. For example, I'm trying to move towards more OO approach and was thinking of having the user information (preferences, username after session has been validated etc.) in its own package.	[reply]
Re^3: Best Practice for Replacing Globals by LanX (Saint) on Apr 19, 2023 at 16:00 UTC
> I don't really know what you mean by replacing them with real lexicals If a package var is used only inside a single file, you can use a lexical without tieing it. > these values need to be used across the program as a whole. Hmm, as I said I need to guess to understand your situation. For instance one of your descriptions fits for constants. I can't see the need to change them in a modperl environment. And you may be able to go the inverse way, keep those package vars and tie them to a class which adapts to the modperl runtime environment by accessing its values in a lexical hash. Again plain guess work without you showing an SSCCE. Cheers Rolf _{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^4: Best Practice for Replacing Globals by beaker121 (Novice) on May 06, 2023 at 21:37 UTC
Thank you, in the end I have refactored all the globals out into CGI::application params and a user object. The static behaviour ones are now using the CGI::application config plug in.	[reply]