Date: Thursday January 10, 2019 @ 06:16 Author: argrath Update of /cvsroot/perldocjp/docs/perl/5.26.1 In directory sf-cvs:/tmp/cvs-serv129353/perl/5.26.1 Modified Files: perlfunc.pod Log Message: 5.26.1/perlfunc =================================================================== File: perlfunc.pod Status: Up-to-date Working revision: 1.5 Wed Jan 9 21:16:20 2019 Repository revision: 1.5 /cvsroot/perldocjp/docs/perl/5.26.1/perlfunc.pod,v Existing Tags: No Tags Exist -------------- next part -------------- Index: docs/perl/5.26.1/perlfunc.pod diff -u docs/perl/5.26.1/perlfunc.pod:1.4 docs/perl/5.26.1/perlfunc.pod:1.5 --- docs/perl/5.26.1/perlfunc.pod:1.4 Mon Sep 17 23:17:20 2018 +++ docs/perl/5.26.1/perlfunc.pod Thu Jan 10 06:16:20 2019 @@ -3754,13 +3754,11 @@ L<C<@INC>|perlvar/@INC> ¥Ç¥£¥ì¥¯¥È¥ê¤ò¸¡º÷¤·¡¢¥Õ¥¡¥¤¥ë¤¬¸«¤Ä¤«¤ì¤Ð L<C<%INC>|perlvar/%INC> ¤ò¹¹¿·¤·¤Þ¤¹¡£ ¤³¤ì¤é¤ÎÊÑ¿ô¤Ë¤Ä¤¤¤Æ¤Ï L<perlvar/@INC> ¤È L<perlvar/%INC> ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ -Æäˡ¢note that -whilst historically L<C<@INC>|perlvar/@INC> contained '.' (the -current directory) making these two cases equivalent, that is no -longer necessarily the case, as '.' is not included in C<@INC> by default -in perl versions 5.26.0 onwards. +Æäˡ¢Îò»ËŪ¤Ë¤Ï L<C<@INC>|perlvar/@INC> ¤Ë '.' (¥«¥ì¥ó¥È¥Ç¥£¥ì¥¯¥È¥ê) ¤ò +´Þ¤ó¤Ç¤¤¤¿¤Î¤Ç¤³¤ÎÆó¤Ä¤Î¾ì¹ç¤ÏÅù²Á¤Ç¤·¤¿¤¬¡¢ +perl ¥Ð¡¼¥¸¥ç¥ó 5.26.0 °Ê¹ß¤Ç¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï C<@INC> ¤Ë '.' ¤ò +´Þ¤ó¤Ç¤¤¤Ê¤¤¤Î¤Ç¡¢¤â¤Ï¤ä¤½¤¦¤Ç¤Ï¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ Âå¤ï¤ê¤Ë¡¢perl ¤Ï¼¡¤Î¤è¤¦¤Ê·Ù¹ð¤ò½Ð¤·¤Þ¤¹: -(TBT) do "stat.pl" failed, '.' is no longer in @INC; did you mean do "./stat.pl"? @@ -4373,6 +4371,8 @@ =item String eval +(ʸ»úÎó eval) + =begin original Since the return value of EXPR is executed as a block within the lexical @@ -4383,11 +4383,8 @@ =end original EXPR ¤ÎÊÖ¤êÃͤϸ½ºß¤Î Perl ¥×¥í¥°¥é¥à¤Î¥ì¥¥·¥«¥ë¥³¥ó¥Æ¥¥¹¥È¤ÎÃæ¤Ç -¼Â¹Ô¤µ¤ì¤ë¤Î¤Ç¡¢ -any outer lexical variables are -visible to it, and any package variable settings or subroutine and -format definitions remain afterwards. -(TBT) +¼Â¹Ô¤µ¤ì¤ë¤Î¤Ç¡¢³°Â¦¤Î¥ì¥¥·¥«¥ë¥¹¥³¡¼¥×¤Ï¤½¤³¤«¤é¸«¤¨¡¢ +¥Ñ¥Ã¥±¡¼¥¸ÊÑ¿ôÀßÄê¤ä¥µ¥Ö¥ë¡¼¥Á¥ó¤È¥Õ¥©¡¼¥Þ¥Ã¥ÈÀßÄê¤Ï¸å¤Ë»Ä¤ê¤Þ¤¹¡£ =over 4 @@ -4410,16 +4407,15 @@ ¤³¤Îµ¡Ç½¤¬Í¸ú¤Î¾ì¹ç(¤³¤ì¤Ï C<use 5.16> ¤Þ¤¿¤Ï¤½¤ì°Ê¾å¤¬ Àë¸À¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤¹)¡¢ -EXPR is considered to be -in the same encoding as the surrounding program. Thus if -S<L<C<use utf8>|utf8>> is in effect, the string will be treated as being -UTF-8 encoded. Otherwise, the string is considered to be a sequence of -independent bytes. Bytes that correspond to ASCII-range code points -will have their normal meanings for operators in the string. The -treatment of the other bytes depends on if the -L<C<'unicode_strings"> feature|feature/The 'unicode_strings' feature> is -in effect. -(TBT) +EXPR ¤Ï¼þ¤ê¤Î¥×¥í¥°¥é¥à¤ÈƱ¤¸¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ç¤¢¤ë¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ +½¾¤Ã¤Æ¡¢S<L<C<use utf8>|utf8>> ¤¬Í¸ú¤Î¾ì¹ç¡¢ +ʸ»úÎó¤Ï UTF-8 ¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¤â¤Î¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ +¤µ¤â¤Ê¤±¤ì¤Ð¡¢¤³¤Îʸ»úÎó¤Ï¸Ä¡¹¤Î¥Ð¥¤¥ÈÎó¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ +ASCII ¤ÎÈϰϤÎÉä¹æ°ÌÃÖ¤ËÂбþ¤¹¤ë¥Ð¥¤¥È¤Ï¡¢ +ʸ»úÎó¤ÎÁàºî¤Ë´Ø¤·¤ÆÄ̾ï¤Î°ÕÌ£¤ò»ý¤Á¤Þ¤¹¡£ +¤½¤Î¾¤Î¥Ð¥¤¥È¤Î°·¤¤¤Ï¡¢ +<C<'unicode_strings"> feature|feature/'unicode_strings' µ¡Ç½> ¤¬Í¸ú¤Î¾ì¹ç¤« +¤É¤¦¤«¤Ë°Í¸¤·¤Þ¤¹¡£ =begin original @@ -4429,10 +4425,8 @@ =end original -In a plain C<eval> without an EXPR argument, being in S<C<use utf8>> or -not is irrelevant; the UTF-8ness of C<$_> itself determines the -behavior. -(TBT) +EXPR °ú¿ô¤Î¤Ê¤¤Ã±¤Ê¤ë C<eval> ¤Î¾ì¹ç¡¢S<C<use utf8>> ¤ÎÍ̵¤Ï̵´Ø·¸¤Ç¤¹; +C<$_> ¼«¿È¤Î UTF-8 À¤¬¿¶¤ëÉñ¤¤¤ò·èÄꤷ¤Þ¤¹¡£ =begin original @@ -4458,10 +4452,11 @@ =end original -Variables defined outside the C<eval> and used inside it retain their -original UTF-8ness. Everything inside the string follows the normal -rules for a Perl program with the given state of S<C<use utf8>>. -(TBT) +Variables defined outside the +C<eval> ¤Î³°Â¦¤ÇÄêµÁ¤µ¤ì¡¢Æ⦤ǻȤï¤ì¤¿ÊÑ¿ô¤Ï¡¢ +¸µ¤Î UTF-8 À¤ò°Ý»ý¤·¤Þ¤¹¡£ +Æ⦤Îʸ»úÎó¤Ï¡¢S<C<use utf8>> ¤Î¾õÂ֤ˤè¤Ã¤Æ Perl ¥×¥í¥°¥é¥à¤ËŬÍѤµ¤ì¤ë +Ä̾ï¤Îµ¬Â§¤Ë½¾¤¤¤Þ¤¹¡£ =item Outside the C<"unicode_eval"> feature @@ -4473,10 +4468,8 @@ =end original -In this case, the behavior is problematic and is not so easily -described. Here are two bugs that cannot easily be fixed without -breaking existing programs: -(TBT) +¤³¤Î¾ì¹ç¡¢¿¶¤ëÉñ¤¤¤Ë¤ÏÌäÂ꤬¤¢¤ê¡¢¤½¤ì¤Û¤É´Êñ¤Ë¤ÏÀâÌÀ¤Ç¤¤Þ¤»¤ó¡£ +´û¸¤Î¥×¥í¥°¥é¥à¤ò²õ¤µ¤º¤Ë´Êñ¤Ë½¤Àµ¤¹¤ë¤³¤È¤¬½ÐÍè¤Ê¤¤Æó¤Ä¤Î¥Ð¥°¤¬¤¢¤ê¤Þ¤¹: =over 4 @@ -4489,9 +4482,7 @@ =end original -It can lose track of whether something should be encoded as UTF-8 or -not. -(TBT) +¤¢¤ë¤â¤Î¤¬ UTF-8 ¤Ç¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¤«¤É¤¦¤«¤ò¸«¼º¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ =item * @@ -4503,10 +4494,9 @@ =end original -Source filters activated within C<eval> leak out into whichever file -scope is currently being compiled. To give an example with the CPAN module -L<Semi::Semicolons>: -(TBT) +C<eval> ¤ÎÃæ¤Ç͸ú¤Ë¤µ¤ì¤¿¥½¡¼¥¹¥Õ¥£¥ë¥¿¤Ï¡¢¸½ºß¤É¤Á¤é¤Î¥Õ¥¡¥¤¥ë¥¹¥³¡¼¥×¤Ç +¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤ë¤«¤ò¥ê¡¼¥¯¤µ¤»¤Þ¤¹¡£ +CPAN ¥â¥¸¥å¡¼¥ë L<Semi::Semicolons> ¤ò»È¤Ã¤¿Îã¤Ï: BEGIN { eval "use Semi::Semicolons; # not filtered" } # filtered here! @@ -4518,9 +4508,8 @@ =end original -L<C<evalbytes>|/evalbytes EXPR> fixes that to work the way one would -expect: -(TBT) +L<C<evalbytes>|/evalbytes EXPR> ¤Ï¡¢¿Í¤¬ÁÛÄꤹ¤ë¤À¤í¤¦¼êË¡¤ÇÆ°ºî¤¹¤ë¤è¤¦¤Ë +¤³¤ì¤ò½¤Àµ¤·¤Þ¤¹: use feature "evalbytes"; BEGIN { evalbytes "use Semi::Semicolons; # filtered" } @@ -4761,12 +4750,11 @@ =end original -If called when S<C<use utf8>> is in effect, the string will be assumed -to be encoded in UTF-8, and C<evalbytes> will make a temporary copy to -work from, downgraded to non-UTF-8. If this is not possible -(because one or more characters in it require UTF-8), the C<evalbytes> -will fail with the error stored in C<$@>. -(TBT) +S<C<use utf8>> ¤¬Í¸ú¤Î¤È¤¤Ë¸Æ¤Ó½Ð¤µ¤ì¤ë¤È¡¢ +ʸ»úÎó¤Ï UTF-8 ¤Ç¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¤È²¾Äꤵ¤ì¡¢ +C<evalbytes> ¤Ï¡¢Èó UTF-8 ¤Ë¥À¥¦¥ó¥°¥ì¡¼¥É¤·¤¿°ì»þŪ¤Ê¥³¥Ô¡¼¤òºî¤ê¤Þ¤¹¡£ +(UTF-8 ¤¬É¬ÍפÊʸ»ú¤¬¤¢¤ë¤¿¤á¤Ë) ¤³¤ì¤¬ÉÔ²Äǽ¤Ê¾ì¹ç¡¢ +C<evalbytes> ¤Ï¼ºÇÔ¤·¡¢¥¨¥é¡¼¤Ï C<$@> ¤ËÊݴɤµ¤ì¤Þ¤¹¡£ =begin original @@ -4777,11 +4765,11 @@ =end original -Bytes that correspond to ASCII-range code points will have their normal -meanings for operators in the string. The treatment of the other bytes -depends on if the L<C<'unicode_strings"> feature|feature/The -'unicode_strings' feature> is in effect. -(TBT) +ASCII ¤ÎÈϰϤÎÉä¹æ°ÌÃÖ¤ËÂбþ¤¹¤ë¥Ð¥¤¥È¤Ï¡¢ +ʸ»úÎó¤ÎÁàºî¤Ë´Ø¤·¤ÆÄ̾ï¤Î°ÕÌ£¤ò»ý¤Á¤Þ¤¹¡£ +¤½¤Î¾¤Î¥Ð¥¤¥È¤Î°·¤¤¤Ï¡¢ +<C<'unicode_strings"> feature|feature/'unicode_strings' µ¡Ç½> ¤¬Í¸ú¤Î¾ì¹ç¤« +¤É¤¦¤«¤Ë°Í¸¤·¤Þ¤¹¡£ =begin original @@ -4790,10 +4778,7 @@ =end original -¤â¤Á¤í¤ó¡¢ -variables that are UTF-8 and are referred to in the string -retain that: -(TBT) +¤â¤Á¤í¤ó¡¢UTF-8 ¤Çʸ»úÎó¤ÎÃæ¤Ç»²¾È¤µ¤ì¤Æ¤¤¤ëÊÑ¿ô¤Ï¤½¤Î¤Þ¤Þ¤Ç¤¹: my $a = "\x{100}"; evalbytes 'print ord $a, "\n"'; @@ -14367,14 +14352,13 @@ =end original -Note the emphasis on bytes: even if the filehandle has been set to operate -on characters (for example using the C<:encoding(UTF-8)> I/O layer), the +¥Ð¥¤¥Èñ°Ì¤ËÂФ¹¤ëÃí°Õ: Î㤨(Î㤨¤Ð C<:encoding(UTF-8)> I/O Áؤò»È¤¦¤Ê¤É¤·¤Æ) +¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¤¬Ê¸»úñ°Ì¤Ç½èÍý¤¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢ L<C<seek>|/seek FILEHANDLE,POSITION,WHENCE>, -L<C<tell>|/tell FILEHANDLE>, and -L<C<sysseek>|/sysseek FILEHANDLE,POSITION,WHENCE> -family of functions use byte offsets, not character offsets, -because seeking to a character offset would be very slow in a UTF-8 file. -(TBT) +L<C<tell>|/tell FILEHANDLE>, +L<C<sysseek>|/sysseek FILEHANDLE,POSITION,WHENCE> ¥·¥ê¡¼¥º¤Î´Ø¿ô¤Ï +ʸ»ú¥ª¥Õ¥»¥Ã¥È¤Ç¤Ï¤Ê¤¯¥Ð¥¤¥È¥ª¥Õ¥»¥Ã¥È¤ò»È¤¤¤Þ¤¹; +ʸ»ú¥ª¥Õ¥»¥Ã¥È¤Ç¥·¡¼¥¯¤¹¤ë¤Î¤Ï UTF-8 ¥Õ¥¡¥¤¥ë¤Ç¤Ï¤È¤Æ¤âÃÙ¤¤¤«¤é¤Ç¤¹¡£ =begin original @@ -15754,13 +15738,13 @@ =end original -C<$a> and C<$b> are set as package globals in the package the sort() is -called from. That means C<$main::a> and C<$main::b> (or C<$::a> and -C<$::b>) in the C<main> package, C<$FooPack::a> and C<$FooPack::b> in the -C<FooPack> package, etc. If the sort block is in scope of a C<my> or -C<state> declaration of C<$a> and/or C<$b>, you I<must> spell out the full -name of the variables in the sort block : -(TBT) +C<$a> ¤È C<$b> ¤Ï¡¢sort() ¤ò¸Æ¤Ó½Ð¤·¤¿¥Ñ¥Ã¥±¡¼¥¸¤Î¥Ñ¥Ã¥±¡¼¥¸¥°¥í¡¼¥Ð¥ë¤È¤·¤Æ +ÀßÄꤵ¤ì¤Þ¤¹¡£ +¤Ä¤Þ¤ê¡¢C<main> ¥Ñ¥Ã¥±¡¼¥¸¤Î C<$main::a> ¤È C<$main::b> +(¤¢¤ë¤¤¤Ï C<$::a> ¤È C<$::b>) ¡¢ +C<FooPack> ¥Ñ¥Ã¥±¡¼¥¸¤Î C<$FooPack::a> ¤È C<$FooPack::b>¡¢¤Ê¤É¤Ç¤¹¡£ +¥½¡¼¥È¥Ö¥í¥Ã¥¯¤¬ C<$a> ¤ä C<$b> ¤Î C<my> ¤Þ¤¿¤Ï C<state> ¤Î¥¹¥³¡¼¥×Æâ¤Î¾ì¹ç¡¢ +¥½¡¼¥È¥Ö¥í¥Ã¥¯¤ÎÊÑ¿ô¤Î´°Á´Ì¾¤ò I<»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó>: package main; my $a = "C"; # DANGER, Will Robinson, DANGER !!! @@ -15824,11 +15808,12 @@ =end original -Sort subroutines written using C<$a> and C<$b> are bound to their calling -package. It is possible, but of limited interest, to define them in a -different package, since the subroutine must still refer to the calling -package's C<$a> and C<$b> : -(TBT) +C<$a> ¤È C<$b> ¤ò»È¤Ã¤Æ½ñ¤«¤ì¤¿¥½¡¼¥È¥µ¥Ö¥ë¡¼¥Á¥ó¤Ï¤½¤Î¸Æ¤Ó½Ð¤·¥Ñ¥Ã¥±¡¼¥¸¤Ë +¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ +°Û¤Ê¤ë¥Ñ¥Ã¥±¡¼¥¸¤ËÄêµÁ¤¹¤ë¤³¤È¤Ï²Äǽ¤Ç¤¹¤¬¡¢ +¤³¤ì¤Ï²Äǽ¤Ç¤¹¤¬¡¢¸Â¤é¤ì¤¿´Ø¿´¤·¤«¤¢¤ê¤Þ¤»¤ó; +¥µ¥Ö¥ë¡¼¥Á¥ó¤Ï¸Æ¤Ó½Ð¤·¥Ñ¥Ã¥±¡¼¥¸¤Î C<$a> ¤È C<$b> ¤ò +»²¾È¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤é¤Ç¤¹: package Foo; sub lexi { $Bar::a cmp $Bar::b } @@ -16098,10 +16083,9 @@ =end original -C<E<sol>m> and any of the other pattern modifiers valid for C<qr> -(summarized in L<perlop/qrE<sol>STRINGE<sol>msixpodualn>) may be -specified explicitly. -(TBT) +C<qr> ¤Ç͸ú¤Ê C<E<sol>m> µÚ¤Ó¤½¤Î¾¤Î¥Ñ¥¿¡¼¥ó½¤¾þ»Ò +(L<perlop/qrE<sol>STRINGE<sol>msixpodualn> ¤Ë¤Þ¤È¤á¤é¤ì¤Æ¤¤¤Þ¤¹) ¤Ï +ÌÀ¼¨Åª¤ËÄêµÁ¤µ¤ì¤Þ¤¹¡£ =begin original @@ -17642,14 +17626,12 @@ =end original Perl ¥Ð¡¼¥¸¥ç¥ó 5.16 ¤è¤êÁ°¤Ç¤Ï¡¢ -it would create an inverted index of all characters -that occurred in the given SCALAR (or L<C<$_>|perlvar/$_> if unspecified). -When -matching a pattern, the rarest character from the pattern would be looked up in -this index. -Rarity was based on some static frequency tables constructed from -some C programs and English text. -(TBT) +Í¿¤¨¤é¤ì¤¿ SCALAR (¤Þ¤¿¤Ï»ØÄꤵ¤ì¤Æ¤¤¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï L<C<$_>|perlvar/$_>)¤Ë +¸½¤ì¤¿Á´¤Æ¤Îʸ»ú¤ÎžÃÖ¥¤¥ó¥Ç¥Ã¥¯¥¹¤òºî¤ê¤Þ¤¹¡£ +¥Ñ¥¿¡¼¥ó¤Ë¥Þ¥Ã¥Á¥ó¥°¤·¤¿¤È¤¡¢ +¥Ñ¥¿¡¼¥óÃæ¤ÎºÇ¤âÉÑÅ٤ξ¯¤Ê¤¤Ê¸»ú¤¬¤³¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤«¤éõ¤µ¤ì¤Þ¤¹¡£ +ÉÑÅ٤ϡ¢C ¥×¥í¥°¥é¥à¤È±Ñ¸ì¤Îʸ¾Ï¤«¤é¹½ÃÛ¤µ¤ì¤¿ÀÅŪÉÑÅ٥ơ¼¥Ö¥ë¤ò +´ð¤Ë¤·¤Æ¤¤¤Þ¤¹¡£ =item sub NAME BLOCK X<sub> @@ -18329,14 +18311,13 @@ =end original -Note the emphasis on bytes: even if the filehandle has been set to operate -on characters (for example using the C<:encoding(UTF-8)> I/O layer), the +¥Ð¥¤¥Èñ°Ì¤ËÂФ¹¤ëÃí°Õ: Î㤨(Î㤨¤Ð C<:encoding(UTF-8)> I/O Áؤò»È¤¦¤Ê¤É¤·¤Æ) +¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¤¬Ê¸»úñ°Ì¤Ç½èÍý¤¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢ L<C<seek>|/seek FILEHANDLE,POSITION,WHENCE>, -L<C<tell>|/tell FILEHANDLE>, and -L<C<sysseek>|/sysseek FILEHANDLE,POSITION,WHENCE> -family of functions use byte offsets, not character offsets, -because seeking to a character offset would be very slow in a UTF-8 file. -(TBT) +L<C<tell>|/tell FILEHANDLE>, +L<C<sysseek>|/sysseek FILEHANDLE,POSITION,WHENCE> ¥·¥ê¡¼¥º¤Î´Ø¿ô¤Ï +ʸ»ú¥ª¥Õ¥»¥Ã¥È¤Ç¤Ï¤Ê¤¯¥Ð¥¤¥È¥ª¥Õ¥»¥Ã¥È¤ò»È¤¤¤Þ¤¹; +ʸ»ú¥ª¥Õ¥»¥Ã¥È¤Ç¥·¡¼¥¯¤¹¤ë¤Î¤Ï UTF-8 ¥Õ¥¡¥¤¥ë¤Ç¤Ï¤È¤Æ¤âÃÙ¤¤¤«¤é¤Ç¤¹¡£ =begin original @@ -18702,14 +18683,13 @@ =end original -Note the emphasis on bytes: even if the filehandle has been set to operate -on characters (for example using the C<:encoding(UTF-8)> I/O layer), the +¥Ð¥¤¥Èñ°Ì¤ËÂФ¹¤ëÃí°Õ: Î㤨(Î㤨¤Ð C<:encoding(UTF-8)> I/O Áؤò»È¤¦¤Ê¤É¤·¤Æ) +¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¤¬Ê¸»úñ°Ì¤Ç½èÍý¤¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢ L<C<seek>|/seek FILEHANDLE,POSITION,WHENCE>, -L<C<tell>|/tell FILEHANDLE>, and -L<C<sysseek>|/sysseek FILEHANDLE,POSITION,WHENCE> -family of functions use byte offsets, not character offsets, -because seeking to a character offset would be very slow in a UTF-8 file. -(TBT) +L<C<tell>|/tell FILEHANDLE>, +L<C<sysseek>|/sysseek FILEHANDLE,POSITION,WHENCE> ¥·¥ê¡¼¥º¤Î´Ø¿ô¤Ï +ʸ»ú¥ª¥Õ¥»¥Ã¥È¤Ç¤Ï¤Ê¤¯¥Ð¥¤¥È¥ª¥Õ¥»¥Ã¥È¤ò»È¤¤¤Þ¤¹; +ʸ»ú¥ª¥Õ¥»¥Ã¥È¤Ç¥·¡¼¥¯¤¹¤ë¤Î¤Ï UTF-8 ¥Õ¥¡¥¤¥ë¤Ç¤Ï¤È¤Æ¤âÃÙ¤¤¤«¤é¤Ç¤¹¡£ =begin original @@ -20358,12 +20338,12 @@ ʸ»úÎ󤬤ʤ¼¤«ÆâÉô¤Ç UTF-8 ¤Ç¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¾ì¹ç(¤·¤¿¤¬¤Ã¤Æ UTF8 ¥Õ¥é¥°¤¬ ¥»¥Ã¥È¤µ¤ì¤Æ¤¤¤ë¾ì¹ç)¡¢ -L<C<vec>|/vec EXPR,OFFSET,BITS> tries to convert it -to use a one-byte-per-character internal representation. However, if the -string contains characters with values of 256 or higher, that conversion -will fail. In that situation, C<vec> will operate on the underlying buffer -regardless, in its internal UTF-8 representation. -(TBT) +L<C<vec>|/vec EXPR,OFFSET,BITS> ¤Ï¤³¤ì¤òñ°ì¥Ð¥¤¥Èʸ»úÆâÉôɽ¸½¤Ë +ÊÑ´¹¤·¤è¤¦¤È¤·¤Þ¤¹¡£ +¤·¤«¤·¡¢¤³¤Îʸ»úÎó¤ËÃͤ¬ 256 °Ê¾å¤Îʸ»ú¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢ +ÊÑ´¹¤Ï¼ºÇÔ¤·¤Þ¤¹¡£ +¤³¤Î¾ì¹ç¡¢C<vec> ¤ÏÆâÉô¤Î UTF-8 ɽ¸½¤òµ¤¤Ë¤»¤º¡¢ +´ð¤È¤Ê¤Ã¤Æ¤¤¤ë¥Ð¥Ã¥Õ¥¡¤ËÂФ·¤ÆÁàºî¤·¤Þ¤¹¡£ =begin original @@ -21225,7 +21205,7 @@ Translate: µÈ¼ ¼÷¿Í <JAE00****@nifty*****> Update: SHIRAKATA Kentaro <argra****@ub32*****> (5.6.1-) -Status: in progress +Status: completed =end meta