Re^2: Filehandle in subroutine in use VRML.pm

Thanks for the quick response. It will take me awhile to formulate why myprint() even exists, and what my ultimate goal is, so please give me some time. Regarding the archaic syntax in my perl programs, I'm 80 years old, and've been programming since 1965, so if we were conversing you'd probably hear some stuff like "Awesome," "Beet Feet" and "Bug out" from me. Anyway, I'll come back to this, and thanks again for the response.

Comment on Re^2: Filehandle in subroutine in use VRML.pm

Replies are listed 'Best First'.
Re^3: Filehandle in subroutine in use VRML.pm by haukex (Archbishop) on Jul 07, 2022 at 12:24 UTC
Regarding the archaic syntax in my perl programs, I'm 80 years old, and've been programming since 1965, so if we were conversing you'd probably hear some stuff like "Awesome," "Beet Feet" and "Bug out" from me. Sure, I understand, and a few of the edits I made are indeed purely stylistic (`for` is equivalent to `foreach`, dropping the parens on function calls, or running the code through perltidy), but at least the changes I named in my node above have become best practices for good reason, as explained in the links. And Use strict and warnings is quite important - your question is a good example of that and the potential of symbolic references to cause confusion and hard to diagnose bugs.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: Filehandle in subroutine in use VRML.pm
by haukex (Archbishop) on Jul 07, 2022 at 12:24 UTC

Regarding the archaic syntax in my perl programs, I'm 80 years old, and've been programming since 1965, so if we were conversing you'd probably hear some stuff like "Awesome," "Beet Feet" and "Bug out" from me.

Sure, I understand, and a few of the edits I made are indeed purely stylistic (for is equivalent to foreach, dropping the parens on function calls, or running the code through perltidy), but at least the changes I named in my node above have become best practices for good reason, as explained in the links. And Use strict and warnings is quite important - your question is a good example of that and the potential of symbolic references to cause confusion and hard to diagnose bugs.

[reply]
[d/l]
[select]