[% setvar title Request For New Pragma: Shell %]
|Note: these documents may be out of date. Do not use as reference!|
To see what is currently happening visit http://www.perl6.org/
Request For New Pragma: Shell
Maintainer: Bryan C. Warnock <email@example.com> Date: 5 Aug 2000 Last Modified: 18 Sep 2000 Mailing List: firstname.lastname@example.org Number: 42 Version: 3 Status: Frozen Frozen since: v2
Added the heavy footnoting about name-clobbering with
Perl 6 should add a new pragma, previously thought to be called
now called something else, although I don't know what. So I'll stick with
shell. Although quite frankly
Bob would be just fine with me.
The shell that Perl uses for shell interpretation is defined at compile time. Furthermore, it is optimized away when no metacharacters are found within the command string.
There are times when one may need (or desire) to change the shell used for interpretation, as well as force shell interpretation, regardless of optimization, for consistency's sake.
Perl runs on many platforms. Many of these platforms, either by default, desire, or need, may have multiple command interpreters that Perl may want to interface with by default. (ie, through the use of backticks or system().)
Perl is not just a glue language, but a SuperGlue language. I ab^H^Huse Perl to interact with a lot of home-grown command interpreters as either a driver, a hardware controller, or Expect-type engine. It's a lot more DWIMmer when I can operate in that environment, vice the standard OS one.
Furthermore, there are times when speed be damned! I need every `` to go through the command interpreter in order to get back consistent results, and I don't want to have to mangle the output string in order to force a metacharacter.
It is important, however, that this be lexically scoped. One can't really afford to have some unknown module expect /bin/sh and accidentally send the command to turn on a robot's "Kill Human" mode, for instance.
Laziness, and perhaps a bit of Hubris.
This was an easy hack in Perl 5, except for the scoping issue. Ideally, there'd be a -force flag to check, and a method to change the location of the shell, the shell arguments, and perhaps what is defined as a shell metacharacter.
See above. I hacked this for Perl 5 in about two minutes, minus the scoping, which I never could figure out. :-( The scoping lament is continued in RFC 40.
use shelland the semantics it would add. (Obviously, other changes to the language notwithstanding.)
Frozen. There has been little discussion, other than pointing out that Shell
is already a module, and on platforms that are case insensitive, the
two would clobber. Furthermore, it was agreed that this
doesn't fit well into that
Shell. Hence, this pragma is more or
less the ubiquitous "player to be named later."
RFC 40: Module Scope Control.