Re: What is this rule for?
- To: Debian Developers <firstname.lastname@example.org>
- Subject: Re: What is this rule for?
- From: Frank Lin PIAT <email@example.com>
- Date: Sun, 11 Oct 2009 10:03:07 +0200
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <20090929062143.GA5792@sumost.ca> <4AC1FA58.firstname.lastname@example.org> <email@example.com> <20090929161430.GB24034@gwolf.org> <4AC26FA2.firstname.lastname@example.org> <email@example.com>
On Tue, 2009-09-29 at 13:37 -0700, Russ Allbery wrote:
> Andreas Tscharner <firstname.lastname@example.org> writes:
> > This is true for Unix/Posix systems, but unfortunately not for Windows
> > systems. And if the maintainer of a great Perl script wants his script
> > to work on both platforms, he'll probably will name it
> > GreatPerlScript.pl If the extension .pl is linked with a Perl
> > interpreter in Windows, he'll be able to run it on both systems without
> > a prepending "perl"
> If he names it GreatPerlScript on Unix and GreatPerlScript.pl on Windows,
> he'll be able to run it on both systems as GreatPerlScript.
This is another interesting point... Should we also preserve the
This is merely a decoration under Windows, but is important under $unix!
Seriously, the developer had to add a file extension to distribute
the file to windows, it doesn't means that such bad practice should be
carried-on on other platforms.
As an alternative to , if a perl/python/$language developer wants
windows users to be able to start a command easily, it is best to
provide a windows "foo.cmd" file which merely launch the interpreter and
command. As a benefit, the command can be launched by executing "foo".
 On doesn't actually "have to" specify the file extension. I can only
speculate on why Python/Perl installer don't set PATHEXT properly...