@@ -394,8 +394,8 @@ Other than that, the semantics are identical to the direct form.
394
394
=head1 Versioning
395
395
396
396
Whenever an authority (such as a CPAN author or a company) posts a
397
- compilation unit as part of an official distribution, or enters it into
398
- any standard Perl 6 library, the module is required to declare its full
397
+ compilation unit as part of a distribution of Perl 6 code , or enters it into
398
+ any Perl 6 library, the module is required to declare its full
399
399
name so that installations can know its unique, immutable identity,
400
400
such that multiple versions by different authors can coexist, all of
401
401
them available to any installed version of Perl. (For the purposes of
@@ -499,12 +499,12 @@ the version lineage that was created first wins, unless overridden by
499
499
local policy or by official abandonment by the original auth (as
500
500
determined either by the author or by community consensus in case the
501
501
author is no longer available or widely regarded as uncooperative).
502
- An officially abandoned lineage will be selected only if it is the
502
+ An abandoned lineage will be selected only if it is the
503
503
only available lineage of locally installed modules.
504
504
505
505
Once the auth is selected, then and only then is any version
506
- selection done. This implies that all official compunits record
507
- permanently when they were first installed in the official library,
506
+ selection done. This implies that all installed compunits record
507
+ permanently when they were first installed in the library,
508
508
and this creation date is considered immutable. This date can be specified
509
509
with the uppercase block typename CREATED. For example:
510
510
@@ -663,12 +663,12 @@ it make sense more often, some hierarchical authority-naming scheme
663
663
may be devised so that authorities can have temporary subauthorities
664
664
to hold branches without relinquishing overall naming authority.)
665
665
666
- So anyway, the basic rule is this: you may import language tweaks
667
- from your own private (user-library) code as you like; however, all
668
- imports of language tweaks from the official library must specify
669
- the exact interface version of the package.
666
+ So anyway, the basic rule is this: you may import language tweaks from
667
+ your own private (user-library as specified in @*INC ) code as you like;
668
+ however, all imports of language tweaks from the installed Perl 6
669
+ library must specify the exact interface version of the package.
670
670
671
- Such officially installed interface versions must be considered
671
+ Such installed interface versions must be considered
672
672
immutable on the language level, so that once any language-tweaking
673
673
compunit is in circulation, it may be presumed to represent a fixed
674
674
language change. By examination of these interface versions a language
@@ -710,7 +710,7 @@ The requirement for immutable interfaces extends transitively to
710
710
any packages imported by a language tweak module. There can be no
711
711
indeterminacy in the language definition either directly or indirectly.
712
712
713
- It must be possible for any official compilation unit to be separately compiled
713
+ It must be possible for any compilation unit to be separately compiled
714
714
without knowledge of the lexical or dynamic context in which it will be
715
715
embedded, and this separate compilation must be able to produce a deterministic
716
716
profile of the interface. It must be possible to extract out the
0 commit comments