Re^2: Strawberry Perl: my @INC gets/is destroyed on XP after some days

No, not really. I'm not using it with *nix-style paths in @INC.

But 'after a while' i get *nix-style paths in @INC.

I noticed it first after firing up my emacs shortcut for shell-comand-on-region for perltidy and emacs told me that something went wrong.

Examining @INC the usual way (like perl -E 'say for @INC;') shows these *nix-style paths.

Well, i have also cygwin installed on my box. But i run Strawberry Perl from cmd.

Best regards, Karl

ŤThe Crux of the Biscuit is the Apostropheť

Comment on Re^2: Strawberry Perl: my @INC gets/is destroyed on XP after some days Select or Download Code

Replies are listed 'Best First'.
Re^3: Strawberry Perl: my @INC gets/is destroyed on XP after some days by BrowserUk (Patriarch) on Aug 23, 2015 at 18:48 UTC
i have also cygwin installed on my box. That is almost certainly the source of your problem. Somehow your two perl installs are interacting. I don't have any details for you -- I gave up on cygwin within days of the first time I installed it 12+ years ago -- but that's where you need to look. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :) In the absence of evidence, opinion is indistinguishable from prejudice. I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!	[reply]
Re^3: Strawberry Perl: my @INC gets/is destroyed on XP after some days by syphilis (Archbishop) on Aug 24, 2015 at 00:47 UTC
Examining @INC the usual way (like `perl -E 'say for @INC;'`) shows these nix-style paths* This would almost certainly indicate that the PATH environment variable is currently set such that the first perl.exe to be located is Cygwin's, not Strawberry's. Next time this happens, run `PATH` to see what that environment variable actually contains ... and then try to work out why it changed. Cheers, Rob	[reply] [d/l] [select]