Nat Torkington writes: > Mark-Jason Dominus writes: > > RFC should have a section that addresses the feasibility of > > translating perl5 to perl6 code if the proposed change is adopted. > > This section should be required. > > I agree. > > Ziggy, want to patch the sample RFC and the RFC format document? Since you haven't had a chance to do this yet, I thought it might help if I supplied a patch. --- rfc-format.html 2000/08/29 16:33:46 1.1 +++ rfc-format.html 2000/08/29 16:35:30 @@ -44,7 +44,7 @@ <H1><A NAME="Format">Format</A></H1> <P> RFCs are written in POD. <EM>rfc-sample.pod</EM> is a sample. The important sections are: TITLE, VERSION, ABSTRACT, -DESCRIPTION, IMPLEMENTATION, and REFERENCES. An optional section is STATUS. +DESCRIPTION, IMPLEMENTATION, TRANSLATION, and REFERENCES. An optional section is +STATUS. <P> A description of each section follows: @@ -117,6 +117,16 @@ <P> Discussion of the possible implementations. This doesn't have to be completely defined down to the <CODE>char *</CODE>, instead enough to show that it can be done. + +<P> +<HR> +<H2><A NAME="TRANSLATION">TRANSLATION</A></H2> +<P> +Discussion of the issues involved in translating old Perl 5 code to +Perl 6 code. If a Perl 5 feature is being eliminated, can it be +emulated in Perl 6? If a feature is being changed, can the old +behavior be achieved with the new feature? Remember that it must be +possible to perform the translation automatically. <P> <HR> --- rfc-sample.pod 2000/08/29 16:38:41 1.1 +++ rfc-sample.pod 2000/08/29 16:38:13 @@ -47,6 +47,17 @@ new model of signal handling which would make it difficult to reuse algorithms and code for systems programming from C. +=head1 TRANSLATION + +In the 'Checkpointing' scenario, Perl 5 code would run without change. + +In the 'Event Loop' scenario, Perl would be supplied with a module, +possibly Signal.pm, which provided a magical %SIG array which would +emulate the old behavior. Installing a handler into %SIG would +actually register an event handler with Perl's event loop. Using %SIG +would automatically load this module, similar to the way Error.pm is +loaded automatically when %! is used. + =head1 REFERENCES RFC 6: "Standard Event Loop"