1

This screen transcript pretty much says it all:

ftype
PerlScript=C:\strawberry\perl\bin\perl.exe "%1" %*
RakuScript=C:\rakudo\bin\raku.exe "%1" %*

assoc
.pl=PerlScript
.raku=RakuScript

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PL;.RAKU

The reason that I have information on perl is that I'm a long-time perl programmer and, more importantly, perl has always worked (extension-free, Perl.exe-free). The assumption I made was that raku would work as well. My question is, what did I miss? Because this next snippet demonstrates that my assumption was wrong.

sub MAIN(Str $filename) {
    say "Program Name: ", $*PROGRAM-NAME;
    say "File Argument: ", $filename;
}

C:\Users\hsmyers\Rakudo>raku parsepgn 3games.pgn
Could not open parsepgn. Failed to stat file: no such file or directory

C:\Users\hsmyers\Rakudo>raku parsepgn.raku 3games.pgn
Program Name: parsepgn.raku
File Argument: 3games.pgn
6
  • 1
    The backslashes in the paths indicate to me that this is on Windows, right? Also, just to make sure: what version of Rakudo are you using? Commented Aug 10 at 19:54
  • Yes, Windows 11 pro (experimental) and I just DL'd Rakudo Star (.msi) Commented Aug 10 at 20:25
  • 1
    FWIW, this works on any system other than Windows. But that doesn't help you. I hope someone with more Windows / Rakudo Star knowledge will be able to answer. Or you could make an issue: github.com/rakudo/star/issues Commented Aug 10 at 23:08
  • Thought I'd start here before I go the issue route. My analysis suggests that there is a difference in how the receiving app handles the information from cmd. Seems likely it's a very up-front problem in raku.exe. But what do I know? Commented Aug 11 at 2:57
  • 1
    @jubilatious The '>' is part of my prompt in the cmd window. Commented Aug 11 at 16:58

0

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.