Skip to content

Commit cbeddcd

Browse files
committed
[v6.d REVIEW] Remove EVAL --encoding respectation
This feature didn't make it into the language and was removed from Rakudo in rakudo/rakudo@31b19d0
1 parent 7f58ce2 commit cbeddcd

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

doc/Type/Cool.pod6

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1412,9 +1412,8 @@ sub EVAL($code where Cool|Blob, :$lang = 'perl6')
14121412
The method form calls subroutine form with invocant as C<$code>, passing
14131413
along named args, if any. Subroutine form coerces L<Cool> C<$code> to
14141414
L<Str>. If C<$code> is a L<Blob>, it'll be processed using the same
1415-
encoding as the C<$lang> compiler would: for C<perl6>, uses the encoding
1416-
specified via C<--encoding> command line argument, or C<utf-8> if none
1417-
were given; for C<Perl5>, processes using same rules as C<perl>.
1415+
encoding as the C<$lang> compiler would: for C<perl6> C<$lang>, uses C<utf-8>;
1416+
for C<Perl5>, processes using the same rules as C<perl>.
14181417
14191418
This works as-is with a literal string parameter. More complex input,
14201419
such as a variable or string with embedded code, is illegal by default.

0 commit comments

Comments
 (0)