Agreed on the --language concept, although I think I prefer "--prog"
(mentioned in #49168) to "--language". Not everything we might want
to invoke in this manner is actually a compiler or language.
If we're agreed on this approach, I'll open a [todo] ticket for it.
I might even write the patch to make it work. :-)
Then, using the $0 argument to 'main' in src/main.c, we can treat the name of the
executable as setting the --language option, so, if 'perl6' is an alias to 'parrot', then:
$ perl6 myfile.pl
is the same as:
$ parrot --language=perl6 myfile.pl
I'm opposed to the command-line pattern of:
$ parrot perl6 myfile.pl
We don't want people to have to type 'parrot' every time they run a script with a language
implemented on Parrot, so there's no value in providing a shortcut that only does half the
job. It could also lead to some nasty conflicts, if someone happens to have a source file with
the same name as one of their installed languages.
IMO, not really. I don't think we want to treat fakecutables as
the official mechanism for creating command-line tools using Parrot.