Re^2: Testing CLI commands on Windows machines


good chemistry is complicated, and a little bit messy -LW
	PerlMonks

Re^2: Testing CLI commands on Windows machines

by nysus (Parson)

on Sep 12, 2018 at 15:00 UTC ( [id://1222220]=note: print w/replies, xml )

Need Help??

in reply to Re: Testing CLI commands on Windows machines
in thread Testing CLI commands on Windows machines

anki_import is just an executable perl script.

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ Priest";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Re^2: Testing CLI commands on Windows machines Download Code

Replies are listed 'Best First'.

Re^3: Testing CLI commands on Windows machines
by RonW (Parson) on Sep 12, 2018 at 20:07 UTC

Unfortunately, MS Windows doesn't know what to do with a file that has no extension. Maybe a MS Windows expert could make it work, but I'm pretty sure that would not be a good idea on Windows.

Assuming the .pl extension is properly registered and associated with perl.exe, MS Windows will "open" the program using perl.exe, which will then run it.

However, the most common way to run Perl (or other compile-on-execute (or interpreted) languages) is to create a .bat file to run the program.

[reply]

In Section Seekers of Perl Wisdom