[% setvar title Keep dump capability. %]
|Note: these documents may be out of date. Do not use as reference!|
To see what is currently happening visit http://www.perl6.org/
Keep dump capability.
Maintainer: S. A. Janet <email@example.com> Date: 30 Sep 2000 Mailing List: firstname.lastname@example.org Number: 358 Version: 1 Status: Developing
To simplify distribution of programs in binary form, support for dump should be kept.
This would immensely aid distribution of code from one Linux, Windows, etc. machine to others without requiring all the recipients to be able to install Perl, compile and install modules required by the program, and configure their hosts so that Perl find the modules. There are also times when pre-loading and pre-processing large amounts of data are desirable.
RFC 267 wants dump eliminated mainly because it is a common name for user subroutines, bit also because it can be accomplished with a kill signal. I really do not care if dump is renamed, but I believe keeping the capability is in perl's interest for greater acceptance and use.