Re: Perl and MSWin11: any issues?

Hi Ken

I'm wondering if it's not still too early to ask, especially since you are not migrating soon.

Or do you hope this to be a "pinned" constantly visible thread which is actualized over months and years?

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on Re: Perl and MSWin11: any issues?

Replies are listed 'Best First'.
Re^2: Perl and MSWin11: any issues? by kcott (Archbishop) on Sep 08, 2021 at 20:32 UTC
G'day Rolf, I had also wondered if I was perhaps jumping the gun somewhat; however, if there is a fundamental change in `11.00` (I'm guessing at version number format) I'd like to know about it sooner rather than later. My computer is for both personal and $work use — working remotely from home is the norm for me; I've been doing this for several years; it's not a temporary, Covid-related measure. For my own usage, I'd probably leave migration until as late as possible, perhaps mid-2025; but, for $work, it may need to be earlier (I don't have any dates on that yet). There are potentially issues that affect $work computers but not my computer at home. The "Git for Windows", that I mentioned above, could be an example of this: some colleagues run Perl applications via "Git BASH". Although not affected directly by these, I'd still like to be in a position to offer feedback to others in the office. I wasn't planning on providing ongoing updates to this thread as the `11.xx` series matures. To be honest, I hadn't really given this any thought: I'd probably deal with future problems in separate threads: something like "Perl issue with MSWin 11.26" (as a purely fictitious example). — Ken	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Perl and MSWin11: any issues?
by kcott (Archbishop) on Sep 08, 2021 at 20:32 UTC

G'day Rolf,

I had also wondered if I was perhaps jumping the gun somewhat; however, if there is a fundamental change in 11.00 (I'm guessing at version number format) I'd like to know about it sooner rather than later.

My computer is for both personal and $work use — working remotely from home is the norm for me; I've been doing this for several years; it's not a temporary, Covid-related measure. For my own usage, I'd probably leave migration until as late as possible, perhaps mid-2025; but, for $work, it may need to be earlier (I don't have any dates on that yet).

There are potentially issues that affect $work computers but not my computer at home. The "Git for Windows", that I mentioned above, could be an example of this: some colleagues run Perl applications via "Git BASH". Although not affected directly by these, I'd still like to be in a position to offer feedback to others in the office.

I wasn't planning on providing ongoing updates to this thread as the 11.xx series matures. To be honest, I hadn't really given this any thought: I'd probably deal with future problems in separate threads: something like "Perl issue with MSWin 11.26" (as a purely fictitious example).

— Ken

[reply]
[d/l]
[select]