Branch: refs/heads/design-into-raku
  Home:   https://github.com/perl6/specs
  Commit: 3d62b9ea86f586612d5df9ea9460a12239b6ccf2
      
https://github.com/perl6/specs/commit/3d62b9ea86f586612d5df9ea9460a12239b6ccf2
  Author: Elizabeth Mattijsen <l...@wenzperl.nl>
  Date:   2019-11-16 (Sat, 16 Nov 2019)

  Changed paths:
    M S01-overview.pod
    M S02-bits.pod
    M S03-operators.pod
    M S04-control.pod
    M S05-regex.pod
    M S06-routines.pod
    M S07-lists.pod
    M S08-capture.pod
    M S09-data.pod
    M S10-packages.pod
    M S11-modules.pod
    M S12-objects.pod
    M S13-overloading.pod
    M S14-roles-and-parametric-types.pod
    M S15-unicode.pod
    M S16-io.pod
    M S17-concurrency.pod
    M S19-commandline.pod
    M S21-calling-foreign-code.pod
    M S22-package-format.pod
    M S24-testing.pod
    M S26-documentation.pod
    M S28-special-names.pod
    M S29-functions.pod
    M S31-pragmatic-modules.pod
    M S32-setting-library/Basics.pod
    M S32-setting-library/Containers.pod
    M S32-setting-library/Exception.pod
    M S32-setting-library/IO.pod
    M S32-setting-library/Numeric.pod
    M S32-setting-library/Rules.pod
    M S32-setting-library/Str.pod
    M S32-setting-library/Temporal.pod
    M S99-glossary.pod
    M html/index.html
    M html/perl-with-historical-message.css
    M html/style.css

  Log Message:
  -----------
  Move the design documents into the Raku era

This goes beyond just replacing "Perl 6" with "Raku", and "Perl 5" by "Perl".
Clearly, many of the oldes documents still assumed that Raku was going to be
another version of "Perl", hence the word "Perl" was often used without any
digit following it.  I have tried to deduce the meaning from the context and
either changed these to "Raku" (looking towards the future), or left them to
be "Perl" (when looking to the past).

I've also done this as Raku hopefully will get some more eyeballs looking at
it, and how it got designed / conceived.  Having a mix of "Perl", "Perl 5"
and "Perl 6" in there, will only cause more confusion.  Which we do *NOT*
want to have.

Errors may have been made in this editorial process.  So please do not assume
this is canon in any way!  If you think something is wrong, let us know or
even better, provide a Pull Request!

Thank you for reading this!

Reply via email to