-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File::Next and Windows Junctions (Reparse Points) #34
Comments
Can you please post a PR or even a set of diffs here to this ticket so we can see what you're talking about? |
Will post a Html diff after Taekwondo. Will also add If ^o=='win32' around win32 specific code. Cheers |
P.S Sorry that my pm and pl files use Whitesmiths indent format. For any irritated K&R indent lovers. Perl::tidy will K&R reformat if you wish |
perltidy html output with my changes with a aqua background (in Whitesmiths indent format). My file shows a large number of differences to original next.pm due to indent format being different, HAVE NOT highlighted differences due to indentation. I am testing my code additions wrapped in if $^o=='Win32' on a couple of different Windows operating systems . Will post tomorrow with an example next.pm. |
Opps did not mean to close this Enhancement Issue |
Sorry for delay have been a little busy here is an example file::next.pm. Has been tested Vista,Win7 and Win 10 if ($^O eq 'MSWin32') { ..... } blocks |
Hello Andy and users of File:;Next.
My question is should we add code to handle Windows Junctions ie Skip them like symbolic Link inside if ^o=='Win32' block . Or Should I just fork File::Next to File::Win32::Next. I would like anybodies feedback on which would be preferable? P.S. I have sent my quick and dirty code version of File::Win32::Next which I have tested on Windows Vista, Windows 7, and Windows 10. Thanks for any feedback.
Cheers all
James P
The text was updated successfully, but these errors were encountered: