=encoding euc-jp =head1 NAME =begin original perlport - Writing portable Perl =end original perlport - �ܿ����Τ��� Perl ��� =head1 DESCRIPTION =begin original Perl runs on numerous operating systems. While most of them share much in common, they also have their own unique features. =end original Perl ��¿���Υ��ڥ졼�ƥ��󥰥����ƥ���ư��ޤ��� �����ΤۤȤ�ɤϰ���Ū�ˤ��ʤ����ʬ��ͭ���Ƥ��ޤ��������줾���ͭ�� ��ǽ����äƤ��ޤ��� =begin original This document is meant to help you to find out what constitutes portable Perl code. That way once you make a decision to write portably, you know where the lines are drawn, and you can stay within them. =end original ����ʸ��ϰܿ����Τ��� Perl �����ɤι������Ǥ�ȯ����������ˤʤ뤿��� ��ΤǤ��� �ܿ����Τ�����ǽ񤳤��ȷ迴�����顢�ɤ�������������Ƥ��뤫���Τ뤳�Ȥǡ� ������¦��α�ޤ뤳�Ȥ��Ǥ��ޤ��� =begin original There is a tradeoff between taking full advantage of one particular type of computer and taking advantage of a full range of them. Naturally, as you broaden your range and become more diverse, the common factors drop, and you are left with an increasingly smaller area of common ground in which you can operate to accomplish a particular task. Thus, when you begin attacking a problem, it is important to consider under which part of the tradeoff curve you want to operate. Specifically, you must decide whether it is important that the task that you are coding have the full generality of being portable, or whether to just get the job done right now. This is the hardest choice to be made. The rest is easy, because Perl provides many choices, whichever way you want to approach your problem. =end original ��������μ���Υ���ԥ塼����������Ȥ����Ȥȡ��������ϰϤ� ����ԥ塼����������Ȥ����Ȥδ֤ˤϥȥ졼�ɥ��դ�����ޤ��� �����ʤ��顢����ϰϤ򹭤��Ƥ��¿�����Τ�����ˤ���ȡ����̤����Ǥ� ���äƤ���������Υ�������ã�����뤿������Ǥ��붦�̤����פ������� �������ʤäƤ����ޤ��� ���äơ�����˼�꤫����Ȥ��ˡ��ȥ졼�ɥ��դΥ����֤Τɤ���ʬ�� �Ȥ�����ͤ��뤳�ȤϽ��פǤ��� �äˡ������ǥ��󥰤��褦�Ȥ��륿�������ܿ����˴ؤ��ƴ����ʰ������� ���פ��ɤ������ޤ������˥���֤򽪤�餻�뤫�ɤ����� ���ꤷ�ʤ���Фʤ�ޤ��� �Ĥ�Τ��Ȥϴ�ñ�Ǥ��� �ʤ��ʤ餢�ʤ�������ˤɤΤ褦�˥��ץ������������Ȥ��Ƥ� Perl ��¿���� �������󶡤��뤫��Ǥ��� =begin original Looking at it another way, writing portable code is usually about willfully limiting your available choices. Naturally, it takes discipline and sacrifice to do that. The product of portability and convenience may be a constant. You have been warned. =end original �����¾����ˡ�Ǹ��Ƥߤ�ȡ��ܿ����Τ��륳���ɤ�񤯤��Ȥ��̾濫�ʤ��� �������������ΰդ����¤��ޤ��� �����ʤ��顢����ϵ�Χ�ȵ�����ȼ���ޤ��� �����餯�ܿ��������������Ѥϰ���Ǥ��� ���ʤ��Ϸٹ𤵤�ޤ����衣 =begin original Be aware of two important points: =end original ��Ĥν��פ��������դ��Ƥ�������: =over 4 =item Not all Perl programs have to be portable (���Ƥ� Perl �ץ�����ब�ܿ���������ɬ�פϤ���ޤ���) =begin original There is no reason you should not use Perl as a language to glue Unix tools together, or to prototype a Macintosh application, or to manage the Windows registry. If it makes no sense to aim for portability for one reason or another in a given program, then don't bother. =end original Unix �ġ����ߤ��ˤ��äĤ����ꡢMacintosh ���ץꥱ�������Υץ��ȥ����פ� ��ä��ꡢWindows �쥸���ȥ�����뤿��θ���Ȥ��� Perl �� �Ȥ��٤��ǤϤʤ��Ȥ�����ͳ�Ϥ���ޤ��� �ץ������ˤȤäƲ��餫����ͳ�ǰܿ�������ɸ�Ȥ��뤳�Ȥ�̵��̣�ʤ顢 ���ˤ��ʤ��Ǥ��������� =item Nearly all of Perl already I portable (�ۤȤ�����Ƥ� Perl �ϴ��˰ܿ����� I<����ޤ�>) =begin original Don't be fooled into thinking that it is hard to create portable Perl code. It isn't. Perl tries its level-best to bridge the gaps between what's available on different platforms, and all the means available to use those features. Thus almost all Perl code runs on any machine without modification. But there are some significant issues in writing portable code, and this document is entirely about those issues. =end original �ܿ����Τ��� Perl �����ɤ���Τ��񤷤��Ȥ����ͤ����٤���ʤ��Ǥ��������� �����ǤϤ���ޤ��� Perl �ϡ��ۤʤä��ץ�åȥե�����Dz������Ѳ�ǽ���Ȥ��ε�ǽ��Ȥ������ ���Ѳ�ǽ�ʤ�����ƤȤδ֤Τ��������������Ϥ����褦�Ȥ��ޤ��� ���äơ��ۤȤ�����Ƥ� Perl �����ɤϽ����ʤ��ˤɤΥޥ���Ǥ�ư��ޤ��� �������ܿ����Τ��륳���ɤ�񤯤ˤϤ����Ĥ��ν��פ����꤬���ꡢ����ʸ��� ����Ū�ˤ��Τ褦������򰷤äƤ��ޤ��� =back =begin original Here's the general rule: When you approach a task commonly done using a whole range of platforms, think about writing portable code. That way, you don't sacrifice much by way of the implementation choices you can avail yourself of, and at the same time you can give your users lots of platform choices. On the other hand, when you have to take advantage of some unique feature of a particular platform, as is often the case with systems programming (whether for Unix, Windows, S, VMS, etc.), consider writing platform-specific code. =end original ����Ū�ʥ롼���󤲤ޤ�: �ץ�åȥե��������ΤǻȤ��ư���Ū�� ���������褦�ʥ�����������Ȥ����ܿ����Τ��륳���ɤ�񤯤��Ȥ� �ͤ��Ƥ��������� ���������ǡ���ʬ���Ȥμ�����������¿�������ˤ��뤳�ȤϤʤ��� Ʊ���˥桼������¿���Υץ�åȥե������������Ϳ���뤳�Ȥ��Ǥ��ޤ��� ����������Υץ�åȥե�����Ǹ�ͭ�ε�ǽ��������Ȥ�ɬ�פ������硢 �㤨�� (Unix, Windows, S, VMS �ʤ����Ѥ�) �����ƥ�ץ������Τ褦�� ��硢�ץ�åȥե������ͭ�Υ����ɤ�񤯤��Ȥ�ͤ��Ƥ��������� =begin original When the code will run on only two or three operating systems, you may need to consider only the differences of those particular systems. The important thing is to decide where the code will run and to be deliberate in your decision. =end original �����ɤ���Ĥ����ĤΥ��ڥ졼�ƥ��󥰥����ƥ�Ǥ���ư���Ȥ��ϡ� ����������Υ����ƥ�Ǥΰ㤤�Τߤ��θ����ɬ�פ�����ޤ��� ���פʤ��Ȥϡ��ɤ��ǥ����ɤ�¹Ԥ��뤫�ȡ������Ϲͤ��뤳�ȤǤ��� =begin original The material below is separated into three main sections: main issues of portability (L<"ISSUES">), platform-specific issues (L<"PLATFORMS">), and built-in perl functions that behave differently on various ports (L<"FUNCTION IMPLEMENTATIONS">). =end original �ʲ��κ����ϻ��Ĥμ�ʾϤ�ʬ�䤵��Ƥ��ޤ�: ��ʰܿ��������� (L<"ISSUES">)���ץ�åȥե������ͭ������ (L<"PLATFORMS">)�� OS �ˤ�äưۤʤä������񤤤򤹤� perl �Ȥ߹��ߴؿ� (L<"FUNCTION IMPLEMENTATIONS">) �Ǥ��� =begin original This information should not be considered complete; it includes possibly transient information about idiosyncrasies of some of the ports, almost all of which are in a state of constant evolution. Thus, this material should be considered a perpetual work in progress (C<< Under Construction >>). =end original ���ξ���ϴ����Ǥ���ȹͤ���٤��ǤϤ���ޤ���; ����ϰ����� OS ���Ф��� �ð����˴ؤ��뤪���餯���Ū�ʾ����ޤ�Ǥ��ơ������ΤۤȤ�ɤϾ�� �ʲ����Ƥ����ΤǤ��� ���äơ����κ����ϱʱ�˺����Ǥ���ȹͤ���٤��Ǥ� (C<< Under Construction >>)�� =head1 ISSUES (����) =head2 Newlines (����) =begin original In most operating systems, lines in files are terminated by newlines. Just what is used as a newline may vary from OS to OS. Unix traditionally uses C<\012>, one type of DOSish I/O uses C<\015\012>, and S uses C<\015>. =end original �ۤȤ�ɤΥ��ڥ졼�ƥ��󥰥����ƥ�ǡ��ե�����ιԤϲ��Ԥǽ�ü����ޤ��� ñ�˲��ԤȤ��Ʋ���Ȥ����� OS �ˤ�äưۤʤ�ޤ��� Unix ������Ū�� C<\012> ��Ȥ���DOS ���� I/O �� C<\015\012> ��Ȥ��� S �� C<\015> ��Ȥ��ޤ��� =begin original Perl uses C<\n> to represent the "logical" newline, where what is logical may depend on the platform in use. In MacPerl, C<\n> always means C<\015>. In DOSish perls, C<\n> usually means C<\012>, but when accessing a file in "text" mode, STDIO translates it to (or from) C<\015\012>, depending on whether you're reading or writing. Unix does the same thing on ttys in canonical mode. C<\015\012> is commonly referred to as CRLF. =end original Perl �ϡ�����Ū�ʡײ��Ԥ�ɽ������Τ� C<\n> ��Ȥ��ޤ�; ��������Ū���� �ȤäƤ���ץ�åȥե�����˰�¸���Ƥ��ޤ��� MacPerl �Ǥ� C<\n> �Ͼ�� C<\015> ���̣���ޤ��� DOS ���� perl �Ǥϡ�C<\n> ������ C<\012> ���̣���ޤ������ե������ �֥ƥ����ȡץ⡼�ɤǥ�����������ȡ�STDIO �� C<\015\012> �Ȥδ֤� �Ѵ����ޤ��� Unix �ϥ��Υ˥���⡼�ɤ� tty ��Ʊ�����Ȥ򤷤ޤ��� C<\015\012> �ϰ���Ū�ˤ� CRLF �Ȥ��ƻ��Ȥ���ޤ��� =begin original To trim trailing newlines from text lines use chomp(). With default settings that function looks for a trailing C<\n> character and thus trims in a portable way. =end original �ƥ����ȹԤ��������β��Ԥ��ڤ���Ȥ��ˤϡ�chomp() ��Ȥ��ޤ��� ���δؿ��Υǥե��������������� C<\n> ʸ����õ���Τǡ��ܿ����Τ������ �ڤ���Ȥ��ޤ��� =begin original When dealing with binary files (or text files in binary mode) be sure to explicitly set $/ to the appropriate value for your file format before using chomp(). =end original �Х��ʥ�ե����� (�ޤ��ϥХ��ʥ�⡼�ɤǤΥƥ����ȥե�����) �򰷤��Ȥ��ˤϡ� chomp() ��Ȥ����˥ե����������Ŭ�ڤ��ͤ� $/ ������Ū�����ꤷ�Ƥ��������� =begin original Because of the "text" mode translation, DOSish perls have limitations in using C and C on a file accessed in "text" mode. Stick to C-ing to locations you got from C (and no others), and you are usually free to use C and C even in "text" mode. Using C or C or other file operations may be non-portable. If you use C on a file, however, you can usually C and C with arbitrary values in safety. =end original �֥ƥ����ȡץ⡼���Ѵ��ˤ�äơ�DOS Ū�� perl �ϡ֥ƥ����ȡץ⡼�ɤ� ������������ե�������Ф��� C �� C �λ��Ѥ����¤�����ޤ��� C ���������֤� C ����(������¾����ˡ��Ȥ�ʤ�)���Ȥ� ��ǰ���뤳�Ȥǡ��֥ƥ����ȡץ⡼�ɤǤ⼫ͳ�� C �� C �� �Ȥ��ޤ��� C �� C �䤽��¾�Υե��������ϸߴ������ʤ����⤷��ޤ��� ���������ե�������Ф��� C ��Ȥ��ȡ����̤�Ǥ�դ��ͤ� C �� C �˻ȤäƤ�����Ǥ��� =begin original A common misconception in socket programming is that C<\n> eq C<\012> everywhere. When using protocols such as common Internet protocols, C<\012> and C<\015> are called for specifically, and the values of the logical C<\n> and C<\r> (carriage return) are not reliable. =end original �����åȥץ�����ߥ󥰤ǤΤ褯�������ϡ�C<\n> �Ϥɤ��Ǥ� C<\012> �� �������Ȥ������ȤǤ��� ����Ū�ʥ��󥿡��ͥåȥץ��ȥ���Τ褦�ʥץ��ȥ����Ȥ��Ȥ��� C<\012> �� C<\015> �����Τ˵��Ҥ���Ƥ��ơ�����Ū�� C<\n> �� C<\r> (����) ���ͤϿ���Ǥ��ޤ��� print SOCKET "Hi there, client!\r\n"; # WRONG print SOCKET "Hi there, client!\015\012"; # RIGHT =begin original However, using C<\015\012> (or C<\cM\cJ>, or C<\x0D\x0A>) can be tedious and unsightly, as well as confusing to those maintaining the code. As such, the Socket module supplies the Right Thing for those who want it. =end original ��������C<\015\012> (�ޤ��� C<\cM\cJ> �ޤ��� C<\x0D\x0A>) ��Ȥ��Τ� ����Ǹ��줷�����⤷��ޤ��󤷡������ɤ��ݼ�˺��𤹤뤫�⤷��ޤ��� ���Τ褦�ʤ�ΤȤ��ơ�Socket �⥸�塼��ϵ����Ƥ��뤳�Ȥ��Ф��� ��������Τ򶡵뤷�ޤ��� use Socket qw(:DEFAULT :crlf); print SOCKET "Hi there, client!$CRLF" # RIGHT =begin original When reading from a socket, remember that the default input record separator C<$/> is C<\n>, but robust socket code will recognize as either C<\012> or C<\015\012> as end of line: =end original �����åȤ����ɤ߹���Ȥ����ǥե�������ϥ쥳���ɶ��ڤ� C<$/> �� C<\n> ������ɤ⡢��ϴ�ʥ����åȥ����ɤ� C<\012> �� C<\015\012> �� �ɤ����Ԥ������Ȥ���ǧ�����뤳�Ȥ�˺��ʤ��Ǥ�������: while () { # ... } =begin original Because both CRLF and LF end in LF, the input record separator can be set to LF and any CR stripped later. Better to write: =end original CRLF �� LF ��ξ���Ȥ� LF �ǽ���äƤ���Τǡ����ϥ쥳���ɶ��ڤ�� LF �����ꤷ�ơ��夫�� CR �����Ǥ��ޤ��� ���褯�񤯤�: use Socket qw(:DEFAULT :crlf); local($/) = LF; # not needed if $/ is already \012 while () { s/$CR?$LF/\n/; # not sure if socket uses LF or CRLF, OK # s/\015?\012/\n/; # same thing } =begin original This example is preferred over the previous one--even for Unix platforms--because now any C<\015>'s (C<\cM>'s) are stripped out (and there was much rejoicing). =end original ������� -- �㤨 Unix �ץ�åȥե�����Ǥ� -- �����Τ�Τ��褤��ΤǤ�; �ʤ��ʤ����Ƥ� C<\015> (C<\cM>) ����������(�����Ƥ���ϤȤƤ��Ф���) ����Ǥ��� =begin original Similarly, functions that return text data--such as a function that fetches a web page--should sometimes translate newlines before returning the data, if they've not yet been translated to the local newline representation. A single line of code will often suffice: =end original Ʊ�ͤˡ�-- web �ڡ������������ؿ��Τ褦�� -- �ƥ����ȥǡ������֤��ؿ��ϡ� �ޤ���������ʲ���ɽ�����Ѵ�����Ƥ��ʤ��ʤ顢�ǡ������֤����˲��Ԥ� �Ѵ�����٤����⤢��ޤ��� ���Ф��� 1 �ԤΥ����ɤǽ�ʬ�Ǥ�: $data =~ s/\015?\012/\n/g; return $data; =begin original Some of this may be confusing. Here's a handy reference to the ASCII CR and LF characters. You can print it out and stick it in your wallet. =end original �����ˤϺ��𤬤��뤫�⤷��ޤ��� �ʲ��� ASCII CR �� LF ʸ���������ʥ�ե���󥹤Ǥ��� �����������ƺ��ۤ�Ž�뤳�Ȥ��Ǥ��ޤ��� LF eq \012 eq \x0A eq \cJ eq chr(10) eq ASCII 10 CR eq \015 eq \x0D eq \cM eq chr(13) eq ASCII 13 | Unix | DOS | Mac | --------------------------- \n | LF | LF | CR | \r | CR | CR | LF | \n * | LF | CRLF | CR | \r * | CR | CR | LF | --------------------------- * text-mode STDIO =begin original The Unix column assumes that you are not accessing a serial line (like a tty) in canonical mode. If you are, then CR on input becomes "\n", and "\n" on output becomes CRLF. =end original Unix ����ϡ����Υ˥���⡼�ɤ�(tty �Τ褦��)���ꥢ�륤�󥿡��ե������� �����������Ƥ���ΤǤϤʤ����Ȥ��ꤷ�Ƥ��ޤ��� �⤷�����ʤ顢���Ϥ� CR �� "\n" �ˤʤꡢ���Ϥ� "\n" �� CRLF �ˤʤ�ޤ��� =begin original These are just the most common definitions of C<\n> and C<\r> in Perl. There may well be others. For example, on an EBCDIC implementation such as z/OS (OS/390) or OS/400 (using the ILE, the PASE is ASCII-based) the above material is similar to "Unix" but the code numbers change: =end original ������ñ�� Perl �ǤΤ�äȤ����Ū�� C<\n> �� C<\r> ������Ǥ��� ¾�Τ�Τ⤢�����ޤ��� �㤨�С�z/OS (OS/390) �� OS/400 (ILE ��ȤäƤ�����; PASE �� ASCII �١���) �Τ褦�� EBCDIC �����Ǥϡ���Ҥλ����� "Unix" ��Ʊ�ͤǤ����� �������ֹ椬�ѹ�����ޤ�: LF eq \025 eq \x15 eq \cU eq chr(21) eq CP-1047 21 LF eq \045 eq \x25 eq chr(37) eq CP-0037 37 CR eq \015 eq \x0D eq \cM eq chr(13) eq CP-1047 13 CR eq \015 eq \x0D eq \cM eq chr(13) eq CP-0037 13 | z/OS | OS/400 | ---------------------- \n | LF | LF | \r | CR | CR | \n * | LF | LF | \r * | CR | CR | ---------------------- * text-mode STDIO =head2 Numbers endianness and Width (���ͤΥ���ǥ��������) =begin original Different CPUs store integers and floating point numbers in different orders (called I) and widths (32-bit and 64-bit being the most common today). This affects your programs when they attempt to transfer numbers in binary format from one CPU architecture to another, usually either "live" via network connection, or by storing the numbers to secondary storage such as a disk file or tape. =end original CPU ���ۤʤ�ȡ���������ư���������ν�� (I<����ǥ�����> (endianness) �� �ƤФ�ޤ�) ���� (�Ƕ�ǤϤۤȤ�� 32 �ӥåȤ� 64 �ӥåȤǤ�) ���ۤʤ�ޤ��� ����ϡ����� CPU �������ƥ����㤫��¾�Τ�Τؿ��ͤ�Х��ʥ�����ǡ� ���̤ϥͥåȥ����³��ͳ�ǡ֥饤�֡פǡ��ޤ��ϥǥ������ե������ �ơ��פΤ褦���󼡥��ȥ졼�����ݴɤ��뤳�Ȥǰܤ����Ȥ����Ȥ��� �ƶ����ޤ��� =begin original Conflicting storage orders make utter mess out of the numbers. If a little-endian host (Intel, VAX) stores 0x12345678 (305419896 in decimal), a big-endian host (Motorola, Sparc, PA) reads it as 0x78563412 (2018915346 in decimal). Alpha and MIPS can be either: Digital/Compaq used/uses them in little-endian mode; SGI/Cray uses them in big-endian mode. To avoid this problem in network (socket) connections use the C and C formats C and C, the "network" orders. These are guaranteed to be portable. =end original �ݴɤν�����ϤȤ�����ͤ������ˤ��������ʤ�ޤ��� ��ȥ륨��ǥ�����Υۥ��� (Intel, VAX) �� 0x12345678 (10 �ʿ��Ǥ� 305419896) ���ݴɤ���ȡ��ӥå�����ǥ�����Υۥ��� (Motorola, Sparc, PA) �� ����� 0x78563412 (10 �ʿ��Ǥ� 2018915346) �Ȥ����ɤ߹��ߤޤ��� Alpha �� MIPS �Ϥɤ���⤢�����ޤ�: Digital/Compaq �Ϥ���� ��ȥ륨��ƥ�����⡼�ɤǻȤ��ޤ�; SGI/Cray �Ϥ���� �ӥå�����ǥ�����⡼�ɤǻȤ��ޤ��� �ͥåȥ��(�����å�)��³�Ǥ���������򤱤�ˤϡ�C �� C �� �֥ͥåȥ���׽���ե����ޥåȤǤ��� C ����� C ��ȤäƤ��������� �����ϰܿ��������뤳�Ȥ��ݾڤ��ޤ��� =begin original As of perl 5.9.2, you can also use the C> and C> modifiers to force big- or little-endian byte-order. This is useful if you want to store signed integers or 64-bit integers, for example. =end original perl 5.9.2 ���顢�ӥå�����ǥ�����ȥ�ȥ륨��ǥ�����˥Х��Ƚ�� �������뤿��� C> �� C> �ν����Ҥ�Ȥ��ޤ��� ������㤨�С�����դ������� 64 �ӥå��������ݴɤ������Ȥ���ͭ�ѤǤ��� =begin original You can explore the endianness of your platform by unpacking a data structure packed in native format such as: =end original ���Τ褦�ˡ��ͥ��ƥ��֤ʷ����� pack ���줿�ǡ�����¤�� unpack ���뤳�Ȥ� �ץ�åȥե�����Υ���ǥ������Ĵ�٤뤳�Ȥ��Ǥ��ޤ�: print unpack("h*", pack("s2", 1, 2)), "\n"; # '10002000' on e.g. Intel x86 or Alpha 21064 in little-endian mode # '00100020' on e.g. Motorola 68040 =begin original If you need to distinguish between endian architectures you could use either of the variables set like so: =end original ����ǥ����󥢡����ƥ��������̤���ɬ�פ�����ʤ顢�ʲ��Τ褦���ѿ��� �ɤ��餫��Ȥ��ޤ�: $is_big_endian = unpack("h*", pack("s", 1)) =~ /01/; $is_little_endian = unpack("h*", pack("s", 1)) =~ /^1/; =begin original Differing widths can cause truncation even between platforms of equal endianness. The platform of shorter width loses the upper parts of the number. There is no good solution for this problem except to avoid transferring or storing raw binary numbers. =end original ���ΰ㤤��Ʊ������ǥ�����Υץ�åȥե�����δ֤Ǥ��ڤ�ͤ�� �������������Ȥ�����ޤ��� �������û��¦�Υץ�åȥե�����Ͽ��ͤξ����ʬ�򼺤��ޤ��� ���ΥХ��ʥ���ͤ�ž���������ݴɤ����ꤷ�ʤ��褦�ˤ���ʳ��ˡ���������ؤ� �褤���ˡ�Ϥ���ޤ��� =begin original One can circumnavigate both these problems in two ways. Either transfer and store numbers always in text format, instead of raw binary, or else consider using modules like Data::Dumper (included in the standard distribution as of Perl 5.005) and Storable (included as of perl 5.8). Keeping all data as text significantly simplifies matters. =end original �������������Ĥ���ˡ���򤱤뤳�Ȥ�����ޤ��� ���ͤ������ΥХ��ʥ�ǤϤʤ��ƥ����ȷ�����ž�������ݴɤ��뤫�� (Perl 5.005 ����ɸ�����ۤ˴ޤޤ�Ƥ���) Data::Dumper �� (perl 5.8 ���� �ޤޤ�Ƥ���) Storable �Τ褦�ʥ⥸�塼���Ȥ����Ȥ��θ���ޤ��� ���ƤΥǡ�����ƥ����Ȥǰ������Ȥ�����򤫤ʤ�ñ�㲽���ޤ��� =begin original The v-strings are portable only up to v2147483647 (0x7FFFFFFF), that's how far EBCDIC, or more precisely UTF-EBCDIC will go. =end original v-ʸ����� v2147483647 (0x7FFFFFFF) �ʲ��ǤΤ߰ܿ���������ޤ�; ����� EBCDIC��������Τˤ� UTF-EBCDIC ���������˱󤤤Ǥ��� =head2 Files and Filesystems (�ե�����ȥե����륷���ƥ�) =begin original Most platforms these days structure files in a hierarchical fashion. So, it is reasonably safe to assume that all platforms support the notion of a "path" to uniquely identify a file on the system. How that path is really written, though, differs considerably. =end original �Ƕ�ΤۤȤ�ɤΥץ�åȥե�����Ǥϥե�����ι�¤�ϳ���Ū�Ǥ��� ���äơ����ƤΥץ�åȥե����ब�����ƥ���Υե�������ˡ����� ���̤��뤿��Ρ֥ѥ��׵�ˡ���б����Ƥ���Ȳ��ꤹ�뤳�ȤϹ���Ū�˰����Ǥ��� �ѥ����ºݤˤɤΤ褦�˽񤫤�뤫�Ϥ��ʤ�ۤʤ�ޤ��� =begin original Although similar, file path specifications differ between Unix, Windows, S, OS/2, VMS, VOS, S, and probably others. Unix, for example, is one of the few OSes that has the elegant idea of a single root directory. =end original ���ƤϤ����ΤΡ��ե�����ѥ��λ�����ˡ�� Unix, Windows, S, OS/2, VMS, VOS, S �����Ƥ����餯����¾�� �ۤʤ�ޤ��� �㤨�С�Unix �ϰ�ĤΥ롼�ȥǥ��쥯�ȥ�Ȥ������쥬��Ȥʹͤ�������� �����ʤ� OS �ΰ�ĤǤ��� =begin original DOS, OS/2, VMS, VOS, and Windows can work similarly to Unix with C as path separator, or in their own idiosyncratic ways (such as having several root directories and various "unrooted" device files such NIL: and LPT:). =end original DOS, OS/2, VMS, VOS, Windows �� C ��ѥ����ڤ�Ȥ��ơ�(ʣ���� �롼�ȥǥ��쥯�ȥ�䡢NIL: �� LPT: �Τ褦���͡��ʡ֥롼�ȤǤʤ��� �ǥХ����ե�����Ȥ��ä�)�ȼ������Ѥ�����ˡ�� Unix �Ȼ����褦�� ư��ޤ��� =begin original S uses C<:> as a path separator instead of C. =end original S �ϥѥ����ڤ�� C �ǤϤʤ� C<:> ��Ȥ��ޤ��� =begin original The filesystem may support neither hard links (C) nor symbolic links (C, C, C). =end original �ե����륷���ƥ�ϥϡ��ɥ�� (C) �䥷��ܥ�å���� (C, C, C) ���б����Ƥ��ʤ����⤷��ޤ��� =begin original The filesystem may support neither access timestamp nor change timestamp (meaning that about the only portable timestamp is the modification timestamp), or one second granularity of any timestamps (e.g. the FAT filesystem limits the time granularity to two seconds). =end original �ե����륷���ƥ�ϥ������������ॹ����פ��ѹ������ॹ����פ� �б����Ƥ��ʤ����⤷��ޤ��� (�Ĥޤ�ܿ����Τ��륿���ॹ����פ� �ѹ������ॹ����פ����Ǥ�); �ޤ������ॹ����פ� 1 ��ñ�̤Ǥ� �ʤ����⤷��ޤ��� (�㤨�С�FAT �ե����륷���ƥ�ϻ����ñ�̤� 2 ��ñ�̤Ǥ�)�� =begin original The "inode change timestamp" (the C<-C> filetest) may really be the "creation timestamp" (which it is not in UNIX). =end original ��inode �ѹ������ॹ����ס� (C<-C> �ե�����ƥ���) �� (UNIX �ʳ��Ǥ�) �ºݤˤϡֺ��������ॹ����ספ��⤷��ޤ��� =begin original VOS perl can emulate Unix filenames with C as path separator. The native pathname characters greater-than, less-than, number-sign, and percent-sign are always accepted. =end original VOS perl �� C ��ѥ����ڤ�Ȥ��� Unix �ե�����̾�򥨥ߥ�졼�ȤǤ��ޤ��� �ͥ��ƥ��֤ʥѥ�̾ʸ���Ǥ�����ʤꡢ���ʤꡢ���㡼�ס��ѡ�����ȤϾ�� ����������ޤ��� =begin original S perl can emulate Unix filenames with C as path separator, or go native and use C<.> for path separator and C<:> to signal filesystems and disk names. =end original S perl �� C ��ѥ����ڤ�Ȥ��� Unix �ե�����̾�򥨥ߥ�졼�� ���뤫���ͥ��ƥ��֤Τޤޤ� C<.> ��ѥ����ڤꡢC<:> ��ե����륷���ƥ�� �ǥ�������̾���Ȥ��ƻȤ��ޤ��� =begin original Don't assume UNIX filesystem access semantics: that read, write, and execute are all the permissions there are, and even if they exist, that their semantics (for example what do r, w, and x mean on a directory) are the UNIX ones. The various UNIX/POSIX compatibility layers usually try to make interfaces like chmod() work, but sometimes there simply is no good mapping. =end original UNIX �Υե����륷���ƥॢ�������ΰ�̣���ꤷ�ʤ��Dz�����: �ɤ߹��ߡ� �񤭹��ߡ��¹ԤΤɤ��Ǥ�; ���Ȥ����ä��Ȥ��Ƥ⡢���ΰ�̣�� (�㤨�Хǥ��쥯�ȥ���Ф��� r, w, x �����򤹤뤫) �� UNIX �Τ�ΤǤ��� �͡��� UNIX/POSIX �ߴ��ؤ����� chmod() �Τ褦�ʤ�Τ�ư��뤿��� ���󥿡��ե������ȤʤäƤ��ޤ������Ȥ��ɤ�ñ�ˤ����ޥåԥ󥰤� �ʤ����Ȥ⤢��ޤ��� =begin original If all this is intimidating, have no (well, maybe only a little) fear. There are modules that can help. The File::Spec modules provide methods to do the Right Thing on whatever platform happens to be running the program. =end original �⤷��������Ƥ������������ΤǤ���ʤ顢����ʤ��Ǥ�������(������¿ʬ �ۤ�ξ�����������Ƥ�������)�� �����ˤʤ�⥸�塼�뤬����ޤ��� File::Spec �⥸�塼��ϥץ�����ब�ɤΥץ�åȥե������ư��Ƥ��Ƥ� �����������ȡפ򤷤ޤ��� use File::Spec::Functions; chdir(updir()); # go up one directory $file = catfile(curdir(), 'temp', 'file.txt'); # on Unix and Win32, './temp/file.txt' # on Mac OS, ':temp:file.txt' # on VMS, '[.temp]file.txt' =begin original File::Spec is available in the standard distribution as of version 5.004_05. File::Spec::Functions is only in File::Spec 0.7 and later, and some versions of perl come with version 0.6. If File::Spec is not updated to 0.7 or later, you must use the object-oriented interface from File::Spec (or upgrade File::Spec). =end original File::Spec �ϥС������ 5.004_05 ����ɸ�����ۤ����Ѳ�ǽ�Ǥ��� File::Spec::Functions �� File::Spec 0.7 �ʹߤΤߤˤ��ꡢ�����ΥС������� perl �ϥС������ 0.6 ��ޤ�Ǥ��ޤ��� File::Spec �� 0.7 �ʹߤ˹�������Ƥ��ʤ��ʤ顢File::Spec �� ���֥������Ȼظ����󥿡��ե�������Ȥ�ʤ���Фʤ�ޤ��� (���뤤�� File::Spec �򹹿����ʤ���Фʤ�ޤ���)�� =begin original In general, production code should not have file paths hardcoded. Making them user-supplied or read from a configuration file is better, keeping in mind that file path syntax varies on different machines. =end original ����Ū�ˡ����ʥ����ɤϥե�����ѥ���ϡ��ɥ����ǥ��󥰤���٤��Ǥ� ����ޤ��� �桼����������Ǥ���褦�ˤ��뤫������ե����뤫���ɤ߹��������褤�Ǥ�; �ե�����ѥ���ʸˡ�ϥޥ���ˤ�äưۤʤ뤳�Ȥ�˺��ʤ��Ǥ��������� =begin original This is especially noticeable in scripts like Makefiles and test suites, which often assume C as a path separator for subdirectories. =end original ����ϡ����Ф��� C �����֥ǥ��쥯�ȥ�Υѥ����ڤ�Ȳ��ꤵ��Ƥ��� Makefile ��ƥ��ȥ������ȤΤ褦�ʥ�����ץȤ��ä����դ�ɬ�פǤ��� =begin original Also of use is File::Basename from the standard distribution, which splits a pathname into pieces (base filename, full path to directory, and file suffix). =end original �⤦��Ĥ�ͭ�Ѥʤ�Τ�ɸ�����ۤ˴ޤޤ�Ƥ��� File::Basename �ǡ������ �ѥ�̾��١����ե�����̾���ǥ��쥯�ȥ�Υե�ѥ����ե�����γ�ĥ�Ҥ� ʬ�򤷤ޤ��� =begin original Even when on a single platform (if you can call Unix a single platform), remember not to count on the existence or the contents of particular system-specific files or directories, like F, F, F, or even F. For example, F may exist but not contain the encrypted passwords, because the system is using some form of enhanced security. Or it may not contain all the accounts, because the system is using NIS. If code does need to rely on such a file, include a description of the file and its format in the code's documentation, then make it easy for the user to override the default location of the file. =end original ñ��Υץ�åȥե�����Ǥ���(Unix ��ñ��Υץ�åȥե�����ȸƤ֤ʤ�)�� F, F, F ���뤤�� F �Ǥ���������Υ����ƥ��ͭ�Υե������ǥ��쥯�ȥ��¸�ߤ� �������Ƥ����ƤˤǤ��ʤ����Ȥ�˺��ʤ��Ǥ��������� �㤨�С�F ��¸�ߤ��뤫�⤷��ޤ��󤬡������ƥब������ �������줿�������ƥ���ȤäƤ��뤿��ˡ��Ź沽���줿�ѥ���ɤ� �ޤ�Ǥ��ʤ����⤷��ޤ��� ���뤤�ϡ�NIS ��ȤäƤ��뤿��ˡ����ƤΥ�������Ȥ� �ޤ�Ǥ��ʤ����⤷��ޤ��� �����ɤ����Τ褦�ʥե�����˰�¸����ɬ�פ������硢�����ɤ�ʸ��� �ե�����������Ȥ��η�����ޤ�ơ��桼�������ե�����Υǥե���Ȥΰ��֤� ��ñ�˾�񤭤Ǥ���褦�ˤ��ޤ��� =begin original Don't assume a text file will end with a newline. They should, but people forget. =end original �ƥ����ȥե����뤬���Ԥǽ���äƤ���Ȳ��ꤷ�ʤ��Ǥ��������� ��������٤��Ǥ������ͤ�˺��ޤ��� =begin original Do not have two files or directories of the same name with different case, like F and F, as many platforms have case-insensitive (or at least case-forgiving) filenames. Also, try not to have non-word characters (except for C<.>) in the names, and keep them to the 8.3 convention, for maximum portability, onerous a burden though this may appear. =end original F �� F �Τ褦�ʡ���ʸ���Ⱦ�ʸ�����㤦������̾������Ĥ� �ե������ǥ��쥯�ȥ����ʤ��Ǥ�������; ¿���Υץ�åȥե������ ��ʸ����ʸ����̵�뤹��(���뤤�Ͼ��ʤ��Ȥ���ʸ����ʸ���˴��Ƥ�) �ե�����̾����Ĥ���Ǥ��� �ޤ�������¤θߴ����Τ��ᡢ�����뤫���Τ�ʤ������Τ���ˡ� (C<.> �ʳ���)��ñ��ʸ����Ȥ�ʤ��褦�ˤ��ơ�8.3 �ε����ݻ����Ƥ��������� =begin original Likewise, when using the AutoSplit module, try to keep your functions to 8.3 naming and case-insensitive conventions; or, at the least, make it so the resulting files have a unique (case-insensitively) first 8 characters. =end original Ʊ�ͤˡ�AutoSplit �⥸�塼���Ȥ���硢�ؿ��� 8.3 ��̿̾����ʸ����ʸ���� ̵�뤹�뵬���ݻ�����褦�ˤ��Ƥ�������; ���뤤�ϡ����ʤ��Ȥ⡢ ��̤Υե����뤬�ǽ�� 8 ʸ����(��ʸ����ʸ����̵�뤷��)��ˡ����� �ʤ�褦�ˤ��Ƥ��������� =begin original Whitespace in filenames is tolerated on most systems, but not all, and even on systems where it might be tolerated, some utilities might become confused by such whitespace. =end original �ե�����̾�ζ���ϤۤȤ�ɤΥ����ƥ�ǵ��Ƥ���ޤ��������ƤǤϤʤ��� ���Ƥ��Ƥ��륷���ƥ�Ǥ⡢���Τ褦�ʶ���ˤ�äƺ��𤹤�桼�ƥ���ƥ��� ����ޤ��� =begin original Many systems (DOS, VMS ODS-2) cannot have more than one C<.> in their filenames. =end original ¿���Υ����ƥ� (DOS, VMS ODS-2) �ϥե�����̾����İʾ�� C<.> �� �Ȥ��ޤ��� =begin original Don't assume C<< > >> won't be the first character of a filename. Always use C<< < >> explicitly to open a file for reading, or even better, use the three-arg version of open, unless you want the user to be able to specify a pipe open. =end original C<< > >> ���ե�����̾�κǽ��ʸ���ǤϤʤ��Ȳ��ꤷ�ʤ��Ǥ��������� �桼�������ѥ��פdz�����褦�ˤ������ΤǤʤ��¤ꡢ�ɤ߹��ߤΤ���˥ե������ �����Ȥ��ˤϾ������Ū�� C<< < >> ��Ȥ�������äȤ褤�Τϡ�3 �����Ǥ� open ��ȤäƤ��������� open(FILE, '<', $existing_file) or die $!; =begin original If filenames might use strange characters, it is safest to open it with C instead of C. C is magic and can translate characters like C<< > >>, C<< < >>, and C<|>, which may be the wrong thing to do. (Sometimes, though, it's the right thing.) Three-arg open can also help protect against this translation in cases where it is undesirable. =end original �⤷�ե�����̾�ˤ�������ʸ�����Ȥ��Ƥ��뤫���Τ�ʤ��ʤ顢 C �ǤϤʤ� C ��ȤäƳ����Τ���äȤ�����Ǥ��� C �ϥޥ�����ǡ�C<< > >>, C<< < >>, C<|> �Τ褦��ʸ���� �Ѵ����뤳�Ȥ����ꡢ����ϴְ�ä����Ȥ��⤷��ޤ��� (�������������ϡ���������������ȤǤ���) 3 ���������� open ��ͽ�ۤ��Ƥ��ʤ������Ǥ����Ѵ�����������ˤʤ�ޤ��� =begin original Don't use C<:> as a part of a filename since many systems use that for their own semantics (Mac OS Classic for separating pathname components, many networking schemes and utilities for separating the nodename and the pathname, and so on). For the same reasons, avoid C<@>, C<;> and C<|>. =end original C<:> ��ե�����̾�ΰ����Ȥ��ƻȤ�ʤ��Ǥ�������; ¿���Υ����ƥब����� Ʊ���ΰ�̣�ǻȤäƤ��뤫��Ǥ� (Mac OS Classic �ϥѥ�̾���Ǥ�ʬ�䤹�뤿��ˡ� ¿���Υͥåȥ����������ȥ桼�ƥ���ƥ��ǤϥΡ���̾�ȥѥ�̾�� ʬ�䤹�뤿��ˡ��ʤ�)�� Ʊ����ͳ�ǡ�C<@>, C<;>, C<|> ���򤱤Ƥ��������� =begin original Don't assume that in pathnames you can collapse two leading slashes C into one: some networking and clustering filesystems have special semantics for that. Let the operating system to sort it out. =end original �ѥ�̾����Ƭ����ĤΥ���å��� C ���Ĥ˰��̤Ǥ���� ���ꤷ�ʤ��Ǥ�������: �����Υͥåȥ���󥰤ȥ��饹����󥰤� �ե����륷���ƥ�Ϥ�����Ф������̤ʰ�̣��������ޤ��� ���ڥ졼�ƥ��󥰥����ƥ��Ǥ���Ƥ��������� =begin original The I as defined by ANSI C are =end original ANSI C ���������Ƥ��롢I<�ܿ����Τ���ե�����̾��ʸ��> ��: a b c d e f g h i j k l m n o p q r t u v w x y z A B C D E F G H I J K L M N O P Q R T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 . _ - =begin original and the "-" shouldn't be the first character. If you want to be hypercorrect, stay case-insensitive and within the 8.3 naming convention (all the files and directories have to be unique within one directory if their names are lowercased and truncated to eight characters before the C<.>, if any, and to three characters after the C<.>, if any). (And do not use C<.>s in directory names.) =end original ���� "-" �Ϻǽ��ʸ���ˤϻȤ��ޤ��� �⤷Ķ�����ˤ������ʤ顢��ʸ����ʸ����̵�뤷�ơ�8.3 ̿̾����˽����ޤ� (���ƤΥե�����ȥǥ��쥯�ȥ�ϡ�̾����ʸ���ˤ��ơ�(�⤷�����) C<.> �� ���� 8 ʸ���� (�⤷�����) C<.> �θ�� 3 ʸ�����ڤ�ͤ᤿�Ȥ��ˡ� �ǥ��쥯�ȥ���ǥ�ˡ����Ǥ���ɬ�פ�����ޤ�)�� (�����ƥǥ��쥯�ȥ�̾�� C<.> ��Ȥ�ʤ��Ǥ���������) =head2 System Interaction (�����ƥ����ߺ���) =begin original Not all platforms provide a command line. These are usually platforms that rely primarily on a Graphical User Interface (GUI) for user interaction. A program requiring a command line interface might not work everywhere. This is probably for the user of the program to deal with, so don't stay up late worrying about it. =end original ���ƤΥץ�åȥե����ब���ޥ�ɥ饤����󶡤��Ƥ���櫓�ǤϤ���ޤ��� ���������̥桼�����Ȥ���ߺ��Ѥ˥���ե�����桼�������󥿡��ե����� (GUI) �˴���Ū�˰�¸���Ƥ��ޤ��� ���ޥ�ɥ饤�󥤥󥿡��ե��������׵᤹��ץ������Ϥɤ��Ǥ� ư���櫓�ǤϤ���ޤ��� ����Ϥ����餯�ץ������򰷤��桼����������ʤΤǡ����ۤ����٤��ޤ� �٤��ޤǵ����Ƥ��ʤ��Ǥ��������� =begin original Some platforms can't delete or rename files held open by the system, this limitation may also apply to changing filesystem metainformation like file permissions or owners. Remember to C files when you are done with them. Don't C or C an open file. Don't C or C a file already tied or opened; C or C it first. =end original �����Υץ�åȥե�����ϥ����ƥ�ˤ�äƳ�����Ƥ���ե���������ޤ��� ��͡���Ǥ��ޤ���; �������¤ϥե����븢�¤��ͭ�ԤΤ褦�� �ե����륷���ƥ�Υ᥿������ѹ��ˤ�Ŭ�Ѥ���뤳�Ȥ⤢��ޤ��� �ե�������Ф����Ȥ�����ä��顢C ���뤳�Ȥ�˺��ʤ��Ǥ��������� �����Ƥ���ե�������Ф��� C �ޤ��� C ���ʤ��Ǥ��������� ���Ǥ� tie ����Ƥ����곫����Ƥ����ꤹ��ե�������Ф��� C �� C �򤷤ʤ��Dz�����; �ޤ� C �ޤ��� C ���Ƥ��������� =begin original Don't open the same file more than once at a time for writing, as some operating systems put mandatory locks on such files. =end original Ʊ���ե������Ʊ���� 2 ��ʾ�񤭹��ߤΤ���˳����ƤϤ����ޤ���; �����Υ��ڥ졼�ƥ��󥰥����ƥ�Ϥ��Τ褦�ʥե��������¾Ū���å���ݤ��ޤ��� =begin original Don't assume that write/modify permission on a directory gives the right to add or delete files/directories in that directory. That is filesystem specific: in some filesystems you need write/modify permission also (or even just) in the file/directory itself. In some filesystems (AFS, DFS) the permission to add/delete directory entries is a completely separate permission. =end original �ǥ��쥯�ȥ�ؤν񤭹���/�������¤�����С����Υǥ��쥯�ȥ�ˤ��� �ե�����/�ǥ��쥯�ȥ���ɲäޤ��Ϻ���Ǥ���Ȳ��ꤷ�ʤ��Ǥ��������� ����ϥե����륷���ƥ��¸�Ǥ�: ���Υե�����/�ǥ��쥯�ȥ꼫�Ȥ� �񤭹���/�������¤�(���뤤�Ϥ��������)ɬ�פʥե����륷���ƥ�⤢��ޤ��� �����Υե����륷���ƥ� (AFS, DFS) �Ǥϡ��ǥ��쥯�ȥ����Ǥ��ɲ�/������¤� �������̤θ��¤Ǥ��� =begin original Don't assume that a single C completely gets rid of the file: some filesystems (most notably the ones in VMS) have versioned filesystems, and unlink() removes only the most recent one (it doesn't remove all the versions because by default the native tools on those platforms remove just the most recent version, too). The portable idiom to remove all the versions of a file is =end original 1 ��� C �Ǵ����˥ե�������������Ȳ��ꤷ�ʤ��Ǥ�������: �����Υե����륷���ƥ� (��äȤ⸲���ʤ�Τ� VMS) �ϥС������������줿 �ե����륷���ƥ�������unlink() ��ñ�˺ǿ��Τ�Τ����������ޤ� (�ǥե���ȤǤϥͥ��ƥ��֤ʥġ����ñ�˺ǿ��ΥС�������������Τǡ� ���ƤΥС������Ϻ�����ޤ���)�� ����ե���������ƤΥС������������뤿��ΰܿ����Τ��봷�Ѷ��: 1 while unlink "file"; =begin original This will terminate if the file is undeleteable for some reason (protected, not there, and so on). =end original ����� (�ݸ��Ƥ��롢¸�ߤ��ʤ����ʤ�) ���餫����ͳ�ǥե����뤬 ����Ǥ��ʤ��Ȥ��˽�λ���ޤ��� =begin original Don't count on a specific environment variable existing in C<%ENV>. Don't count on C<%ENV> entries being case-sensitive, or even case-preserving. Don't try to clear %ENV by saying C<%ENV = ();>, or, if you really have to, make it conditional on C<$^O ne 'VMS'> since in VMS the C<%ENV> table is much more than a per-process key-value string table. =end original ����δĶ��ѿ��� C<%ENV> �ˤ���Ȥ������Ȥ�׻�������ʤ��Ǥ��������� C<%ENV> �Υ���ȥ꤬��ʸ����ʸ����ǧ�����뤫�䡢��ʸ����ʸ���� ��¸����뤫�����׻�������ʤ��Ǥ��������� %ENV �򥯥ꥢ���뤿��� C<%ENV = ();> �Ȥ��ʤ��Ǥ�������; �⤷ �����ˤ�������ɬ�פ�����ʤ顢C<$^O ne 'VMS'> �Ȥ�������դ��� �ԤäƤ�������; VMS �Ǥ� C<%ENV> �ơ��֥�ϥץ�����ñ�̤Υ���/��ʸ���� �ơ��֥�ʾ�Τ�Τ�����Ǥ��� =begin original On VMS, some entries in the %ENV hash are dynamically created when their key is used on a read if they did not previously exist. The values for C<$ENV{HOME}>, C<$ENV{TERM}>, C<$ENV{HOME}>, and C<$ENV{USER}>, are known to be dynamically generated. The specific names that are dynamically generated may vary with the version of the C library on VMS, and more may exist than is documented. =end original VMS �Ǥϡ�%ENV �ϥå���ΰ����Υ���ȥ�ϡ��������ޤ�¸�ߤ��Ƥ��ʤ���С� �ɤ߹��ߤ˻Ȥ�줿�Ȥ���ưŪ�˺�������ޤ��� C<$ENV{HOME}>, C<$ENV{TERM}>, C<$ENV{HOME}>, and C<$ENV{USER}> ���ͤ� ưŪ�˺����������Τ��Ƥ��ޤ��� ưŪ�˺�����������Ū��̾���� VMS �� C �饤�֥��ΥС������ˤ�ä� �ۤʤꡢʸ�񲽤���Ƥ����Τ��⤿�����󤢤뤫�⤷��ޤ��� =begin original On VMS by default, changes to the %ENV hash are persistent after the process exits. This can cause unintended issues. =end original VMS �Υǥե���ȤǤϡ�%ENV �ϥå���ؤ��ѹ��ϡ��ץ���������λ������� ��³�����ޤ��� ����ϰտޤ��Ƥ��ʤ������������������⤷��ޤ��� =begin original Don't count on signals or C<%SIG> for anything. =end original �����ʥ�� C<%SIG> �ˤĤ��Ʋ������Ƥˤ��ʤ��Dz������� =begin original Don't count on filename globbing. Use C, C, and C instead. =end original �ե�����̾�Υ����֤����Ƥˤ��ʤ��Dz������� ����� C, C, C ��ȤäƤ��������� =begin original Don't count on per-program environment variables, or per-program current directories. =end original �ץ������ñ�̤δĶ��ѿ��䡢�ץ������ñ�̤Υ����ȥǥ��쥯�ȥ�� ���Ƥˤ��ʤ��Dz������� =begin original Don't count on specific values of C<$!>, neither numeric nor especially the strings values-- users may switch their locales causing error messages to be translated into their languages. If you can trust a POSIXish environment, you can portably use the symbols defined by the Errno module, like ENOENT. And don't trust on the values of C<$!> at all except immediately after a failed system call. =end original C<$!> ��������ͤ�׻�������ʤ��Ǥ�������; ���ͤǤ⡢�ä�ʸ�����ͤǤ� �Ǥ� -- �桼�����ϼ�ʬ�θ�����������뤿��˥��顼��å���������������� ����������ѹ����뤫�⤷��ޤ��� �⤷ POSIX Ū�ʴĶ����ѤǤ���ʤ顢ENOENT �Τ褦�ʡ�Errno �⥸�塼��� �������Ƥ��륷��ܥ��ܿ�������äƻȤ��ޤ��� �����ơ������ƥॳ���뤬���Ԥ���ľ��ʳ��Ǥ� C<$!> ���ͤ����� ���Ѥ��ʤ��Ǥ��������� =head2 Command names versus file pathnames (���ޥ��̾���ե�����ѥ�̾��) =begin original Don't assume that the name used to invoke a command or program with C or C can also be used to test for the existence of the file that holds the executable code for that command or program. First, many systems have "internal" commands that are built-in to the shell or OS and while these commands can be invoked, there is no corresponding file. Second, some operating systems (e.g., Cygwin, DJGPP, OS/2, and VOS) have required suffixes for executable files; these suffixes are generally permitted on the command name but are not required. Thus, a command like "perl" might exist in a file named "perl", "perl.exe", or "perl.pm", depending on the operating system. The variable "_exe" in the Config module holds the executable suffix, if any. Third, the VMS port carefully sets up $^X and $Config{perlpath} so that no further processing is required. This is just as well, because the matching regular expression used below would then have to deal with a possible trailing version number in the VMS file name. =end original C �� C �ǥ��ޥ�ɤ�ץ�������ư���뤿��˻Ȥ�줿̾������ ���Υ��ޥ�ɤ�ץ������μ¹Բ�ǽ�����ɤ��ݻ����Ƥ���ե������¸�ߤ� �ƥ��Ȥˤ�Ȥ���Ȳ��ꤷ�ʤ��Ǥ��������� 1 ���ܤˡ�¿���Υ����ƥ�ϥ������ OS ���Ȥ߹��ޤ�Ƥ���������ץ��ޥ�ɤ� �����������Υ��ޥ�ɤϵ�ư�Ǥ��ޤ������б�����ե�����Ϥ���ޤ��� 2 ���ܤˡ������Υ��ڥ졼�ƥ��󥰥����ƥ�(�㤨�� Cygwin, DJGPP, OS/2, VOS) �� �¹ԥե�����˳�ĥ�Ҥ�ɬ�פǤ�; �����γ�ĥ�Ҥϰ���Ū�˥��ޥ��̾�Ȥ��� ��뤵��Ƥ��ޤ����׵ᤵ��ƤϤ��ޤ��� ���äơ�"perl" �Τ褦�ʥ��ޥ�ɤ� OS �˰�¸���ơ�"perl", "perl.exe", "perl.pm" �Τ褦�ʥե�����Ȥ���¸�ߤ��Ƥ��뤫�⤷��ޤ��� The variable in the Config �⥸�塼����ѿ� "_exe" �ϡ�(�⤷�����)�¹Է����γ�ĥ�Ҥ��ݻ����ޤ��� 3 ���ܤˡ�VMS �ǤϤ���ʾ�ν��������פʤ褦�˿��Ť� $^X �� $Config{perlpath} �����ꤷ�ޤ��� ����ϡ��ʲ��˼�������ɽ���Υޥå��󥰤����줫�� VMS �ե�����̾�� ���뤫�⤷��ʤ������ΥС�������ֹ�򰷤�ɬ�פ����뤫��Ǥ��� =begin original To convert $^X to a file pathname, taking account of the requirements of the various operating system possibilities, say: =end original $^X ��ե�����ѥ�̾���Ѵ�����Ȥ����ʲ��Τ褦�ˡ��͡��� ���ڥ졼�ƥ��󥰥����ƥ�β�ǽ�����׵���θ���Ƥ�������: use Config; $thisperl = $^X; if ($^O ne 'VMS') {$thisperl .= $Config{_exe} unless $thisperl =~ m/$Config{_exe}$/i;} =begin original To convert $Config{perlpath} to a file pathname, say: =end original $Config{perlpath} ��ե�����Υѥ�̾���Ѵ�����ˤϡ��㤨��: use Config; $thisperl = $Config{perlpath}; if ($^O ne 'VMS') {$thisperl .= $Config{_exe} unless $thisperl =~ m/$Config{_exe}$/i;} =head2 Networking (�ͥåȥ��) =begin original Don't assume that you can reach the public Internet. =end original �����Υ��󥿡��ͥåȤ��Ϥ����Ȥ��ꤷ�ʤ��Ǥ��������� =begin original Don't assume that there is only one way to get through firewalls to the public Internet. =end original �ե���������������̤äƸ����Υ��󥿡��ͥåȤؽФ�ƻ�� ��Ĥ�������Ȥ������Ȥ��ꤷ�ʤ��Ǥ��������� =begin original Don't assume that you can reach outside world through any other port than 80, or some web proxy. ftp is blocked by many firewalls. =end original �ݡ��� 80 �䤤���Ĥ��Υ����֥ץ�������ʳ��ǡ���¦���������Ϥ����Ȥ� ���ꤷ�ʤ��Ǥ��������� ftp ��¿���Υե�������������ǥ֥��å�����ޤ��� =begin original Don't assume that you can send email by connecting to the local SMTP port. =end original �������� SMTP �ݡ��Ȥ���³���뤳�Ȥ� e �᡼��������Ǥ���� ���ꤷ�ʤ��Ǥ��������� =begin original Don't assume that you can reach yourself or any node by the name 'localhost'. The same goes for '127.0.0.1'. You will have to try both. =end original 'localhost' �Ȥ���̾���Ǽ�ʬ���Ȥ䤽��¾�ΥΡ��ɤ��Ϥ��� ���ꤷ�ʤ��Ǥ��������� Ʊ�����Ȥ� '127.0.0.1' �ˤ�����ޤ��� ξ����ɬ�פ�����ޤ��� =begin original Don't assume that the host has only one network card, or that it can't bind to many virtual IP addresses. =end original �ۥ��Ȥ� 1 ������ͥåȥ�������ɤ�����Ȥ���ʣ���β��� IP ���ɥ쥹�� ������Ƥ��ʤ��Ȳ��ꤷ�ʤ��Ǥ��������� =begin original Don't assume a particular network device name. =end original ����Υͥåȥ���ǥХ���̾���ꤷ�ʤ��Ǥ��������� =begin original Don't assume a particular set of ioctl()s will work. =end original ����� ioctl() ��ư��뤳�Ȥ��ꤷ�ʤ��Ǥ��������� =begin original Don't assume that you can ping hosts and get replies. =end original �ۥ��Ȥ� ping ���Ʒ�̤���������Ȳ��ꤷ�ʤ��Ǥ��������� =begin original Don't assume that any particular port (service) will respond. =end original ����Υݡ��� (�����ӥ�) ����������Ȳ��ꤷ�ʤ��Ǥ��������� =begin original Don't assume that Sys::Hostname (or any other API or command) returns either a fully qualified hostname or a non-qualified hostname: it all depends on how the system had been configured. Also remember things like DHCP and NAT-- the hostname you get back might not be very useful. =end original Sys::Hostname (�ޤ��Ϥ���¾�� API �䥳�ޥ��) �����������ۥ���̾�� ��������ʤ��ۥ���̾�Τɤ��餫���֤��Ȳ��ꤷ�ʤ��Ǥ�������: ��������Ƥ� �����ƥब�ɤΤ褦�����ꤵ��Ƥ��뤫�˰�¸���ޤ��� �ޤ���DHCP �� NAT �Τ��Ȥ�˺��ʤ��Ǥ������� -- �������ۥ���̾������ ͭ�ѤǤϤʤ����⤷��ޤ��� =begin original All the above "don't":s may look daunting, and they are -- but the key is to degrade gracefully if one cannot reach the particular network service one wants. Croaking or hanging do not look very professional. =end original ��Ҥ������ƤΡ֤٤��餺�פ϶����������Τ��⤷��ޤ���; �����Ƥ��� �̤�Ǥ� -- ���������ϡ�˾��Ǥ�������Υͥåȥ�������ӥ��� ��ã�Ǥ��ʤ��Ȥ��ˡ�Ŭ�ڤ˥ǥ��졼�ɤ��뤳�ȤǤ��� croak ��ϥ󥰥��åפǤϤȤƤ�ץ��λŻ��ˤϸ����ޤ��� =head2 Interprocess Communication (IPC) (�ץ��������̿�(IPC)) =begin original In general, don't directly access the system in code meant to be portable. That means, no C, C, C, C, C<``>, C, C with a C<|>, nor any of the other things that makes being a perl hacker worth being. =end original ����Ū�ˡ��ܿ�����������륳������ǥ����ƥ��ľ�ܥ����������ʤ��Ǥ��������� �ĤޤꡢC, C, C, C, C<``>, C, C �Ǥ� C<|> ����¾ perl �ϥå��������ͤ�����Ȼפ���ΤǤ��� =begin original Commands that launch external processes are generally supported on most platforms (though many of them do not support any type of forking). The problem with using them arises from what you invoke them on. External tools are often named differently on different platforms, may not be available in the same location, might accept different arguments, can behave differently, and often present their results in a platform-dependent way. Thus, you should seldom depend on them to produce consistent results. (Then again, if you're calling I, you probably don't expect it to run on both Unix and CP/M.) =end original �����ץ�������ư���륳�ޥ�ɤϰ���Ū�ˤۤȤ�ɤΥץ�åȥե������ �б����Ƥ��ޤ�(����������¿���� fork ���б����Ƥ��ޤ���)�� ������Ȥ��Ȥ�������ϲ���ư���뤫�Ȥ������Ȥ���ȯ�����ޤ��� �����ġ���ϥץ�åȥե����ब�ۤʤ�Ф��Ф��аۤʤä�̾���Ȥʤꡢ Ʊ���������Ѳ�ǽ�ǤϤʤ����⤷�줺���ۤʤä������������뤫�⤷�줺�� �ۤʤä�ư��򤹤뤫�⤷�줺�����Ф��з�̤�ץ�åȥե�����˰�¸�������� ɽ�����ޤ��� ���äơ���Ӥ�����̤��������뤿��ˡ��ۤȤ�ɤ��Τ褦�ʤ�Τ� ��¸���ʤ��褦�ˤ���٤��Ǥ��� (�Ƥӡ�I ��ƤӽФ��ʤ顢�����餯 Unix �� CP/M ��ξ���� �ƤӽФ����Ȥ����ꤷ�Ƥ��ʤ��Ǥ��礦��) =begin original One especially common bit of Perl code is opening a pipe to B: =end original �ä˰���Ū�� Perl �����ɤΰ�Ĥ� B �ؤΥѥ��פ򳫤����ȤǤ�: open(MAIL, '|/usr/lib/sendmail -t') or die "cannot fork sendmail: $!"; =begin original This is fine for systems programming when sendmail is known to be available. But it is not fine for many non-Unix systems, and even some Unix systems that may not have sendmail installed. If a portable solution is needed, see the various distributions on CPAN that deal with it. Mail::Mailer and Mail::Send in the MailTools distribution are commonly used, and provide several mailing methods, including mail, sendmail, and direct SMTP (via Net::SMTP) if a mail transfer agent is not available. Mail::Sendmail is a standalone module that provides simple, platform-independent mailing. =end original sendmail �����Ѳ�ǽ�Ǥ��뤳�Ȥ�ʬ���äƤ���ʤ饷���ƥ� �ץ�����ߥ󥰤Ȥ��Ƥ��ޤ�ư���ޤ��� ������¿������ Unix �����ƥ�䡢Unix �Ǥ� sendmail �� ���󥹥ȡ��뤵��Ƥ��ʤ������ƥ�ǤϤ��ޤ�ư���ޤ��� �ܿ����Τ����ˡ��ɬ�פʤ顢CPAN �ˤ��뤳��򰷤�������͡��� �ǥ����ȥ�ӥ塼�����򻲾Ȥ��Ƥ��������� Mail::Mailer ����� MailTools �� Mail::Send �ϰ���Ū�˻Ȥ�졢mail�� sendmail���᡼��ž������������Ȥ����ѤǤ��ʤ��ʤ� (Net::SMTP ��ͳ��) SMTP ľ�ܤ�ޤत���Ĥ��Υ᡼�������᥽�åɤ��󶡤��ޤ��� Mail::Sendmail ��ñ��ǡ��ץ�åȥե�������Ω�ʥ᡼���������󶡤��� ñ�ΤΥ⥸�塼��Ǥ��� =begin original The Unix System V IPC (C) is not available even on all Unix platforms. =end original Unix System V IPC (C) �� Unix �ץ�åȥե�����Ǥ��������Ƥ����ѤǤ���櫓�ǤϤ���ޤ��� =begin original Do not use either the bare result of C or bare v-strings (such as C) to represent IPv4 addresses: both forms just pack the four bytes into network order. That this would be equal to the C language C struct (which is what the socket code internally uses) is not guaranteed. To be portable use the routines of the Socket extension, such as C, C, and C. =end original IPv4 ���ɥ쥹��ɽ�����뤿��� C �����η�̤� (C �Τ褦��)����v-ʸ�����Ȥ�ʤ��Ǥ�������: �ɤ���� ������ñ�� 4 �Х��Ȥ�ͥåȥ������� pack ���Ƥ��ޤ��� ���줬(�����åȥ����ɤ������ǻȤ�) C ����� C ��¤�Τ� Ʊ���Ǥ��뤳�Ȥ��ݾڤ���Ƥ��ޤ��� �ܿ�����������뤿��ˤϡ�C, C, C �Τ褦�ʡ�Socket �������ƥ󥷥��Υ롼����� �ȤäƤ��������� =begin original The rule of thumb for portable code is: Do it all in portable Perl, or use a module (that may internally implement it with platform-specific code, but expose a common interface). =end original �ܿ����Τ��륳���ɤΤ���ηи�Ū��ˡ§��: ���ưܿ����Τ��� Perl �Ǥ��뤫�� �⥸�塼���ȤäƤ������� (����������ǥץ�åȥե������¸�μ����� ���Ƥ��뤫�⤷��ޤ��󤬡�����Ū�ʥ��󥿡��ե������򻯤��Ƥ��ޤ�)�� =head2 External Subroutines (XS) (�������֥롼����(XS)) =begin original XS code can usually be made to work with any platform, but dependent libraries, header files, etc., might not be readily available or portable, or the XS code itself might be platform-specific, just as Perl code might be. If the libraries and headers are portable, then it is normally reasonable to make sure the XS code is portable, too. =end original XS �����ɤ����̤ɤΥץ�åȥե�����Ǥ�ư���褦�˺���Ƥ��ޤ����� ��¸�饤�֥�ꡢ�إå��ե�����ʤɤ����Ѳ�ǽ�Ǥʤ��ä���ܿ������ʤ��ä��ꡢ XS �����ɼ��Ȥ� (Perl �����ɤ������Ǥ��뤫�⤷��ʤ��褦��) �ץ�åȥե������¸���⤷��ޤ��� �饤�֥��ȥإå��˰ܿ���������ʤ顢XS �����ɤ�ܿ���������� �ͤ���Τ����̹���Ū�Ǥ��� =begin original A different type of portability issue arises when writing XS code: availability of a C compiler on the end-user's system. C brings with it its own portability issues, and writing XS code will expose you to some of those. Writing purely in Perl is an easier way to achieve portability. =end original XS �����ɤ�񤯤Ȥ��ˤϰ�ä�����ΰܿ��������꤬ȯ�����ޤ�: ����ɥ桼�����Υ����ƥ�� C ����ѥ��餬���ѤǤ��뤫�Ǥ��� C �Ϥ��켫�Ȥΰܿ��������꤬���ꡢXS �����ɤϤ����Τ����Ĥ��򻯤��ޤ��� �ԥ奢 Perl �ǽ񤯤��Ȥϰܿ�����ã���������ñ����ˡ�Ǥ��� =head2 Standard Modules (ɸ��⥸�塼��) =begin original In general, the standard modules work across platforms. Notable exceptions are the CPAN module (which currently makes connections to external programs that may not be available), platform-specific modules (like ExtUtils::MM_VMS), and DBM modules. =end original ����Ū�ˡ�ɸ��⥸�塼��ϤɤΥץ�åȥե�����Ǥ�ư���ޤ��� ���ܤ���٤��㳰�� CPAN �⥸�塼�� (���ΤȤ������Ѳ�ǽ�Ǥʤ����⤷��ʤ� �����ץ���������³���ޤ�)��(ExtUtils::MM_VMS �Τ褦��) �ץ�åȥե������ͭ�Υ⥸�塼�롢DBM �⥸�塼��Ǥ��� =begin original There is no one DBM module available on all platforms. SDBM_File and the others are generally available on all Unix and DOSish ports, but not in MacPerl, where only NBDM_File and DB_File are available. =end original ���ƤΥץ�åȥե���������Ѳ�ǽ�� DBM �⥸�塼��Ϥ���ޤ��� SDBM_File �Ȥ���¾�ϰ���Ū�����Ƥ� Unix �� DOS ���Ǥ����Ѳ�ǽ�Ǥ����� MacPerl �Ǥ����ѤǤ�����NBDM_File �� DB_File �Τߤ����Ѳ�ǽ�Ǥ��� =begin original The good news is that at least some DBM module should be available, and AnyDBM_File will use whichever module it can find. Of course, then the code needs to be fairly strict, dropping to the greatest common factor (e.g., not exceeding 1K for each record), so that it will work with any DBM module. See L for more details. =end original �����Τ餻�ϡ����ʤ��Ȥⲿ�餫�� DBM �⥸�塼������Ѳ�ǽ�ʤϤ��ǡ� AnyDBM_File �ϸ��դ��ä��ɤ줫�Υ⥸�塼���Ȥ��ޤ��� �������Ǥ�դ� DBM �⥸�塼���ư����뤿��ˡ������ɤϤ��ʤ긷̩�ǡ� ��������Ū��ǽ�˸��ꤵ��ޤ�(�㤨�С��ƥ쥳���ɤ� 1K ��Ķ�����ޤ���)�� ����ʤ�ܺ٤ˤĤ��Ƥ� L �򻲾Ȥ��Ƥ��������� =head2 Time and Date (���������) =begin original The system's notion of time of day and calendar date is controlled in widely different ways. Don't assume the timezone is stored in C<$ENV{TZ}>, and even if it is, don't assume that you can control the timezone through that variable. Don't assume anything about the three-letter timezone abbreviations (for example that MST would be the Mountain Standard Time, it's been known to stand for Moscow Standard Time). If you need to use timezones, express them in some unambiguous format like the exact number of minutes offset from UTC, or the POSIX timezone format. =end original �����������դȻ���Υ����ƥ�Ǥε�ˡ���礭���ۤʤä���ˡ�� ���椵��Ƥ��ޤ��� �����ॾ���� C<$ENV{TZ}> ���ݴɤ���Ƥ���Ȳ��ꤷ�ʤ��Ǥ�������; �ޤ��㤨�ݴɤ���Ƥ��Ƥ⡢�����ѿ��ǥ����ॾ���������Ǥ���� ���ꤷ�ʤ��Ǥ��������� 3 ʸ�������ॾ����ά�ΤˤĤ��Ʋ��β���⤷�ʤ��Dz����� (�㤨�� MST �� Mountain Standard Time ���⤷��ޤ��󤬡�Moscow Standard Time �Ȥ��Ƥ� �Τ��Ƥ��ޤ�)�� �����ॾ�����Ȥ�ɬ�פ�����ʤ顢UTC ��������Τ�ʬ���� POSIX �����ॾ��������Τ褦�ʡ�ۣ�椵�Τʤ������ǵ��Ҥ��Ƥ��Ƥ��������� =begin original Don't assume that the epoch starts at 00:00:00, January 1, 1970, because that is OS- and implementation-specific. It is better to store a date in an unambiguous representation. The ISO 8601 standard defines YYYY-MM-DD as the date format, or YYYY-MM-DDTHH-MM-SS (that's a literal "T" separating the date from the time). Please do use the ISO 8601 instead of making us to guess what date 02/03/04 might be. ISO 8601 even sorts nicely as-is. A text representation (like "1987-12-18") can be easily converted into an OS-specific value using a module like Date::Parse. An array of values, such as those returned by C, can be converted to an OS-specific representation using Time::Local. =end original ������ 1970 ǯ 1 �� 1 �� 00:00:00 �˳��Ϥ����Ȳ��ꤷ�ʤ��Ǥ�������; �ʤ��ʤ餳��� OS �ȼ����˰�¸���뤫��Ǥ��� ۣ�椵�Τʤ�ɽ�������դ��ݴɤ��������ɤ��Ǥ��� ISO 8601 ɸ������դη����Ȥ��� YYYY-MM-DD �򡢤��뤤�� YYYY-MM-DDTHH-MM-SS (��ƥ��� "T" �����դȻ����ʬ���Ƥ��ޤ�) �� ������Ƥ��ޤ��� �ɤ��� 02/03/04 �Ȥ������դΰ�̣���¬������ΤǤϤʤ���ISO 8601 �� �ȤäƤ��������� ISO 8601 �Ϥ��Τޤޤ��ޤ������Ȥ�Ǥ��ޤ��� ("1987-12-18" �Τ褦��) �ƥ�����ɽ���� Date::Parse �Τ褦�ʥ⥸�塼��� �Ȥäƴ�ñ�� OS ��ͭ���ͤ��Ѵ��Ǥ��ޤ��� C ���֤����褦���ͤ�����ϡ�Time::Local ��Ȥä� OS ��ͭ�� ɽ�����Ѵ��Ǥ��ޤ��� =begin original When calculating specific times, such as for tests in time or date modules, it may be appropriate to calculate an offset for the epoch. =end original ��������դΥ⥸�塼��Υƥ��ȤΤ褦�ʡ�����λ����׻�����Ȥ��ˤϡ� ��������Υ��ե��åȤ�׻�����Τ�Ŭ�ڤǤ��礦�� require Time::Local; $offset = Time::Local::timegm(0, 0, 0, 1, 0, 70); =begin original The value for C<$offset> in Unix will be C<0>, but in Mac OS will be some large number. C<$offset> can then be added to a Unix time value to get what should be the proper value on any system. =end original Unix �Ǥ� C<$offset> ���ͤ� C<0> �Ǥ�����Mac OS �Ǥ��礭�ʿ��ˤʤ�ޤ��� ���줫�顢C<$offset> ��Ǥ�դΥ����ƥ�Ǥ�Ŭ�ڤ��ͤ����뤿��� Unix time �˲ä����ޤ��� =begin original On Windows (at least), you shouldn't pass a negative value to C or C. =end original (���ʤ��Ȥ�) Windows �Ǥϡ�C �� C ������� �Ϥ��٤��ǤϤ���ޤ��� =head2 Character sets and character encoding (ʸ�������ʸ�����󥳡��ǥ���) =begin original Assume very little about character sets. =end original ʸ������ˤĤ��Ʋ���Ǥ��뤳�ȤϤۤȤ�ɤ���ޤ��� =begin original Assume nothing about numerical values (C, C) of characters. Do not use explicit code point ranges (like \xHH-\xHH); use for example symbolic character classes like C<[:print:]>. =end original ʸ���ο��� (C, C) �ˤĤ��Ʋ���Ǥ��뤳�ȤϤ���ޤ��� (\xHH-\xHH �Τ褦��) ����Ū�������֤��ϰϤϻȤ�ʤ��Ǥ�������; �㤨�� C<[:print:]> �Τ褦�ʥ���ܥ�å���ʸ�����饹��ȤäƤ��������� =begin original Do not assume that the alphabetic characters are encoded contiguously (in the numeric sense). There may be gaps. =end original �ѻ���(����Ū�ʰ�̣��)Ϣ³���ƥ��󥳡��ɤ����Ȳ��ꤷ�ʤ��Ǥ��������� ��֤����뤫�⤷��ޤ��� =begin original Do not assume anything about the ordering of the characters. The lowercase letters may come before or after the uppercase letters; the lowercase and uppercase may be interlaced so that both "a" and "A" come before "b"; the accented and other international characters may be interlaced so that E comes before "b". =end original ʸ���ν���ˤĤ��Ʋ��Ⲿ�ꤷ�ʤ��Ǥ��������� ��ʸ������ʸ���������⤷��ޤ��󤷸夫�⤷��ޤ���; ��ʸ������ʸ������ߤ� ��뤿��ˡ�"a" �� "A" ��ξ���� "b" �������⤷��ޤ���; ���������ʸ���� ����¾�ι��ʸ���ϸ�ߤ���뤫���Τ�ʤ��Τ� E �� "b" �� �����⤷��ޤ��� =head2 Internationalisation (��ݲ�) =begin original If you may assume POSIX (a rather large assumption), you may read more about the POSIX locale system from L. The locale system at least attempts to make things a little bit more portable, or at least more convenient and native-friendly for non-English users. The system affects character sets and encoding, and date and time formatting--amongst other things. =end original POSIX (���Ū�礭������) ���ꤹ��ʤ顢L ���� POSIX �������륷���ƥ�ˤĤ���¿�����ɤ�ޤ��� �������륷���ƥ�Ͼ��ʤ��Ȥ�ʪ����⤦�����ܿ����Τ�����ˤ��褦�Ȥ��롢 ���뤤�Ͼ��ʤ��Ȥ���Ѹ�桼���ˤȤäƤ������������˿Ƥ��������ΤǤ��� ���Υ����ƥ��ʸ������ȥ��󥳡��ǥ��󥰡����դȻ���η��� -- ¾�Τ�Τ� �����ä� -- �˱ƶ���Ϳ���ޤ��� =begin original If you really want to be international, you should consider Unicode. See L and L for more information. =end original �⤷�����˹�ݲ��������ʤ顢Unicode ���θ����٤��Ǥ��� ����ʤ����ˤĤ��Ƥ� L �� L �� ���Ȥ��Ƥ��������� =begin original If you want to use non-ASCII bytes (outside the bytes 0x00..0x7f) in the "source code" of your code, to be portable you have to be explicit about what bytes they are. Someone might for example be using your code under a UTF-8 locale, in which case random native bytes might be illegal ("Malformed UTF-8 ...") This means that for example embedding ISO 8859-1 bytes beyond 0x7f into your strings might cause trouble later. If the bytes are native 8-bit bytes, you can use the C pragma. If the bytes are in a string (regular expression being a curious string), you can often also use the C<\xHH> notation instead of embedding the bytes as-is. (If you want to write your code in UTF-8, you can use the C.) The C and C pragmata are available since Perl 5.6.0. =end original �� ASCII �Х��� (0x00..0x7f ���ϰϳ��ΥХ���) ��֥����������ɡפ� �Ȥ������ʤ顢�ܿ����Τ���ˡ����ΥХ��Ȥ����Ǥ��뤫������Ū�ˤ���ɬ�פ� ����ޤ��� ï�����㤨�Ф��Υ����ɤ� UTF-8 ��������ǻȤ����⤷�줺�����ξ�� ������ʥͥ��ƥ��֤ΥХ��Ȥ������Ȥʤ�ޤ� ("Malformed UTF-8 ...")�� ������㤨�� 0x7f ��Ķ���� ISO 8859-1 �ΥХ��Ȥ�ʸ������Ȥ߹���� ���Ȥ������������������⤷��ʤ��Ȥ������ȤǤ��� ���ΥХ��Ȥ��ͥ��ƥ��֤� 8 �ӥåȥХ��Ȥʤ顢C �ץ饰�ޤ�Ȥ��ޤ��� ���ΥХ��Ȥ�ʸ����ˤ���(����ɽ���Ϥ�������ʸ����ˤʤ�ޤ�)�ʤ顢 ���ΥХ��Ȥ򤽤Τޤ��Ȥ߹�������� C<\xHH> ɽ���⤷�Ф��лȤ��ޤ��� (�����ɤ� UTF-8 �ǽ񤭤����ʤ顢C ���Ȥ��ޤ���) C �� C �Υץ饰�ޤ� Perl 5.6.0 �������Ѳ�ǽ�Ǥ��� =head2 System Resources (�����ƥ�꥽����) =begin original If your code is destined for systems with severely constrained (or missing!) virtual memory systems then you want to be I mindful of avoiding wasteful constructs such as: =end original ���ʤ��Υ����ɤ����ۥ���ˤĤ��Ƹ��������¤��줿(���뤤��¸�ߤ��ʤ�!) �����ƥ��ư��뤳�ȤˤʤäƤ���ʤ顢I<�ä�> �ʲ��Τ褦��̵�̤ʹ�¤�� �򤱤����Ǥ�: # NOTE: this is no longer "bad" in perl5.005 for (0..10000000) {} # bad for (my $x = 0; $x <= 10000000; ++$x) {} # good @lines = ; # bad while () {$file .= $_} # sometimes bad $file = join('', ); # better =begin original The last two constructs may appear unintuitive to most people. The first repeatedly grows a string, whereas the second allocates a large chunk of memory in one go. On some systems, the second is more efficient that the first. =end original �Ǹ����Ĥι�¤�ϤۤȤ�ɤο͡��ˤȤä�ľ��Ū�ǤϤʤ����⤷��ޤ��� �����ܤϽ�����ʸ�����礭���ʤꡢ�����ܤϰ��٤��礭�ʥ���β��� ������Ƥޤ��� �����ƥ�ˤ�äƤϡ������ܤ����������ܤ����ΨŪ�Ǥ��� =head2 Security (�������ƥ�) =begin original Most multi-user platforms provide basic levels of security, usually implemented at the filesystem level. Some, however, do not-- unfortunately. Thus the notion of user id, or "home" directory, or even the state of being logged-in, may be unrecognizable on many platforms. If you write programs that are security-conscious, it is usually best to know what type of system you will be running under so that you can write code explicitly for that platform (or class of platforms). =end original �ۤȤ�ɤΥޥ���桼���ץ�åȥե�����Ǥ�(���̤ϥե����륷���ƥ�� �������줿)����Ū�ʥ�٥�Υ������ƥ����󶡤��Ƥ��ޤ��� �������������� -- ��ǰ�ʤ��� -- �����ǤϤ���ޤ��� ���äƥ桼���� ID��"home" �ǥ��쥯�ȥꡢ���뤤�ϥ������󤷤Ƥ��뤫�ɤ��� �Ȥ�����ǰ����¿���Υץ�åȥե�����Ǥ�ǧ���Ǥ��ʤ����⤷��ޤ��� �������ƥ���ռ������ץ�������񤯤ʤ顢�ɤμ���Υ����ƥ�� �¹Ԥ���뤫���Τ�Τ����̤Ϻ��ɤǤ�; ����ˤ�ä�����Ū�ˤ��� �ץ�åȥե�����(�ޤ��ϥץ�åȥե�����μ���)�Τ���Υ����ɤ�񤱤ޤ��� =begin original Don't assume the UNIX filesystem access semantics: the operating system or the filesystem may be using some ACL systems, which are richer languages than the usual rwx. Even if the rwx exist, their semantics might be different. =end original UNIX �Υե����륷���ƥॢ��������̣�����ꤷ�ʤ��Ǥ�������: ���ڥ졼�ƥ��󥰥����ƥ��ե����륷���ƥ���̾�� rwx ����˭�٤� ��ǽ����� ACL �����ƥ��ȤäƤ��뤫�⤷��ޤ��� rwx ��¸�ߤ����Ȥ��Ƥ⡢��̣�ϰ㤦���⤷��ޤ��� =begin original (From security viewpoint testing for permissions before attempting to do something is silly anyway: if one tries this, there is potential for race conditions-- someone or something might change the permissions between the permissions check and the actual operation. Just try the operation.) =end original (�������ƥ����̤���ϡ������򤷤褦�Ȥ������˸��¤�ƥ��Ȥ���Τ� ���⤽��Ф����Ƥ��ޤ�: �������褦�Ȥ���ȡ�����Ū�ʶ����郎����ޤ� -- ���¥����å��ȼºݤ����δ֤�ï���ޤ��ϲ��������¤��Ѥ��뤫�⤷��ޤ��� ñ�������Ƥ���������) =begin original Don't assume the UNIX user and group semantics: especially, don't expect the C<< $< >> and C<< $> >> (or the C<$(> and C<$)>) to work for switching identities (or memberships). =end original UNIX �Υ桼�����ȥ��롼�פΰ�̣�����ꤷ�ʤ��Ǥ�������: �äˡ��桼���� (���뤤�ϥ��롼��)���ڤ��ؤ���Τ� C<< $< >> �� C<< $> >> (�ޤ��� C<$(> �� C<$)>) ��ư�������ꤷ�ʤ��Ǥ��������� =begin original Don't assume set-uid and set-gid semantics. (And even if you do, think twice: set-uid and set-gid are a known can of security worms.) =end original set-uid �� set-gid ��ư����ꤷ�ʤ��Ǥ��������� (�����Ƥ��������Ȥ��Ƥ⡢���ٹͤ��Ƥ�������: set-uid �� set-gid �ϥ������ƥ�����δ̵ͤȤ����Τ��Ƥ��ޤ���) =head2 Style (��������) =begin original For those times when it is necessary to have platform-specific code, consider keeping the platform-specific code in one place, making porting to other platforms easier. Use the Config module and the special variable C<$^O> to differentiate platforms, as described in L<"PLATFORMS">. =end original �ץ�åȥե������ͭ�Υ����ɤ��ɬ�פ�������ˤϡ��ץ�åȥե������ͭ�� �����ɤ� 1 �ս�˽���ơ�¾�Υץ�åȥե�����ؤΰܿ������ưפˤ��뤳�Ȥ� ��θ���Ƥ��������� L<"PLATFORMS"> �ǵ��Ҥ���Ƥ���褦�ˡ��ץ�åȥե�������̤��뤿��� Config �⥸�塼����ü��ѿ� C<$^O> ��ȤäƤ��������� =begin original Be careful in the tests you supply with your module or programs. Module code may be fully portable, but its tests might not be. This often happens when tests spawn off other processes or call external programs to aid in the testing, or when (as noted above) the tests assume certain things about the filesystem and paths. Be careful not to depend on a specific output style for errors, such as when checking C<$!> after a failed system call. Using C<$!> for anything else than displaying it as output is doubtful (though see the Errno module for testing reasonably portably for error value). Some platforms expect a certain output format, and Perl on those platforms may have been adjusted accordingly. Most specifically, don't anchor a regex when testing an error value. =end original �⥸�塼���ץ������ȶ����󶡤���ƥ��Ȥˤ����դ��Ƥ��������� �⥸�塼��Υ����ɤϴ����˰ܿ��������뤫���Τ�ޤ��󤬡� �ƥ��ȤϤ����ǤϤʤ����⤷��ޤ��� ����ϡ��ƥ��Ȥν����Ȥ��뤿���¾�Υץ�������ư�����곰���Υץ������� �ƤӽФ����ꤷ���ꡢ�ƥ��Ȥ�(��Ҥ����褦��)�ե����륷���ƥ��ѥ��ˤĤ��� �����β���򤷤��Ȥ��ˤ��Ф��е�����ޤ��� �����ƥॳ����˼��Ԥ������Ȥ� C<$!> �Τ褦�ʡ����顼������ν��Ϸ����� ��¸���ʤ��褦�����դ��Ƥ��������� ���ϤȤ���ɽ������ʳ��Τ��Ȥ� C<$!> ��Ȥ����Ȥϵ��䤬����ޤ�(������ ���顼�ͤˤĤ��ƽ�ʬ�ʰܿ����Τ���ƥ��Ȥ���뤿��� Errno �⥸�塼��� ���Ȥ��Ƥ�������)�� �����Υץ�åȥե�����Ϥ����ν��Ϸ��������ꤷ�Ƥ��ơ������� �ץ�åȥե������ Perl �Ϥ���˱�����Ĵ�����ޤ��� ��äȤ⸷̩�˸����С����顼�ͤ�ƥ��Ȥ���Ȥ�������ɽ���� �Ȥ�ʤ��Ǥ��������� =head1 CPAN Testers =begin original Modules uploaded to CPAN are tested by a variety of volunteers on different platforms. These CPAN testers are notified by mail of each new upload, and reply to the list with PASS, FAIL, NA (not applicable to this platform), or UNKNOWN (unknown), along with any relevant notations. =end original CPAN �˥��åץ����ɤ��줿�⥸�塼��Ͽ����ʥץ�åȥե������ �͡��ʥܥ��ƥ����ˤ�äƥƥ��Ȥ���ޤ��� ������ CPAN testers �Ͽ��������åץ����ɤ���뤳�Ȥ˥᡼��ˤ�ä� ���Τ��졢PASS, FAIL, NA (���Υץ�åȥե�����Ǥ���Ŭ��), UNKNOWN (����) �Τ����줫�򡢴�Ϣ�������ȶ����ֿ����ޤ��� =begin original The purpose of the testing is twofold: one, to help developers fix any problems in their code that crop up because of lack of testing on other platforms; two, to provide users with information about whether a given module works on a given platform. =end original �ƥ��Ȥ���Ū����Ĥ���ޤ�: ����ܤϡ�¾�Υץ�åȥե�����Υƥ��Ȥ� �ʤ����Ȥˤ�ä���������륳���ɤ������ȯ�Ԥ��������뤳�Ȥ� �����뤿��Ǥ�; ����ܤϡ�����⥸�塼�뤬����ץ�åȥե������ ư��뤫�ɤ����ξ����桼�������󶡤��뤳�ȤǤ��� =begin original Also see: =end original �ʲ��⻲�Ȥ��Ƥ�������: =over 4 =item * =begin original Mailing list: cpan-testers@perl.org =end original �᡼��󥰥ꥹ��: cpan-testers@perl.org =item * =begin original Testing results: http://testers.cpan.org/ =end original �ƥ��ȷ��: http://testers.cpan.org/ =back =head1 PLATFORMS (�ץ�åȥե�����) =begin original As of version 5.002, Perl is built with a C<$^O> variable that indicates the operating system it was built on. This was implemented to help speed up code that would otherwise have to C and use the value of C<$Config{osname}>. Of course, to get more detailed information about the system, looking into C<%Config> is certainly recommended. =end original �С������ 5.002 ���顢Perl �� C<$^O> �ѿ����ӥ�ɤ��줿���ڥ졼�ƥ��� �����ƥ�򼨤��褦�ʷ��ǥӥ�ɤ���ޤ��� ����ϡ�C ���� C<$Config{osname}> ���ͤ�Ĵ�٤�ɬ�פ� �ʤ��褦�ˤ��뤳�Ȥǹ�®��������Ƥ��ޤ��� ������󥷥��ƥफ���äȾܺ٤ʾ��������ʤ顢C<%Config> �� ���뤳�Ȥ��μ¤ˤ�����Ǥ��� =begin original C<%Config> cannot always be trusted, however, because it was built at compile time. If perl was built in one place, then transferred elsewhere, some values may be wrong. The values may even have been edited after the fact. =end original ��������C<%Config> �ϥ���ѥ�����˥ӥ�ɤ����Τǡ���� ���ꤹ��Ȥ����櫓�ˤϤ����ޤ��� perl ��������ǥӥ�ɤ��졢���줫���̤ξ��˰ܤ����ȡ������Ĥ��� �ͤϴְ�ä���Τˤʤ뤫�⤷��ޤ��� �ͤϸ夫�齤�����뤳�Ȥ���Ǥ��ޤ��� =head2 Unix =begin original Perl works on a bewildering variety of Unix and Unix-like platforms (see e.g. most of the files in the F directory in the source code kit). On most of these systems, the value of C<$^O> (hence C<$Config{'osname'}>, too) is determined either by lowercasing and stripping punctuation from the first field of the string returned by typing C (or a similar command) at the shell prompt or by testing the file system for the presence of uniquely named files such as a kernel or header file. Here, for example, are a few of the more popular Unix flavors: =end original Perl �϶ä��ۤɿ����� Unix �� Unix ���ץ�åȥե������ư��ޤ� (�㤨�� �����������ɥ��åȤ� F �ǥ��쥯�ȥ�ΤۤȤ�ɤΥե������ ���Ȥ��Ƥ�������)�� �����Υ����ƥ�ΤۤȤ�ɤǤϡ�C<$^O> ���ͤ� (���ä� C<$Config{'osname'}> ���ͤ�)��������ץ���ץȤ��� C (�ޤ��� �����褦�ʥ��ޥ��) ���֤��줿ʸ����κǽ�Υե�����ɤ���������� �������ƾ�ʸ���ˤ�����Τ��������ͥ��إå��ե�����Τ褦�ʥ�ˡ����� ̾�����դ����ե������¸�ߤ�ե����륷���ƥ��Ĵ�٤뤳�Ȥˤ�ä� ���ꤵ��ޤ��� �㤨�С��ʲ��Ϥ��ͭ̾�� Unix �������ƥ�Τ����Ĥ��Ǥ�: uname $^O $Config{'archname'} -------------------------------------------- AIX aix aix BSD/OS bsdos i386-bsdos Darwin darwin darwin dgux dgux AViiON-dgux DYNIX/ptx dynixptx i386-dynixptx FreeBSD freebsd freebsd-i386 Haiku haiku BePC-haiku Linux linux arm-linux Linux linux i386-linux Linux linux i586-linux Linux linux ppc-linux HP-UX hpux PA-RISC1.1 IRIX irix irix Mac OS X darwin darwin MachTen PPC machten powerpc-machten NeXT 3 next next-fat NeXT 4 next OPENSTEP-Mach openbsd openbsd i386-openbsd OSF1 dec_osf alpha-dec_osf reliantunix-n svr4 RM400-svr4 SCO_SV sco_sv i386-sco_sv SINIX-N svr4 RM400-svr4 sn4609 unicos CRAY_C90-unicos sn6521 unicosmk t3e-unicosmk sn9617 unicos CRAY_J90-unicos SunOS solaris sun4-solaris SunOS solaris i86pc-solaris SunOS4 sunos sun4-sunos =begin original Because the value of C<$Config{archname}> may depend on the hardware architecture, it can vary more than the value of C<$^O>. =end original C<$Config{archname}> ���ͤϥϡ��ɥ������������ƥ�����˰�¸���Ƥ��뤿�ᡢ C<$^O> ���ͤ����͡����ͤˤʤ�ޤ��� =head2 DOS and Derivatives (DOS �Ȥ�������) =begin original Perl has long been ported to Intel-style microcomputers running under systems like PC-DOS, MS-DOS, OS/2, and most Windows platforms you can bring yourself to mention (except for Windows CE, if you count that). Users familiar with I or I style shells should be aware that each of these file specifications may have subtle differences: =end original Perl ���Τ��� Intel �����Υޥ���������ԥ塼����ư��� PC-DOS, MS-DOS, OS/2 �Τ褦�ʥ����ƥ�ȡ����ʤ�����Ŧ�Ǥ���褦�ʤۤȤ�����Ƥ� Windows �ץ�åȥե�����(�⤷ Windows CE ��ޤ��ʤ顢����Ͻ����ޤ�)�� �ܿ�����Ƥ��ޤ����� I �� I �����Υ�����ˤʤ�Ƥ���桼�����ϡ� �ʲ��Τ褦�ʥե��������˾������İ㤤�����뤳�Ȥ˵����Ĥ��Ϥ��Ǥ�: $filespec0 = "c:/foo/bar/file.txt"; $filespec1 = "c:\\foo\\bar\\file.txt"; $filespec2 = 'c:\foo\bar\file.txt'; $filespec3 = 'c:\\foo\\bar\\file.txt'; =begin original System calls accept either C or C<\> as the path separator. However, many command-line utilities of DOS vintage treat C as the option prefix, so may get confused by filenames containing C. Aside from calling any external programs, C will work just fine, and probably better, as it is more consistent with popular usage, and avoids the problem of remembering what to backwhack and what not to. =end original �����ƥॳ����ϥѥ����ڤ�Ȥ��� C �ޤ��� C<\> �Τɤ��餫������դ��ޤ��� ���������Ť� DOS �Υ��ޥ�ɥ饤��桼�ƥ���ƥ��� C �򥪥ץ����� ��Ƭ���Ȥ��ư����Τǡ��ե�����̾�� C ���ޤޤ�Ƥ���Ⱥ��𤹤뤫�� ����ޤ��� �����ץ�������ƤӽФ����Ȥ�����ơ�C �ϤȤƤ⤦�ޤ�ư��������餯 ���褤�Ǥ�; �ʤ��ʤ����Ū�ʻ���ˡ�Ǥ�����������äơ����� �Хå�����å���Dz����ؤǤʤ�����Ф���Ȥ���������򤱤��ޤ��� =begin original The DOS FAT filesystem can accommodate only "8.3" style filenames. Under the "case-insensitive, but case-preserving" HPFS (OS/2) and NTFS (NT) filesystems you may have to be careful about case returned with functions like C or used with functions like C or C. =end original DOS FAT �ե����륷���ƥ�� "8.3" �����Υե�����̾�ˤΤ��б����Ƥ��ޤ��� ����ʸ����ʸ����̵�뤹�뤬����¸�����HPFS (OS/2) �� NTFS (NT) �ե����륷���ƥ�Ǥ� C �Τ褦�ʴؿ������֤��줿�ꡢC �� C �Τ褦�ʴؿ��ǻȤ���ʸ����ʸ�������դ���ɬ�פ� ���뤫�⤷��ޤ��� =begin original DOS also treats several filenames as special, such as AUX, PRN, NUL, CON, COM1, LPT1, LPT2, etc. Unfortunately, sometimes these filenames won't even work if you include an explicit directory prefix. It is best to avoid such filenames, if you want your code to be portable to DOS and its derivatives. It's hard to know what these all are, unfortunately. =end original DOS �Ϥޤ���AUX, PRN, NUL, CON, COM1, LPT1, LPT2 �Τ褦�ʤ����Ĥ��� �ե�����̾�����̤˰����ޤ��� ��ǰ�ʤ��顢�Ȥ��ɤ������Υե�����̾������Ū�ʥǥ��쥯�ȥ���Ƭ���� �ޤ�Ǥ��Ƥ�ư��ޤ��� �����ɤ� DOS �Ȥ��������ǰܿ���������褦�ˤ���ˤϡ������Υե�����̾�� �򤱤�Τ����ɤǤ��� ��ǰ�ʤ��顢��������Ƥ��Τ�Τ��񤷤��Ǥ��� =begin original Users of these operating systems may also wish to make use of scripts such as I or I to put wrappers around your scripts. =end original �����Υ��ڥ졼�ƥ��󥰥����ƥ�Υ桼�����ϡ�������ץȤΥ�åѡ��Ȥ��� I �� I �Τ褦�ʥ�����ץȤ�Ȥ��������⤷��ޤ��� =begin original Newline (C<\n>) is translated as C<\015\012> by STDIO when reading from and writing to files (see L<"Newlines">). C will keep C<\n> translated as C<\012> for that filehandle. Since it is a no-op on other systems, C should be used for cross-platform code that deals with binary data. That's assuming you realize in advance that your data is in binary. General-purpose programs should often assume nothing about their data. =end original �ե����뤫���ɤ߽񤭤���Ȥ������� (C<\n>) �� STDIO �ˤ�ä� C<\015\012> �� �Ѵ�����ޤ�(L<"Newlines"> �򻲾Ȥ��Ƥ�������)�� C �ϡ����Υե�����ϥ�ɥ���Ф��� C<\n> �� C<\012> �Ȥ����Ѵ�����ޤ��� ����Ϥ���¾�Υ����ƥ�Ǥϲ��⤷�ʤ��Τǡ��Х��ʥ�ǡ����򰷤� �������ץ�åȥե����ॳ���ɤǤ� C ��Ȥ��٤��Ǥ��� ����ϡ�ͽ��ǡ������Х��ʥ�Ǥ��뤳�Ȥ�ʬ���äƤ��뤳�Ȥ��ꤷ�Ƥ��ޤ��� ���ѥץ������ϥǡ����ˤĤ��Ʋ��Ⲿ�ꤷ�ʤ��٤��Ǥ��� =begin original The C<$^O> variable and the C<$Config{archname}> values for various DOSish perls are as follows: =end original �͡��� DOS Ū�� perl �Ǥ� C<$^O> �ѿ��� C<$Config{archname}> ���ͤ� �ʲ����̤�Ǥ�: OS $^O $Config{archname} ID Version -------------------------------------------------------- MS-DOS dos ? PC-DOS dos ? OS/2 os2 ? Windows 3.1 ? ? 0 3 01 Windows 95 MSWin32 MSWin32-x86 1 4 00 Windows 98 MSWin32 MSWin32-x86 1 4 10 Windows ME MSWin32 MSWin32-x86 1 ? Windows NT MSWin32 MSWin32-x86 2 4 xx Windows NT MSWin32 MSWin32-ALPHA 2 4 xx Windows NT MSWin32 MSWin32-ppc 2 4 xx Windows 2000 MSWin32 MSWin32-x86 2 5 00 Windows XP MSWin32 MSWin32-x86 2 5 01 Windows 2003 MSWin32 MSWin32-x86 2 5 02 Windows CE MSWin32 ? 3 Cygwin cygwin cygwin =begin original The various MSWin32 Perl's can distinguish the OS they are running on via the value of the fifth element of the list returned from Win32::GetOSVersion(). For example: =end original �͡��� MSWin32 Perl �ϡ�Win32::GetOSVersion() �����֤����ꥹ�Ȥ� 5 ���ܤ� ���Ǥ��ͤ�Ȥä�ư��Ƥ��� OS ����̤Ǥ��ޤ��� �㤨��: if ($^O eq 'MSWin32') { my @os_version_info = Win32::GetOSVersion(); print +('3.1','95','NT')[$os_version_info[4]],"\n"; } =begin original There are also Win32::IsWinNT() and Win32::IsWin95(), try C, and as of libwin32 0.19 (not part of the core Perl distribution) Win32::GetOSName(). The very portable POSIX::uname() will work too: =end original �ޤ� Win32::IsWinNT() �� Win32::IsWin95() �⤢��ޤ�; C �� ��ƤߤƤ�������; ������ libwin32 0.19 (���� Perl ���ۤΰ����Ǥ� ����ޤ���) ����� Win32::GetOSName() ������ޤ��� �ȤƤ�ܿ����Τ��� POSIX::uname() ��ư��ޤ�: c:\> perl -MPOSIX -we "print join '|', uname" Windows NT|moonru|5.0|Build 2195 (Service Pack 2)|x86 =begin original Also see: =end original �ʲ��⻲�Ȥ��Ƥ�������: =over 4 =item * =begin original The djgpp environment for DOS, http://www.delorie.com/djgpp/ and L. =end original DOS �Τ���� djgpp �Ķ� http://www.delorie.com/djgpp/ �� L�� =item * =begin original The EMX environment for DOS, OS/2, etc. emx@iaehv.nl, http://www.leo.org/pub/comp/os/os2/leo/gnu/emx+gcc/index.html or ftp://hobbes.nmsu.edu/pub/os2/dev/emx/ Also L. =end original DOS, OS/2 �ʤɤΤ���� EMX �Ķ� emx@iaehv.nl, http://www.leo.org/pub/comp/os/os2/leo/gnu/emx+gcc/index.html, ftp://hobbes.nmsu.edu/pub/os2/dev/emx/ ����� L�� =item * =begin original Build instructions for Win32 in L, or under the Cygnus environment in L. =end original L �ˤ��� Win32 �Τ���Υӥ�ɼ�礪��� L �ˤ��� Cygnus �Ķ��� =item * =begin original The C modules in L. =end original L �� C �⥸�塼�롣 =item * =begin original The ActiveState Pages, http://www.activestate.com/ =end original ActiveState �Υڡ���, http://www.activestate.com/ =item * =begin original The Cygwin environment for Win32; F (installed as L), http://www.cygwin.com/ =end original Win32 �Τ���� Cygwin �Ķ�; F (L �Ȥ��� ���󥹥ȡ��뤵��ޤ�), http://www.cygwin.com/ =item * =begin original The U/WIN environment for Win32, http://www.research.att.com/sw/tools/uwin/ =end original Win32 �Τ���� U/WIN �Ķ� http://www.research.att.com/sw/tools/uwin/ =item * =begin original Build instructions for OS/2, L =end original OS/2 �Τ���Υӥ�ɼ��Ǥ��� L =back =head2 S =begin original Any module requiring XS compilation is right out for most people, because MacPerl is built using non-free (and non-cheap!) compilers. Some XS modules that can work with MacPerl are built and distributed in binary form on CPAN. =end original XS ����ѥ��뤬ɬ�פʥ⥸�塼��ϤۤȤ�ɤο͡��ˤȤäƤϻȤ��ޤ���; MacPerl �ϥե꡼�Ǥʤ�(�����ư¤��ʤ�!)����ѥ����Ȥä� �ӥ�ɤ���Ƥ��뤫��Ǥ��� MacPerl ��ư�������� XS �⥸�塼��ϥӥ�ɤ���� CPAN �ǥХ��ʥ������ ���ۤ���Ƥ��ޤ��� =begin original Directories are specified as: =end original �ǥ��쥯�ȥ�ϰʲ��Τ褦�˻��ꤵ��ޤ�: volume:folder:file for absolute pathnames volume:folder: for absolute pathnames :folder:file for relative pathnames :folder: for relative pathnames :file for relative pathnames file for relative pathnames =begin original Files are stored in the directory in alphabetical order. Filenames are limited to 31 characters, and may include any character except for null and C<:>, which is reserved as the path separator. =end original �ե�����ϥǥ��쥯�ȥ�˥���ե��٥åȽ���ݴɤ���ޤ��� �ե�����̾�� 31 ʸ�������¤��졢null �ȡ��ѥ����ڤ�Ȥ���ͽ�󤵤�Ƥ��� C<:> �ʳ���Ǥ�դ�ʸ����ޤळ�Ȥ��Ǥ��ޤ��� =begin original Instead of C, see C and C in the Mac::Files module, or C and C. =end original C ������ˡ�Mac::Files �⥸�塼��� C �� C���ޤ��� C �� C �� ���Ȥ��Ƥ��������� =begin original In the MacPerl application, you can't run a program from the command line; programs that expect C<@ARGV> to be populated can be edited with something like the following, which brings up a dialog box asking for the command line arguments. =end original MacPerl ���ץꥱ�������Ǥϡ����ޥ�ɥ饤�󤫤�ץ������� �¹Ԥ��뤳�ȤϤǤ��ޤ���; C<@ARGV> ��Ÿ������뤳�Ȥ����ꤷ�Ƥ���ץ������� �ʲ��Τ褦�ʴ����˽������졢���ޥ�ɥ饤�������֤ͤ�����������ܥå����� ��������ޤ��� if (!@ARGV) { @ARGV = split /\s+/, MacPerl::Ask('Arguments?'); } =begin original A MacPerl script saved as a "droplet" will populate C<@ARGV> with the full pathnames of the files dropped onto the script. =end original "droplet" �Ȥ�����¸���줿 MacPerl ������ץȤϡ�������ץȤ˥ɥ��åפ��줿 �ե�����Υե�ѥ�̾�� C<@ARGV> ��Ÿ�����ޤ��� =begin original Mac users can run programs under a type of command line interface under MPW (Macintosh Programmer's Workshop, a free development environment from Apple). MacPerl was first introduced as an MPW tool, and MPW can be used like a shell: =end original Mac �桼������ MPW (Macintosh Programmer's Workshop, Apple �ˤ��ե꡼�� ��ȯ�Ķ�) �ǤΥ��ޥ�ɥ饤�󥤥󥿡��ե������ǥץ�������¹ԤǤ��ޤ��� MacPerl �Ϻǽ� MPW �ġ���Ȥ���Ƴ�����졢MPW �ϥ�����Τ褦�ˤ��ƻȤ��ޤ�: perl myscript.plx some arguments =begin original ToolServer is another app from Apple that provides access to MPW tools from MPW and the MacPerl app, which allows MacPerl programs to use C, backticks, and piped C. =end original ToolServer �� Apple �ˤ��⤦��Ĥ� app �ǡ�MPW �� MacPerl app ���� MPW tools �ؤΥ����������󶡤��ޤ�; MacPerl �ץ�����ब C, �ե������ȡ��ѥ��� C ��Ȥ���褦�ˤ��ޤ��� =begin original "S" is the proper name for the operating system, but the value in C<$^O> is "MacOS". To determine architecture, version, or whether the application or MPW tool version is running, check: =end original "S" �ϥ��ڥ졼�ƥ��󥰥����ƥ�Ȥ���Ŭ�ڤ�̾���Ǥ�����C<$^O> ���ͤ� "MacOS"�� �������ƥ����㡢�С�����󡢥��ץꥱ������� MPW tool �Ǥ� �¹Ԥ���Ƥ��뤫����ꤹ��ˤϡ��ʲ��Τ褦�˥����å����Ƥ�������: $is_app = $MacPerl::Version =~ /App/; $is_tool = $MacPerl::Version =~ /MPW/; ($version) = $MacPerl::Version =~ /^(\S+)/; $is_ppc = $MacPerl::Architecture eq 'MacPPC'; $is_68k = $MacPerl::Architecture eq 'Mac68K'; =begin original S, based on NeXT's OpenStep OS, runs MacPerl natively, under the "Classic" environment. There is no "Carbon" version of MacPerl to run under the primary Mac OS X environment. S and its Open Source version, Darwin, both run Unix perl natively. =end original NeXT's OpenStep OS ���ˤ��� S �� "Classic" �Ķ��� MacPerl ��ͥ��ƥ��֤˼¹Ԥ��ޤ��� ����Ū�� Mac OS X �Ķ���ư����뤿��� "Carbon" �Ǥ� MacPerl �Ϥ���ޤ��� S �Ȥ��Υ����ץ󥽡����ǤǤ��� Darwin ��ξ���� Unix perl �� �ͥ��ƥ��֤˼¹Ԥ��ޤ��� =begin original Also see: =end original �ʲ��⻲�Ȥ��Ƥ�������: =over 4 =item * =begin original MacPerl Development, http://dev.macperl.org/ . =end original MacPerl Development, http://dev.macperl.org/ �� =item * =begin original The MacPerl Pages, http://www.macperl.com/ . =end original The MacPerl Pages, http://www.macperl.com/ �� =item * =begin original The MacPerl mailing lists, http://lists.perl.org/ . =end original The MacPerl �᡼��󥰥ꥹ��, http://lists.perl.org/ �� =item * MPW, ftp://ftp.apple.com/developer/Tool_Chest/Core_Mac_OS_Tools/ =back =head2 VMS =begin original Perl on VMS is discussed in L in the perl distribution. =end original VMS �Ǥ� Perl �� perl ���ۤ� L �ǵ�������Ƥ��ޤ��� =begin original The official name of VMS as of this writing is OpenVMS. =end original �����񤤤Ƥ�������Ǥ� VMS ������̾�Τ� OpenVMS �Ǥ��� =begin original Perl on VMS can accept either VMS- or Unix-style file specifications as in either of the following: =end original VMS �Ǥ� Perl �ϡ� VMS ������ Unix �����Υե���������ξ���� �ʲ��Τɤ��餫�η��Ǥ�����դ��ޤ�: $ perl -ne "print if /perl_setup/i" SYS$LOGIN:LOGIN.COM $ perl -ne "print if /perl_setup/i" /sys$login/login.com =begin original but not a mixture of both as in: =end original �������ʲ��Τ褦��ξ���򺮤��뤳�ȤϤǤ��ޤ���: $ perl -ne "print if /perl_setup/i" sys$login:/login.com Can't open sys$login:/login.com: file specification syntax error =begin original Interacting with Perl from the Digital Command Language (DCL) shell often requires a different set of quotation marks than Unix shells do. For example: =end original Perl �� Digital Command Language (DCL) ������Ȥ���ߺ��ѤϤ��Ф��� Unix �����뤬�Ԥ��ΤȤ��Ȥʤ륯�����Ȥμ��बɬ�פˤʤ�ޤ��� �㤨��: $ perl -e "print ""Hello, world.\n""" Hello, world. =begin original There are several ways to wrap your perl scripts in DCL F<.COM> files, if you are so inclined. For example: =end original �⤷�����������ʤ顢DCL F<.COM> �ե������ perl ������ץȤ��åפ��� �����Ĥ�����ˡ������ޤ��� �㤨��: $ write sys$output "Hello from DCL!" $ if p1 .eqs. "" $ then perl -x 'f$environment("PROCEDURE") $ else perl -x - 'p1 'p2 'p3 'p4 'p5 'p6 'p7 'p8 $ deck/dollars="__END__" #!/usr/bin/perl print "Hello from Perl!\n"; __END__ $ endif =begin original Do take care with C<$ ASSIGN/nolog/user SYS$COMMAND: SYS$INPUT> if your perl-in-DCL script expects to do things like C<< $read = ; >>. =end original perl-in-DCL ������ץȤ� C<< $read = ; >> �Τ褦�ʤ��Ȥ� ���뤳�Ȥ����ꤷ�Ƥ���ʤ顢C<$ ASSIGN/nolog/user SYS$COMMAND: SYS$INPUT> �� ���դ��Ƥ��������� =begin original The VMS operating system has two filesystems, known as ODS-2 and ODS-5. =end original VMS ���ڥ졼�ƥ��󥰥����ƥ�ˤϡ�ODS-2 ����� ODS-5 �Ȥ����Τ��� ��ĤΥե����륷���ƥब����ޤ��� =begin original For ODS-2, filenames are in the format "name.extension;version". The maximum length for filenames is 39 characters, and the maximum length for extensions is also 39 characters. Version is a number from 1 to 32767. Valid characters are C. =end original ODS-2 �Ǥϡ��ե�����̾�� "name.extension;version" �η����Ǥ��� �ե�����̾�κ���Ĺ�� 39 ʸ���ǡ���ĥ�Ҥκ���Ĺ�� 39 ʸ���Ǥ��� version �� 1 ���� 32767 �ο��ͤǤ��� ������ʸ���� C �Ǥ��� =begin original The ODS-2 filesystem is case-insensitive and does not preserve case. Perl simulates this by converting all filenames to lowercase internally. =end original ODS-2 �ե����륷���ƥ�Ǥ���ʸ����ʸ����̵�뤷����ʸ����ʸ������¸���ޤ��� Perl �ϡ����ƤΥե�����̾�������Ǿ�ʸ�����Ѵ����뤳�ȤǤ���� ���ߥ�졼�Ȥ��ޤ��� =begin original For ODS-5, filenames may have almost any character in them and can include Unicode characters. Characters that could be misinterpreted by the DCL shell or file parsing utilities need to be prefixed with the C<^> character, or replaced with hexadecimal characters prefixed with the C<^> character. Such prefixing is only needed with the pathnames are in VMS format in applications. Programs that can accept the UNIX format of pathnames do not need the escape characters. The maximum length for filenames is 255 characters. The ODS-5 file system can handle both a case preserved and a case sensitive mode. =end original ODS-5 �Ǥϡ��ե�����̾�ϤۤȤ�ɤɤ��ʸ���Ǥ�Ȥ���Unicode ʸ����Ȥ��ޤ��� DCL �������ե�����ѡ����桼�ƥ���ƥ��ˤ�äƸ���ᤵ��뤫�⤷��ʤ� ʸ���� C<^> ʸ�������֤��뤫��C<^> ʸ�������֤��� 16 ��ʸ�����֤������� ɬ�פ�����ޤ��� ���Τ褦�����֤ϥѥ�̾�����ץꥱ���������� VMS �����λ��ˤΤ�ɬ�פǤ��� UNIX �����Υѥ�̾������դ���ץ�������ʸ���򥨥������פ���ɬ�פ� ����ޤ��� �ե�����̾�κ���Ĺ�� 255 ʸ���Ǥ��� ODS-5 �ե����륷���ƥ����ʸ����ʸ������¸������ʸ����ʸ����ǧ������⡼�ɤ� ξ���򰷤��ޤ��� =begin original ODS-5 is only available on the OpenVMS for 64 bit platforms. =end original ODS-5 �� 64 �ӥåȥץ�åȥե������ OpenVMS �ǤΤ����Ѳ�ǽ�Ǥ��� =begin original Support for the extended file specifications is being done as optional settings to preserve backward compatibility with Perl scripts that assume the previous VMS limitations. =end original ��ĥ�ե���������б��ϰ����� VMS �����¤��ꤹ�� Perl ������ץȤȤ� �����ߴ�������¸���뤿��˥��ץ���������Ȥ��ƹԤ��ޤ��� =begin original In general routines on VMS that get a UNIX format file specification should return it in a UNIX format, and when they get a VMS format specification they should return a VMS format unless they are documented to do a conversion. =end original VMS �� UNIX �����ե�������ͤ�Ȥ�����Ū�ʥ롼����Ǥϡ�UNIX ������ �֤��٤��ǡ�VMS �������ͤ������ä����ϡ��Ѵ������ʸ�񲽤���Ƥ��ʤ��¤� VMS �������֤��٤��Ǥ��� =begin original For routines that generate return a file specification, VMS allows setting if the C library which Perl is built on if it will be returned in VMS format or in UNIX format. =end original �֤��ե������������������롼����Ǥϡ�VMS �Ǥ� Perl ���ӥ�ɤ��줿 C �饤�֥�꤬ VMS �������֤��� UNIX �������֤���������Ǥ��ޤ��� =begin original With the ODS-2 file system, there is not much difference in syntax of filenames without paths for VMS or UNIX. With the extended character set available with ODS-5 there can be a significant difference. =end original ODS-2 �ե����륷���ƥ�Ǥϡ��ѥ�������ե�����̾��ʸˡ�� VMS �� UNIX �Ȥ��ޤ��Ѥ��ޤ��� ODS-5 �����Ѳ�ǽ�ʳ�ĥʸ������Ǥ��礭�ʰ㤤������ޤ��� =begin original Because of this, existing Perl scripts written for VMS were sometimes treating VMS and UNIX filenames interchangeably. Without the extended character set enabled, this behavior will mostly be maintained for backwards compatibility. =end original ���Τ��ᡢVMS �Τ���˽񤫤줿���ˤ��� Perl ������ץȤϻ��� VMS �� UNIX �ե�����̾��򴹲�ǽ�Ȥ��Ƥ��ޤ��� ��ĥʸ�����礬ͭ���Ǥʤ���С����ο����񤤤ϤۤȤ�ɸ����ߴ����Τ���� �ݻ�����Ƥ��ޤ��� =begin original When extended characters are enabled with ODS-5, the handling of UNIX formatted file specifications is to that of a UNIX system. =end original ODS-5 �dz�ĥʸ����ͭ���ξ�硢UNIX �����Υե�������ͤΰ����� UNIX �����ƥ�Τ�ΤǤ��� =begin original VMS file specifications without extensions have a trailing dot. An equivalent UNIX file specification should not show the trailing dot. =end original ��ĥ�Ҥʤ��� VMS �ե�������ͤ������˥ɥåȤ�����ޤ��� ������ UNIX �ե�������ͤ������ΥɥåȤ�ɽ�����ʤ��٤��Ǥ��� =begin original The result of all of this, is that for VMS, for portable scripts, you can not depend on Perl to present the filenames in lowercase, to be case sensitive, and that the filenames could be returned in either UNIX or VMS format. =end original ��������Ƥη�̤Ȥ��ơ�VMS �Ǥΰܿ����Τ��륹����ץȤȤ��Ƥϡ�Perl �� �ե�����̾����ʸ����ɽ������Ƥ����ꡢ��ʸ����ʸ������̤����ꡢ �ե�����̾�� UNIX �ޤ��� VMS �����Τɤ��餫���֤����Ȥ������Ȥ� ��¸�Ǥ��ޤ��� =begin original And if a routine returns a file specification, unless it is intended to convert it, it should return it in the same format as it found it. =end original �����Ƥ���롼���󤬤���ե�������ͤ��֤��ʤ顢���줬�Ѵ���տޤ��Ƥ��ʤ� �¤ꡢ���Ĥ����Τ�Ʊ���������֤����٤��Ǥ��� =begin original C by default has traditionally returned lowercased filenames. When the ODS-5 support is enabled, it will return the exact case of the filename on the disk. =end original �ǥե���Ȥ� C ������Ū�˾�ʸ���Υե�����̾���֤��ޤ��� ODS-5 �б���ͭ���ΤȤ����ǥ�������Υե�����̾�����Τ���ʸ����ʸ���� �֤��ޤ��� =begin original Files without extensions have a trailing period on them, so doing a C in the default mode with a file named F will return F when VMS is (though that file could be opened with C). =end original ��ĥ�Ҥʤ��Υե�����������˥ԥꥪ�ɤ��ͤ��Ƥ���Τǡ�F �Ȥ���̾���� �ǥե���ȥ⡼�ɤ� C ��Ԥ��ȡ�VMS �Ǥ� F ���֤��ޤ�(���������� �ե������ C �dz����ޤ�). =begin original With support for extended file specifications and if C was given a UNIX format directory, a file named F will return F and optionally in the exact case on the disk. When C is given a VMS format directory, then C should return F, and again with the optionally the exact case. =end original ��ĥ�ե�������ͤ��б����Ƥ��� C �� UNIX �����Υǥ��쥯�ȥ�� Ϳ������ȡ�F �Ȥ���̾���Υե������ F ���֤������ץ����Ȥ��� �ǥ�����������Τ���ʸ����ʸ�����֤��ޤ��� C �� VMS �����ǥ��쥯�ȥ��Ϳ������ȡ�C �� F �� �֤������ץ����Ȥ������Τ���ʸ����ʸ�����֤��ޤ��� =begin original RMS had an eight level limit on directory depths from any rooted logical (allowing 16 levels overall) prior to VMS 7.2, and even with versions of VMS on VAX up through 7.3. Hence C is a valid directory specification but C is not. F authors might have to take this into account, but at least they can refer to the former as C. =end original VMS 7.2 ��������ӡ�VAX �� VMS �Ǥ� 7.3 �⡢RMS �ˤ�Ǥ�դ������롼�Ȥ���� �ǥ��쥯�ȥ�ο�����8 ��٥�����¤���Ƥ��ޤ�(���ΤǤ� 16 ��٥�)�� ���ä� C �������ʥǥ��쥯�ȥ����Ǥ��� C �ϰ㤤�ޤ��� F �κ�ԤϤ����ͤ�������Ƥ���ɬ�פ����뤫�⤷��ޤ��󤬡� ���ʤ��Ȥ����Ԥ� C �Ȥ��ƻ��ȤǤ��ޤ��� =begin original Pumpkings and module integrators can easily see whether files with too many directory levels have snuck into the core by running the following in the top-level source directory: =end original �ѥ�ץ��󥰤ȥ⥸�塼������Ԥϡ��ʲ���ȥåץ�٥륽�����ǥ��쥯�ȥ�� �¹Ԥ��뤳�Ȥǡ���������ǥ��쥯�ȥ��٥����ĥե����뤬������ �ϥ󥰤����뤫�ɤ������ñ��Ĵ�٤��ޤ�: $ perl -ne "$_=~s/\s+.*//; print if scalar(split /\//) > 8;" < MANIFEST =begin original The VMS::Filespec module, which gets installed as part of the build process on VMS, is a pure Perl module that can easily be installed on non-VMS platforms and can be helpful for conversions to and from RMS native formats. It is also now the only way that you should check to see if VMS is in a case sensitive mode. =end original VMS �Υӥ�ɥץ������ΰ����Ȥ��ƥ��󥹥ȡ��뤵��� VMS::Filespec �⥸�塼��ϴ�ñ���� VMS �ץ�åȥե�����˥��󥹥ȡ������� RSM �ͥ��ƥ��ַ����Ȥ��Ѵ��ν����Ȥʤ�ԥ奢 Perl �⥸�塼��Ǥ��� ����Ϥ��ޤǤ� VMS ����ʸ����ʸ������̤���⡼�ɤ��ɤ���������å����� ͣ�����ˡ�Ǥ��� =begin original What C<\n> represents depends on the type of file opened. It usually represents C<\012> but it could also be C<\015>, C<\012>, C<\015\012>, C<\000>, C<\040>, or nothing depending on the file organization and record format. The VMS::Stdio module provides access to the special fopen() requirements of files with unusual attributes on VMS. =end original C<\n> ��ɽ�����Ƥ����Τϥե�����򳫤�����˰�¸���ޤ��� ���̤� C<\012> ��ɽ�����ޤ������ե�����ι����䵭Ͽ�����˰�¸���� C<\015>, C<\012>, C<\015\012>, C<\000>, C<\040> ���뤤�� ����ʤ����⤷��ޤ��� VMS::Stdio �⥸�塼��� VMS �Ǥ����̤Ǥʤ�°���դ��Υե������ �ü�� fopen() �ؤΥ����������󶡤��ޤ��� =begin original TCP/IP stacks are optional on VMS, so socket routines might not be implemented. UDP sockets may not be supported. =end original TCP/IP �����å��� VMS �Ǥϥ��ץ����ʤΤǡ������åȥ롼����� ��������Ƥ��ޤ��� UDP �����åȤ��б����Ƥ��ޤ��� =begin original The TCP/IP library support for all current versions of VMS is dynamically loaded if present, so even if the routines are configured, they may return a status indicating that they are not implemented. =end original ���ߤ����ƤΥС������� VMS �� TCP/IP �饤�֥���б��ϡ��⤷����� ưŪ���ɤ߹��ޤ��Τǡ��롼�������ꤵ��Ƥ����Ȥ��Ƥ⡢ ̤�����򼾤륹�ơ��������֤����⤷��ޤ��� =begin original The value of C<$^O> on OpenVMS is "VMS". To determine the architecture that you are running on without resorting to loading all of C<%Config> you can examine the content of the C<@INC> array like so: =end original OpenVMS �Ǥ� C<$^O> ���ͤ� "VMS" �Ǥ��� C<%Config> �������ɤ߹���Ȥ������ʤ�Ȥ鷺�˼¹Ԥ��Ƥ��륢�����ƥ������ ���ꤹ��ˤϡ��ʲ��Τ褦�ˤ��� @INC �������Ȥ��ǧ���ޤ�: if (grep(/VMS_AXP/, @INC)) { print "I'm on Alpha!\n"; } elsif (grep(/VMS_VAX/, @INC)) { print "I'm on VAX!\n"; } elsif (grep(/VMS_IA64/, @INC)) { print "I'm on IA64!\n"; } else { print "I'm not so sure about where $^O is...\n"; } =begin original In general, the significant differences should only be if Perl is running on VMS_VAX or one of the 64 bit OpenVMS platforms. =end original ����Ū�ˡ������ʰ㤤�� Perl �� VMS_VAX �ޤ��� 64 �ӥå� OpenVMS �ץ�åȥե�����Τɤ줫�Ǽ¹Ԥ���Ƥ���Ȥ��ˤΤߤ���ޤ��� =begin original On VMS, perl determines the UTC offset from the C logical name. Although the VMS epoch began at 17-NOV-1858 00:00:00.00, calls to C are adjusted to count offsets from 01-JAN-1970 00:00:00.00, just like Unix. =end original VMS �Ǥϡ�perl �� UTC ���ե��åȤ� C ����̾���� ���ꤷ�ޤ��� VMS �ε����� 17-NOV-1858 00:00:00.00 �˻Ϥޤ�ޤ�����C �θƤӽФ��� Unix ��Ʊ�� 01-JAN-1970 00:00:00.00 ����Υ��ե��åȤ�Ĵ������ޤ��� =begin original Also see: =end original �ʲ��⻲�Ȥ��Ƥ�������: =over 4 =item * =begin original F (installed as L), L =end original F (L �Ȥ��ƥ��󥹥ȡ��뤵��ޤ�), L =item * =begin original vmsperl list, vmsperl-subscribe@perl.org =end original vmsperl �᡼��󥰥ꥹ��: vmsperl-subscribe@perl.org =item * =begin original vmsperl on the web, http://www.sidhe.org/vmsperl/index.html =end original web ��� vmsperl: http://www.sidhe.org/vmsperl/index.html =back =head2 VOS =begin original Perl on VOS is discussed in F in the perl distribution (installed as L). Perl on VOS can accept either VOS- or Unix-style file specifications as in either of the following: =end original VOS �Ǥ� Perl �� perl ���ۤ� F (L �Ȥ��� ���󥹥ȡ��뤵��ޤ�) �ǵ�������Ƥ��ޤ��� VOS �Ǥ� Perl �ϡ��ʲ��Τɤ��餫�Τ褦�ˤ��ơ�VOS ������ Unix �����Τɤ���Υե�������������դ��ޤ�: $ perl -ne "print if /perl_setup/i" >system>notices $ perl -ne "print if /perl_setup/i" /system/notices =begin original or even a mixture of both as in: =end original ���뤤��ξ���򺮤���: $ perl -ne "print if /perl_setup/i" >system/notices =begin original Even though VOS allows the slash character to appear in object names, because the VOS port of Perl interprets it as a pathname delimiting character, VOS files, directories, or links whose names contain a slash character cannot be processed. Such files must be renamed before they can be processed by Perl. Note that VOS limits file names to 32 or fewer characters, file names cannot start with a C<-> character, or contain any character matching C<< tr/ !%&'()*+;<>?// >> =end original VOS �ϥ��֥�������̾�Ȥ��ƥ���å���ʸ��������뤳�Ȥ�����Ƥ��ޤ����� VOS �Ǥ� Perl ���󥿥ץ꥿�Ϥ����ѥ�̾��ʬ�䤹��ʸ���Ȥ��Ʋ�᤹��Τǡ� ̾���˥���å���ʸ����ޤ� VOS �ե����롢�ǥ��쥯�ȥꡢ��󥯤� �����Ǥ��ޤ��� ���Τ褦�ʥե������ Perl �ˤ�äƽ������������ ��͡��व��ʤ���Фʤ�ޤ��� VOS �ϥե�����̾�� 32 ʸ���ʲ������¤��Ƥ����ꡢ�ե�����̾�� C<-> ʸ���� �Ϥ���ʤ��ä��ꡢC<< tr/ !%&'()*+;<>?// >> �˥ޥå��󥰤��� ʸ����ޤळ�Ȥ��Ǥ��ʤ����Ȥ����դ��Ƥ��������� =begin original The value of C<$^O> on VOS is "VOS". To determine the architecture that you are running on without resorting to loading all of C<%Config> you can examine the content of the @INC array like so: =end original VOS �Ǥ� C<$^O> ���ͤ� "VOS" �Ǥ��� C<%Config> �������ɤ߹���Ȥ������ʤ�Ȥ鷺�˼¹Ԥ��Ƥ��륢�����ƥ������ ���ꤹ��ˤϡ��ʲ��Τ褦�ˤ��� @INC �������Ȥ��ǧ���ޤ�: if ($^O =~ /VOS/) { print "I'm on a Stratus box!\n"; } else { print "I'm not on a Stratus box!\n"; die; } =begin original Also see: =end original �ʲ��⻲�Ȥ��Ƥ�������: =over 4 =item * =begin original F (installed as L) =end original F (L �Ȥ��ƥ��󥹥ȡ��뤵��ޤ�) =item * =begin original The VOS mailing list. =end original VOS �᡼��󥰥ꥹ�ȡ� =begin original There is no specific mailing list for Perl on VOS. You can post comments to the comp.sys.stratus newsgroup, or subscribe to the general Stratus mailing list. Send a letter with "subscribe Info-Stratus" in the message body to majordomo@list.stratagy.com. =end original VOS �Ǥ� Perl ���ѤΥ᡼��󥰥ꥹ�ȤϤ���ޤ��� comp.sys.stratus �˥塼�����롼�פ���Ƥ��뤫������Ū�� Stratus �᡼��󥰥ꥹ�Ȥ���ɤ��Ƥ��������� ��å�������ʸ��"subscribe Info-Stratus" �Ƚ񤤤� majordomo@list.stratagy.com �˥᡼������äƤ��������� =item * =begin original VOS Perl on the web at http://ftp.stratus.com/pub/vos/posix/posix.html =end original web ��� VOS Perl: http://ftp.stratus.com/pub/vos/posix/posix.html =back =head2 EBCDIC Platforms (EBCDIC �ץ�åȥե�����) =begin original Recent versions of Perl have been ported to platforms such as OS/400 on AS/400 minicomputers as well as OS/390, VM/ESA, and BS2000 for S/390 Mainframes. Such computers use EBCDIC character sets internally (usually Character Code Set ID 0037 for OS/400 and either 1047 or POSIX-BC for S/390 systems). On the mainframe perl currently works under the "Unix system services for OS/390" (formerly known as OpenEdition), VM/ESA OpenEdition, or the BS200 POSIX-BC system (BS2000 is supported in perl 5.6 and greater). See L for details. Note that for OS/400 there is also a port of Perl 5.8.1/5.9.0 or later to the PASE which is ASCII-based (as opposed to ILE which is EBCDIC-based), see L. =end original �Ƕ�ΥС������� Perl �� AS/400 �ޥ���������ԥ塼���Ǥ� OS/400�� S/390 �ᥤ��ե졼��Ǥ� OS/390, VM/ESA, BS2000 �Τ褦�ʥץ�åȥե������ �ܿ�����Ƥ��ޤ��� ���Τ褦�ʥ���ԥ塼���������� EBCDIC ʸ������ (�̾�� OS/400 �Ǥ� Character Code Set ID 0037��S/390 �Ǥ� 1047 �ޤ��� POSIX-BC �� �ɤ��餫) �������ǻȤ��ޤ��� �ᥤ��ե졼�� perl �ϸ��ߤΤȤ��� "Unix system services for OS/390" (������ OpenEdition �Ȥ����Τ��Ƥ������), VM/ESA OpenEdition, BS200 POSIX-BC �����ƥ��ư��ޤ� (BS2000 �� 5.6 �ʹߤ��б����ޤ�)�� �ܤ����� L �򻲾Ȥ��Ƥ��������� OS/400 �ˤ� (EBCDIC �١����� ILE �ǤϤʤ�) ASCII �١����� PASE �ؤ� Perl 5.8.1/5.9.0 �ʹߤΰܿ��⤢�뤳�Ȥ����դ��Ƥ�������; L �� ���Ȥ��Ƥ��������� =begin original As of R2.5 of USS for OS/390 and Version 2.3 of VM/ESA these Unix sub-systems do not support the C<#!> shebang trick for script invocation. Hence, on OS/390 and VM/ESA perl scripts can be executed with a header similar to the following simple script: =end original OS/390 �� USS �� R2.5 ����� VM/ESA �ΥС������ 2.3 �ʹߡ� ������ Unix �������ƥ�ϥ�����ץȤε�ư�Τ���� C<#!> �ȥ�å��� �б����ʤ��ʤ�ޤ����� ���äơ�OS/390 �� VM/ESA �Ǥ� perl ������ץȤϰʲ��Τ褦��ñ��� ������ץȤȻ����إå��դ��Ǽ¹ԤǤ��ޤ�: : # use perl eval 'exec /usr/local/bin/perl -S $0 ${1+"$@"}' if 0; #!/usr/local/bin/perl # just a comment really print "Hello from perl!\n"; =begin original OS/390 will support the C<#!> shebang trick in release 2.8 and beyond. Calls to C and backticks can use POSIX shell syntax on all S/390 systems. =end original OS/390 �ϥ�꡼�� 2.8 �ʹߡ�C<#!> �ȥ�å����б����Ƥ��ޤ��� C �ȵե������ȤθƤӽФ������Ƥ� S/390 �����ƥ�� POSIX ������ʸˡ�� �Ȥ��ޤ��� =begin original On the AS/400, if PERL5 is in your library list, you may need to wrap your perl scripts in a CL procedure to invoke them like so: =end original AS/400 �Ǥϡ��饤�֥��ꥹ�Ȥ� PERL5 ������С��ʲ��Τ褦�ˤ��� CL ��³���� perl ������ץȤ��åפ���ɬ�פ�����ޤ�: BEGIN CALL PGM(PERL5/PERL) PARM('/QOpenSys/hello.pl') ENDPGM =begin original This will invoke the perl script F in the root of the QOpenSys file system. On the AS/400 calls to C or backticks must use CL syntax. =end original ����� QOpenSys �ե����륷���ƥ�Υ롼�Ȥˤ��� perl ������ץ� F ��ư���ޤ��� AS/400 �Ǥ� C ��ե������ȤθƤӽФ��� CL ʸˡ�� �Ȥ�ʤ���Фʤ�ޤ��� =begin original On these platforms, bear in mind that the EBCDIC character set may have an effect on what happens with some perl functions (such as C, C, C, C, C, C, C, C), as well as bit-fiddling with ASCII constants using operators like C<^>, C<&> and C<|>, not to mention dealing with socket interfaces to ASCII computers (see L<"Newlines">). =end original �����Υץ�åȥե�����Ǥϡ�(C, C, C, C, C, C, C, C �Τ褦��) ������ perl �δؿ�����ӡ�C<^>, C<&>, C<|> �Τ褦�ʱ黻�Ҥ�Ȥä� ASCII ����Υӥå����Ǥθ��̤� EBCDIC ʸ���Ǥϰۤʤ뤳�Ȥ����뤳�Ȥ� ���դ��Ƥ�������; ASCII ����ԥ塼���ؤΥ����åȥ��󥿡��ե������� �������Ȥ���ڤ��ޤ��� (L<"Newlines"> ����)�� =begin original Fortunately, most web servers for the mainframe will correctly translate the C<\n> in the following statement to its ASCII equivalent (C<\r> is the same under both Unix and OS/390 & VM/ESA): =end original �����ˤ⡢�ᥤ��ե졼��ΤۤȤ�ɤ� web �����Фϰʲ���ʸ�� C<\n> �� ASCII ������ʪ���������Ѵ����ޤ� (C<\r> �� Unix �� OS/390 & VM/ESA ��Ʊ���Ǥ�): print "Content-type: text/html\r\n\r\n"; =begin original The values of C<$^O> on some of these platforms includes: =end original �����Υץ�åȥե������ C<$^O> ���ͤϰʲ��Τ褦�ʤ�ΤǤ�: uname $^O $Config{'archname'} -------------------------------------------- OS/390 os390 os390 OS400 os400 os400 POSIX-BC posix-bc BS2000-posix-bc VM/ESA vmesa vmesa =begin original Some simple tricks for determining if you are running on an EBCDIC platform could include any of the following (perhaps all): =end original EBCDIC �ץ�åȥե�����Ǽ¹Ԥ���Ƥ��뤫�ɤ�������ꤹ�뤿��� ñ��ʥȥ�å��Ȥ��Ƥϡ��ʲ��Τɤ줫(�����餯����)������ޤ�: if ("\t" eq "\05") { print "EBCDIC may be spoken here!\n"; } if (ord('A') == 193) { print "EBCDIC may be spoken here!\n"; } if (chr(169) eq 'z') { print "EBCDIC may be spoken here!\n"; } =begin original One thing you may not want to rely on is the EBCDIC encoding of punctuation characters since these may differ from code page to code page (and once your module or script is rumoured to work with EBCDIC, folks will want it to work with all EBCDIC character sets). =end original ��¸�������Ȼפ�ʤ����������Ȥΰ�Ĥϡ�������ʸ���� EBCDIC ���󥳡��ɤǤ��礦; �����ϥ����ɥڡ����ˤ�äưۤʤ뤫��Ǥ� (�����ư�ö���ʤ��Υ⥸�塼��䥹����ץȤ� EBCDIC ��ư���ȱ������ȡ� �͡������Ƥ� EBCDIC ʸ�������ư��뤳�Ȥ���ޤ�)�� =begin original Also see: =end original �ʲ��⻲�Ȥ��Ƥ�������: =over 4 =item * =begin original L, F, F, F, L. =end original L, F, F, F, L =item * =begin original The perl-mvs@perl.org list is for discussion of porting issues as well as general usage issues for all EBCDIC Perls. Send a message body of "subscribe perl-mvs" to majordomo@perl.org. =end original perl-mvs@perl.org �᡼��󥰥ꥹ�Ȥϰܿ������ꤪ������Ƥ� EBCDIC Perl �� �ؤ������Ū�ʻ���ˡ�ˤĤ��Ƶ������뤿���ʪ�Ǥ��� ��å��������Τ� "subscribe perl-mvs" �Ƚ񤤤� majordomo@perl.org �� ���äƤ��������� =item * =begin original AS/400 Perl information at http://as400.rochester.ibm.com/ as well as on CPAN in the F directory. =end original AS/400 Perl information at http://as400.rochester.ibm.com/ ����� CPAN �� F �ǥ��쥯�ȥꡣ =back =head2 Acorn RISC OS =begin original Because Acorns use ASCII with newlines (C<\n>) in text files as C<\012> like Unix, and because Unix filename emulation is turned on by default, most simple scripts will probably work "out of the box". The native filesystem is modular, and individual filesystems are free to be case-sensitive or insensitive, and are usually case-preserving. Some native filesystems have name length limits, which file and directory names are silently truncated to fit. Scripts should be aware that the standard filesystem currently has a name length limit of B<10> characters, with up to 77 items in a directory, but other filesystems may not impose such limitations. =end original Acorns �� Unix ��Ʊ�� ASCII ��Ȥ����ƥ����ȥե�����β��� (C<\n>) �� C<\012> ��Ȥ��Τȡ�Unix �ե�����̾���ߥ�졼����󤬥ǥե���Ȥ� ͭ���ʤΤǡ��ۤȤ�ɤ�ñ��ʥ�����ץȤϤ����餯�֤��Τޤޡפ�ư��ޤ��� �ͥ��ƥ��֤ʥե����륷���ƥ�ϥ⥸��顼�����ǡ��ġ��Υե����륷���ƥ�� ��ʸ����ʸ������̤��뤫���ʤ����ϴط��ʤ������̤���ʸ����ʸ������¸���ޤ��� �ͥ��ƥ��֤ʥե����륷���ƥ�ΰ�����̾����Ĺ�������¤����ꡢ �ե�����̾�ȥǥ��쥯�ȥ�̾�ϼ��ޤ�褦�˰��ۤ��ڤ�ͤ���ޤ��� ������ץȤϡ�ɸ��ե����륷���ƥ��̾����Ĺ���� B<10> �����¤��졢��Ĥ� �ǥ��쥯�ȥ��77 �����ƥ�ޤǤ����¤���뤳�Ȥ����դ���٤��Ǥ�; ������¾�Υե����륷���ƥ�Ϥ��Τ褦�����¤Ϥʤ����⤷��ޤ��� =begin original Native filenames are of the form =end original �ͥ��ƥ��֤ʥե�����̾�ϰʲ��η����Ǥ�: Filesystem#Special_Field::DiskName.$.Directory.Directory.File =begin original where =end original ���줾��ϰʲ����̤�Ǥ�: Special_Field is not usually present, but may contain . and $ . Filesystem =~ m|[A-Za-z0-9_]| DsicName =~ m|[A-Za-z0-9_/]| $ represents the root directory . is the path separator @ is the current directory (per filesystem but machine global) ^ is the parent directory Directory and File =~ m|[^\0- "\.\$\%\&:\@\\^\|\177]+| =begin original The default filename translation is roughly C =end original �ǥե���ȥե�����̾�Ѵ��Ϥ������� C �Ǥ��� =begin original Note that C<"ADFS::HardDisk.$.File" ne 'ADFS::HardDisk.$.File'> and that the second stage of C<$> interpolation in regular expressions will fall foul of the C<$.> if scripts are not careful. =end original C<"ADFS::HardDisk.$.File" ne 'ADFS::HardDisk.$.File'> �ȡ�����ɽ����� C<$> Ÿ������ 2 ���ơ����ϡ�������ץȤ����տ����ʤ���� C<$.> �� ��Ȥ����Ȥ����դ��Ƥ��������� =begin original Logical paths specified by system variables containing comma-separated search lists are also allowed; hence C is a valid filename, and the filesystem will prefix C with each section of C until a name is made that points to an object on disk. Writing to a new file C would be allowed only if C contains a single item list. The filesystem will also expand system variables in filenames if enclosed in angle brackets, so C<< .Modules >> would look for the file S>. The obvious implication of this is that B >>> and should be protected when C is used for input. =end original ����޶��ڤ�θ����ꥹ�Ȥ�ޤॷ���ƥ��ѿ��ǻ��ꤵ�줿�����ѥ���Ȥ��ޤ�; ���ä� C �������ʥե�����̾�ǡ� �ե����륷���ƥ�ϡ�̾�����ǥ�������Υ��֥������Ȥ�ؤ��褦�ˤʤ�ޤ� C �Τ��줾�����ʬ�� C �����֤��ޤ��� C ��ñ��Υ����ƥ�ꥹ�Ȥ��ޤޤ�Ƥ�����ˤΤߡ� �������ե����� C �˽񤭹���ޤ��� �ե����륷���ƥ�ϥե�����̾�˥����ƥ��ѿ����Ѥ��ä��ǰϤޤ�Ƥ���� Ÿ������Τǡ� C<< .Modules >> �� S> �Ȥ����ե������õ���ޤ��� �����������餫�˿�¬����뤳�Ȥϡ� B<���������ե�����̾�� C<< <> >> �ǻϤޤ뤳�Ȥ�����>��C �� ���ϤǻȤ���Ȥ����ݸ���٤��Ȥ������ȤǤ��� =begin original Because C<.> was in use as a directory separator and filenames could not be assumed to be unique after 10 characters, Acorn implemented the C compiler to strip the trailing C<.c> C<.h> C<.s> and C<.o> suffix from filenames specified in source code and store the respective files in subdirectories named after the suffix. Hence files are translated: =end original C<.> ���ǥ��쥯�ȥꥻ�ѥ졼���Ȥ��ƻȤ��Ƥ��ơ��ե�����̾�� 10 ʸ���� �ʹߤϥ�ˡ����Ǥ���Ȳ���Ǥ��ʤ��Τǡ�Acorn �ϥ�������������˻��ꤵ�줿 �ե�����̾���������� C<.c> C<.h> C<.s>, C<.o> ��ĥ�Ҥ��ڤ���Ȥ��ơ� ��ĥ�Ҥ�̾���Υ��֥ǥ��쥯�ȥ�ˤ��줾��Υե�������ݴɤ���褦�ʷ��� C ����ѥ����������ޤ����� ���äƥե�������Ѵ�����ޤ�: foo.h h.foo C:foo.h C:h.foo (logical path variable) sys/os.h sys.h.os (C compiler groks Unix-speak) 10charname.c c.10charname 10charname.o o.10charname 11charname_.c c.11charname (assuming filesystem truncates at 10) =begin original The Unix emulation library's translation of filenames to native assumes that this sort of translation is required, and it allows a user-defined list of known suffixes that it will transpose in this fashion. This may seem transparent, but consider that with these rules C and C both map to C, and that C and C cannot and do not attempt to emulate the reverse mapping. Other C<.>'s in filenames are translated to C. =end original Unix ���ߥ�졼�����饤�֥��Υե�����̾�Υͥ��ƥ��֤ؤ��Ѵ��� ���μ���Ѵ���ɬ�פǤ��뤳�Ȥ��ꤷ�Ƥ��ơ�������ˡ�������ؤ�����Τ� ��ĥ�ҤΥꥹ�Ȥ�桼��������Ǥ���褦�ˤʤäƤ��ޤ��� �����Ʃ��Ū�˻פ��ޤ����������ε�§�Ǥ� C �� C ��ξ���� C �˥ޥåԥ󥰤��졢C �� C �ϵեޥåԥ󥰤Υ��ߥ�졼�Ȥ��ߤ뤳�Ȥ��Ǥ��ʤ����Ȥ� ��θ���Ƥ��������� �ե�����̾��Τ���¾�� C<.> �� C ���Ѵ�����ޤ��� =begin original As implied above, the environment accessed through C<%ENV> is global, and the convention is that program specific environment variables are of the form C. Each filesystem maintains a current directory, and the current filesystem's current directory is the B current directory. Consequently, sociable programs don't change the current directory but rely on full pathnames, and programs (and Makefiles) cannot assume that they can spawn a child process which can change the current directory without affecting its parent (and everyone else for that matter). =end original ���Ǥ˰ż������褦�ˡ�C<%ENV> ���̤��ƥ�����������Ķ��ϥ������Х�ǡ� �ץ�������ͭ�Ķ��ѿ��� C �η����Ѵ�����ޤ��� ���줾��Υե����륷���ƥ�ϥ����ȥǥ��쥯�ȥ������������ߤ� �ե����륷���ƥ�Υ����ȥǥ��쥯�ȥ�� B<�������Х��> �����ȥǥ��쥯�ȥ�Ǥ��� ���äơ��Ҹ�Ū�ʥץ������ϥ����ȥǥ��쥯�ȥ���ѹ������� �ե�ѥ�̾����ꡢ�ץ������(����� Makefile) �Ͽ� (����Ӥ��ΰ�̣�Ǥ� ����¾��������)�˱ƶ���Ϳ�����˥����ȥǥ��쥯�ȥ���ѹ��Ǥ��� �ҥץ�����������Ǥ���Ȳ���Ǥ��ޤ��� =begin original Because native operating system filehandles are global and are currently allocated down from 255, with 0 being a reserved value, the Unix emulation library emulates Unix filehandles. Consequently, you can't rely on passing C, C, or C to your children. =end original �ͥ��ƥ��֥��ڥ졼�ƥ��󥰥����ƥ�ե�����ϥ�ɥ�ϥ������Х�� ���ߤΤȤ��� 255 ���鲼�����˳�����Ƥ�졢0 ��ͽ�󤵤줿�ͤʤΤǡ� Unix ���ߥ�졼�����饤�֥��� Unix �ե�����ϥ�ɥ�򥨥ߥ�졼�Ȥ��ޤ��� ���äơ�C, C, C ��ҥץ��������Ϥ����Ȥ� ���ޤ��� =begin original The desire of users to express filenames of the form C<< .Bar >> on the command line unquoted causes problems, too: C<``> command output capture has to perform a guessing game. It assumes that a string C<< <[^<>]+\$[^<>]> >> is a reference to an environment variable, whereas anything else involving C<< < >> or C<< > >> is redirection, and generally manages to be 99% right. Of course, the problem remains that scripts cannot rely on any Unix tools being available, or that any tools found have Unix-like command line arguments. =end original ���ޥ�ɥ饤��ǥ������Ȥʤ��� C<< .Bar >> �����Υե�����̾�� ���Ҥ���Ȥ����桼�������ߵ�����������������ޤ�: C<``> ���ޥ�ɽ��� ��ª�Ͽ���������򤹤�ɬ�פ�����ޤ��� C<< <[^<>]+\$[^<>]> >> �ϴĶ��ѿ��λ��ȡ�����ʳ��� C<< < >> �� C<< > >> �� �ط��������Ƥϥ�����쥯�Ȥȿ�¬��������ϰ���Ū�˲��Ȥ� 99% ���������Ǥ��� ������󡢥�����ץȤϤɤ� Unix �ġ��뤬���Ѳ�ǽ�Ǥ��뤳�Ȥ䡢���Ĥ��� �ġ��뤬 Unix ���Υ��ޥ�ɥ饤��������뤳�Ȥˤ����ʤ��Ȥ�������� �ĤäƤ��ޤ��� =begin original Extensions and XS are, in theory, buildable by anyone using free tools. In practice, many don't, as users of the Acorn platform are used to binary distributions. MakeMaker does run, but no available make currently copes with MakeMaker's makefiles; even if and when this should be fixed, the lack of a Unix-like shell will cause problems with makefile rules, especially lines of the form C, and anything using quoting. =end original �������ƥ󥷥��� XS �ϡ�����Ū�ˤϡ���ͳ�ʥġ����Ȥä�ï�Ǥ� �ӥ�ɤǤ��ޤ��� �ºݤˤϡ�¿���οͤϤǤ��ޤ���; Acorn �ץ�åȥե�����Υ桼������ �Х��ʥ����ۤ�ȤäƤ��뤫��Ǥ��� MakeMaker �ϼ¹ԤǤ��ޤ��������ߤΤȤ��� MakeMaker �� makefile ������Ǥ��� make �Ϥ���ޤ���; ���Ȥ����줬��������Ƥ⡢Unix �������뤬�ʤ��Τ� makefile ��§�����꤬������ޤ�; �ä� C �����ιԤ䡢 �������Ȥ�Ȥä���ΤǤ��� =begin original "S" is the proper name for the operating system, but the value in C<$^O> is "riscos" (because we don't like shouting). =end original "S" �ϥ��ڥ졼�ƥ��󥰥����ƥ��Ŭ�ڤ�̾���Ǥ�����C<$^O> ���ͤ� "riscos" (��ʸ���Ϲ��ޤʤ�����Ǥ�)�� =head2 Other perls (����¾�� perl) =begin original Perl has been ported to many platforms that do not fit into any of the categories listed above. Some, such as AmigaOS, Atari MiNT, BeOS, HP MPE/iX, QNX, Plan 9, and VOS, have been well-integrated into the standard Perl source code kit. You may need to see the F directory on CPAN for information, and possibly binaries, for the likes of: aos, Atari ST, lynxos, riscos, Novell Netware, Tandem Guardian, I (Yes, we know that some of these OSes may fall under the Unix category, but we are not a standards body.) =end original Perl �Ͼ�Ҥ������ƥ�������Τɤ�ˤ����ƤϤޤ�ʤ��褦��¿���� �ץ�åȥե�����˰ܿ�����Ƥ��ޤ��� AmigaOS, Atari MiNT, BeOS, HP MPE/iX, QNX, Plan 9, VOS �Τ褦�� �����Τ�Τ�ɸ�� Perl �����������ɥ��åȤȤ褯���礵��Ƥ��ޤ��� Atari ST, lynxos, riscos, Novell Netware, Tandem Guardian I<�ʤ�> �� �褦�ʤ�ΤˤĤ��Ƥξ���Ȥ����餯�Х��ʥ�����뤿��� CPAN �� F �ǥ��쥯�ȥ�򸫤�ɬ�פ����뤫�⤷��ޤ���: (�Ϥ��������� OS �ΰ����� Unix ���ƥ�������뤳�Ȥ��ΤäƤ��ޤ����� �䤿����ɸ����ȿ��ǤϤ���ޤ���) =begin original Some approximate operating system names and their C<$^O> values in the "OTHER" category include: =end original "OTHER" ���ƥ���ˤ��뤤���Ĥ��ζ�����ڥ졼�ƥ��󥰥����ƥ�̾�� ���� C<$^O> ���ͤϰʲ��Τ褦�ʤ�ΤǤ�: OS $^O $Config{'archname'} ------------------------------------------ Amiga DOS amigaos m68k-amigos BeOS beos MPE/iX mpeix PA-RISC1.1 =begin original See also: =end original �ʲ��⻲�Ȥ��Ƥ�������: =over 4 =item * =begin original Amiga, F (installed as L). =end original Amiga, F (L �Ȥ��ƥ��󥹥ȡ��뤵��ޤ�) =item * =begin original Atari, F and Guido Flohr's web page http://stud.uni-sb.de/~gufl0000/ =end original Atari, F �� Guido Flohr �� web �ڡ��� http://stud.uni-sb.de/~gufl0000/ =item * Be OS, F =item * =begin original HP 300 MPE/iX, F and Mark Bixby's web page http://www.bixby.org/mark/perlix.html =end original HP 300 MPE/iX, F �� Mark Bixby �� web �ڡ��� http://www.bixby.org/mark/perlix.html =item * =begin original A free perl5-based PERL.NLM for Novell Netware is available in precompiled binary and source code form from http://www.novell.com/ as well as from CPAN. =end original Novell Netware �ѤΥե꡼�� perl5 �١����� PERL.NLM �ϡ�����ѥ���Ѥߤ� �Х��ʥ�ȥ����������ɷ����� http://www.novell.com/ ����� CPAN ���� ���Ѳ�ǽ�Ǥ��� =item * S, F =back =head1 FUNCTION IMPLEMENTATIONS (�ؿ�����) =begin original Listed below are functions that are either completely unimplemented or else have been implemented differently on various platforms. Following each description will be, in parentheses, a list of platforms that the description applies to. =end original �ʲ��ΰ����ϡ��ץ�åȥե�����ˤ�ä�������������Ƥ��ʤ����� ����ʤ���аۤʤä����Ǽ�������Ƥ���ؿ��Ǥ��� ���줾��ε��Ҥˤ��뤫�ä��ϡ����Ҥ�Ŭ�Ѥ����ץ�åȥե�����ΰ����Ǥ��� =begin original The list may well be incomplete, or even wrong in some places. When in doubt, consult the platform-specific README files in the Perl source distribution, and any other documentation resources accompanying a given port. =end original �������Դ����Ǥ��ä��ꡢ�����Ǵְ�äƤ����ǽ��������ޤ��� ���路���Ȥ��ϡ�Perl ���������ۤΥץ�åȥե������ͭ�� README �ե�����䡢 �ץ�åȥե�����˴�Ϣ���뤽��¾��ʸ��꥽����������å����Ƥ��������� =begin original Be aware, moreover, that even among Unix-ish systems there are variations. =end original ����ˡ�Unix �������ƥ�ˤ�Хꥨ������󤬤��뤳�Ȥ����դ��Ƥ��������� =begin original For many functions, you can also query C<%Config>, exported by default from the Config module. For example, to check whether the platform has the C call, check C<$Config{d_lstat}>. See L for a full description of available variables. =end original ¿���δؿ��˴ؤ��ơ�Config �⥸�塼�뤫��ǥե���Ȥǥ������ݡ��Ȥ���� C<%Config> ���䤤��碌�뤳�Ȥ�Ǥ��ޤ��� �㤨�С��ץ�åȥե������ C �ƤӽФ������뤫�ɤ�����Ĵ�٤�ˤϡ� C<$Config{d_lstat}> ��Ĵ�٤Ƥ��������� ���Ѳ�ǽ���ѿ��δ����������ˤĤ��Ƥ� L �򻲾Ȥ��Ƥ��������� =head2 Alphabetical Listing of Perl Functions (Perl �ؿ��Υ���ե��٥åȽ�ꥹ��) =over 8 =item -X =begin original C<-r>, C<-w>, and C<-x> have a limited meaning only; directories and applications are executable, and there are no uid/gid considerations. C<-o> is not supported. (S) =end original C<-r>, C<-w>, C<-x> �ϸ¤�줿��̣��������ޤ���; �ǥ��쥯�ȥ�� ���ץꥱ�������ϼ¹Բ�ǽ�ǡ�uid/gid �Ȥ�����ǰ�Ϥ���ޤ��� C<-o> ���б����Ƥ��ޤ��� (S) =begin original C<-w> only inspects the read-only file attribute (FILE_ATTRIBUTE_READONLY), which determines whether the directory can be deleted, not whether it can be written to. Directories always have read and write access unless denied by discretionary access control lists (DACLs). (S) =end original C<-w> ���ɤ߹������ѥե�����°�� (FILE_ATTRIBUTE_READONLY) �Τߤ�Ĵ�٤ޤ�; ����ϥǥ��쥯�ȥ�˽񤭹���뤫�ɤ����ǤϤʤ��ǥ��쥯�ȥ꤬ ����Ǥ��뤫�ɤ�������ꤷ�ޤ��� �ǥ��쥯�ȥ�ϡ���ե�����������ꥹ�� (DACL) �ǵ��ݤ���ʤ��¤ꡢ��� �ɤ߽񤭥��������Ǥ��ޤ��� (S) =begin original C<-r>, C<-w>, C<-x>, and C<-o> tell whether the file is accessible, which may not reflect UIC-based file protections. (VMS) =end original C<-r>, C<-w>, C<-x>, C<-o> �ϥե����뤬����������ǽ���ɤ������֤��� UIC �١����Υե������ݸ��ȿ�Ǥ��ޤ��� (VMS) =begin original C<-s> returns the size of the data fork, not the total size of data fork plus resource fork. (S). =end original C<-s> �ϥǡ����ե������ȥ꥽�����ե������ι�ץ������ǤϤʤ��� �ǡ����ե������Υ��������֤��ޤ��� (S) =begin original C<-s> by name on an open file will return the space reserved on disk, rather than the current extent. C<-s> on an open filehandle returns the current size. (S) =end original �����Ƥ���ե�����ؤ�̾���Ǥ� C<-s> �ϡ����ߤΥ������ƥ�ȤǤϤʤ��� �ǥ��������ͽ�󤵤�Ƥ�����֤��֤��ޤ��� �����Ƥ���ե�����ϥ�ɥ�ؤ� C<-s> �ϸ��ߤΥ��������֤��ޤ��� (S) =begin original C<-R>, C<-W>, C<-X>, C<-O> are indistinguishable from C<-r>, C<-w>, C<-x>, C<-o>. (S, Win32, VMS, S) =end original C<-R>, C<-W>, C<-X>, C<-O> �ϡ�C<-r>, C<-w>, C<-x>, C<-o> �� ���̤��դ��ޤ��� (S, Win32, VMS, S) =begin original C<-b>, C<-c>, C<-k>, C<-g>, C<-p>, C<-u>, C<-A> are not implemented. (S) =end original C<-b>, C<-c>, C<-k>, C<-g>, C<-p>, C<-u>, C<-A> �ϼ�������Ƥ��ޤ��� (S) =begin original C<-g>, C<-k>, C<-l>, C<-p>, C<-u>, C<-A> are not particularly meaningful. (Win32, VMS, S) =end original C<-g>, C<-k>, C<-l>, C<-p>, C<-u>, C<-A> ���ä˰�̣�Ϥ���ޤ��� (Win32, VMS, S) =begin original C<-d> is true if passed a device spec without an explicit directory. (VMS) =end original C<-d> �ϡ�����Ū�ʥǥ��쥯�ȥ�ʤ��� device spec ���Ϥ����ȿ��ˤʤ�ޤ��� (VMS) =begin original C<-T> and C<-B> are implemented, but might misclassify Mac text files with foreign characters; this is the case will all platforms, but may affect S often. (S) =end original C<-T> �� C<-B> �ϼ�������Ƥ��ޤ����������ʸ�����ޤޤ줿 Mac text �ե������ְ�ä�Ƚ�ꤹ�뤳�Ȥ�����ޤ���; ��������Ƥ� �ץ�åȥե�����ǵ�����ޤ�����S �Ǥ褯�ƶ�������ޤ��� (S) =begin original C<-x> (or C<-X>) determine if a file ends in one of the executable suffixes. C<-S> is meaningless. (Win32) =end original C<-x> (�ޤ��� C<-X>) �ϥե����뤬�¹Բ�ǽ�ե�����γ�ĥ�ҤΤɤ줫�� ����äƤ��뤫��Ƚ�ꤷ�ޤ��� C<-S> ��̵��̣�Ǥ��� (Win32) =begin original C<-x> (or C<-X>) determine if a file has an executable file type. (S) =end original C<-x> (�ޤ��� C<-X>) �ե����뤬�¹Բ�ǽ�ե����뷿���ɤ����� ���ꤷ�ޤ��� (S) =item atan2 =begin original Due to issues with various CPUs, math libraries, compilers, and standards, results for C may vary depending on any combination of the above. Perl attempts to conform to the Open Group/IEEE standards for the results returned from C, but cannot force the issue if the system Perl is run on does not allow it. (Tru64, HP-UX 10.20) =end original �͡��� CPU�����ͱ黻�饤�֥�ꡢ����ѥ��顢ɸ�������ˤ�ꡢC �� ��̤Ͼ�Ҥ��Ȥ߹�碌�˰�¸�����͡��˰ۤʤ�ޤ��� Perl �� C �����֤�����̤� Open Group/IEEE ɸ��� ��򤵤��褦�Ȥ��ޤ����������ƥ�� Perl �����������ʤ��Ȥ����� ư��Ƥ������������������뤳�ȤϤǤ��ޤ��� (Tru64, HP-UX 10.20) =begin original The current version of the standards for C is available at L. =end original C �θ��ߤΥС�������ɸ��� L �� ���Ѳ�ǽ�Ǥ��� =item binmode =begin original Meaningless. (S, S) =end original ̵��̣�Ǥ��� (S, S) =begin original Reopens file and restores pointer; if function fails, underlying filehandle may be closed, or pointer may be in a different position. (VMS) =end original �ե�����κƥ����ץ�ȥݥ��󥿤�����; �ؿ������Ԥ���ȡ���Ȥʤ� �ե�����ϥ�ɥ뤬�Ĥ���줿�ꡢ�ݥ��󥿤��ۤʤä����֤򼨤����Ȥ� ����ޤ��� (VMS) =begin original The value returned by C may be affected after the call, and the filehandle may be flushed. (Win32) =end original C �����֤��줿�ͤϤ��θƤӽФ��θ�˱ƶ�������뤳�Ȥ����ꡢ �ե�����ϥ�ɥ뤬�ե�å��夵��뤳�Ȥ�����ޤ��� (Win32) =item chmod =begin original Only limited meaning. Disabling/enabling write permission is mapped to locking/unlocking the file. (S) =end original �¤�줿��̣��������ޤ��� �񤭹��߸��¤�̵��/ͭ���ϥե�����Υ��å�/������å��˳�����Ƥ��ޤ��� (S) =begin original Only good for changing "owner" read-write access, "group", and "other" bits are meaningless. (Win32) =end original �ֽ�ͭ�ԡ��ɤ߽񤭥����������ѹ��Τ�ư����֥��롼�סס֤���¾�פΥӥåȤ� ̵��̣�Ǥ��� (Win32) =begin original Only good for changing "owner" and "other" read-write access. (S) =end original �ֽ�ͭ�ԡפȡ֤���¾�פ��ɤ߽񤭥����������ѹ��Τ�ư��ޤ��� (S) =begin original Access permissions are mapped onto VOS access-control list changes. (VOS) =end original �����������Ĥ� VOS ������������ꥹ���ѹ��˳�����Ƥ��ޤ��� (VOS) =begin original The actual permissions set depend on the value of the C in the SYSTEM environment settings. (Cygwin) =end original �ºݤε��Ĥ� SYSTEM �Ķ������ C ���ͤ˰�¸�������ꤵ��ޤ��� (Cygwin) =item chown =begin original Not implemented. (S, Win32, S, S) =end original ��������Ƥ��ޤ��� (S, Win32, S, S) =begin original Does nothing, but won't fail. (Win32) =end original ���⤷�ޤ��󤬼��Ԥ⤷�ޤ��� (Win32) =begin original A little funky, because VOS's notion of ownership is a little funky (VOS). =end original VOS �Ǥν�ͭ�Ԥγ�ǰ�Ͼ����ѤʤΤǡ������ѤǤ��� (VOS) =item chroot =begin original Not implemented. (S, Win32, VMS, S, S, VOS, VM/ESA) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, S, VOS, VM/ESA) =item crypt =begin original May not be available if library or source was not provided when building perl. (Win32) =end original perl �Υӥ�ɻ��˥饤�֥�꤫���������󶡤���Ƥ��ʤ��� ���ѤǤ��ʤ����⤷��ޤ��� (Win32) =item dbmclose =begin original Not implemented. (VMS, S, VOS) =end original ��������Ƥ��ޤ��� (VMS, S, VOS) =item dbmopen =begin original Not implemented. (VMS, S, VOS) =end original ��������Ƥ��ޤ��� (VMS, S, VOS) =item dump =begin original Not useful. (S, S) =end original �Ȥ�ƻ�Ϥ���ޤ��� (S, S) =begin original Not supported. (Cygwin, Win32) =end original �б����Ƥ��ޤ��� (Cygwin, Win32) =begin original Invokes VMS debugger. (VMS) =end original VMS �ǥХå���ư���ޤ��� (VMS) =item exec =begin original Not implemented. (S) =end original ��������Ƥ��ޤ��� (S) =begin original Implemented via Spawn. (VM/ESA) =end original Spawn �Ǽ�������Ƥ��ޤ��� (VM/ESA) =begin original Does not automatically flush output handles on some platforms. (SunOS, Solaris, HP-UX) =end original �����Υץ�åȥե�����ǤϽ��ϥϥ�ɥ��ưŪ�˥ե�å��夷�ޤ��� (SunOS, Solaris, HP-UX) =item exit =begin original Emulates UNIX exit() (which considers C to indicate an error) by mapping the C<1> to SS$_ABORT (C<44>). This behavior may be overridden with the pragma C. As with the CRTL's exit() function, C is also mapped to an exit status of SS$_NORMAL (C<1>); this mapping cannot be overridden. Any other argument to exit() is used directly as Perl's exit status. On VMS, unless the future POSIX_EXIT mode is enabled, the exit code should always be a valid VMS exit code and not a generic number. When the POSIX_EXIT mode is enabled, a generic number will be encoded in a method compatible with the C library _POSIX_EXIT macro so that it can be decoded by other programs, particularly ones written in C, like the GNV package. (VMS) =end original C<1> �� SS$_ABORT (C<44>) �˥ޥåԥ󥰤��뤳�Ȥ� UNIX �� (���顼�򼨤������ C ��Ȥ�) exit() �򥨥ߥ�졼�Ȥ��ޤ��� ���ο����񤤤ϥץ饰�� C �Ǿ�񤭤���ޤ��� CRTL �� exit() �ؿ���Ʊ�͡�C �� SS$_NORMAL �ν�λ���ơ����� (C<1>) �˥ޥåԥ󥰤���ޤ�; ���Υޥåԥ󥰤Ͼ�񤭤Ǥ��ޤ��� exit() �ؤΤ���¾�ΰ�����ľ�� Perl �ν�λ���ơ������Ȥ��ƻȤ��ޤ��� VMS �Ǥϡ������ POSIX_EXIT �⡼�ɤ�ͭ���Ǥʤ��¤ꡢ��λ�����ɤ� ���ͭ���� VMS ��λ�����ɤǤ��ꡢ����Ū�ʿ��ͤǤϤʤ��٤��Ǥ��� POSIX_EXIT �⡼�ɤ�ͭ���ʤ顢����Ū�ʿ��ͤ� C �饤�֥��� _POSIX_EXIT �� �ߴ����Τ���᥽�åɤ˥��󥳡��ɤ����Τǡ�����¾�Υץ�����ࡢ�ä� GNV �ѥå������Τ褦�� C �ǽ񤫤�Ƥ���ץ������ǥǥ����ɤǤ��ޤ��� (VMS) =item fcntl =begin original Not implemented. (Win32) Some functions available based on the version of VMS. (VMS) =end original ��������Ƥ��ޤ��� (Win32) �����δؿ��� VMS �ΥС������ˤ�äƤ����Ѳ�ǽ�Ǥ��� (VMS) =item flock =begin original Not implemented (S, VMS, S, VOS). =end original ��������Ƥ��ޤ��� (S, VMS, S, VOS) =begin original Available only on Windows NT (not on Windows 95). (Win32) =end original Windows NT �ǤΤ����Ѳ�ǽ�Ǥ� (Windows 95 �Ǥ�ư��ޤ���)�� (Win32) =item fork =begin original Not implemented. (S, AmigaOS, S, VM/ESA, VMS) =end original ��������Ƥ��ޤ��� (S, AmigaOS, S, VM/ESA, VMS) =begin original Emulated using multiple interpreters. See L. (Win32) =end original ʣ���Υ��󥿥ץ꥿��Ȥäƥ��ߥ�졼�Ȥ���Ƥ��ޤ��� L �򻲾Ȥ��Ƥ��������� (Win32) =begin original Does not automatically flush output handles on some platforms. (SunOS, Solaris, HP-UX) =end original �����Υץ�åȥե�����ǤϽ��ϥϥ�ɥ��ưŪ�˥ե�å��夷�ޤ��� (SunOS, Solaris, HP-UX) =item getlogin =begin original Not implemented. (S, S) =end original ��������Ƥ��ޤ��� (S, S) =item getpgrp =begin original Not implemented. (S, Win32, VMS, S) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S) =item getppid =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item getpriority =begin original Not implemented. (S, Win32, VMS, S, VOS, VM/ESA) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, VOS, VM/ESA) =item getpwnam =begin original Not implemented. (S, Win32) =end original ��������Ƥ��ޤ��� (S, Win32) =begin original Not useful. (S) =end original �Ȥ�ƻ�Ϥ���ޤ��� (S) =item getgrnam =begin original Not implemented. (S, Win32, VMS, S) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S) =item getnetbyname =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item getpwuid =begin original Not implemented. (S, Win32) =end original ��������Ƥ��ޤ��� (S, Win32) =begin original Not useful. (S) =end original �Ȥ�ƻ�Ϥ���ޤ��� (S) =item getgrgid =begin original Not implemented. (S, Win32, VMS, S) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S) =item getnetbyaddr =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item getprotobynumber =begin original Not implemented. (S) =end original ��������Ƥ��ޤ��� (S) =item getservbyport =begin original Not implemented. (S) =end original ��������Ƥ��ޤ��� (S) =item getpwent =begin original Not implemented. (S, Win32, VM/ESA) =end original ��������Ƥ��ޤ��� (S, Win32, VM/ESA) =item getgrent =begin original Not implemented. (S, Win32, VMS, VM/ESA) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, VM/ESA) =item gethostbyname =begin original C does not work everywhere: you may have to use C. (S, S) =end original C �Ϥɤ��Ǥ�ư���櫓�ǤϤ���ޤ���: C ��Ȥ�ɬ�פ����뤫�⤷��ޤ��� (S, S) =item gethostent =begin original Not implemented. (S, Win32) =end original ��������Ƥ��ޤ��� (S, Win32) =item getnetent =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item getprotoent =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item getservent =begin original Not implemented. (Win32, S) =end original ��������Ƥ��ޤ��� (Win32, S) =item sethostent =begin original Not implemented. (S, Win32, S, S) =end original ��������Ƥ��ޤ��� (S, Win32, S, S) =item setnetent =begin original Not implemented. (S, Win32, S, S) =end original ��������Ƥ��ޤ��� (S, Win32, S, S) =item setprotoent =begin original Not implemented. (S, Win32, S, S) =end original ��������Ƥ��ޤ��� (S, Win32, S, S) =item setservent =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item endpwent =begin original Not implemented. (S, MPE/iX, VM/ESA, Win32) =end original ��������Ƥ��ޤ��� (S, MPE/iX, VM/ESA, Win32) =item endgrent =begin original Not implemented. (S, MPE/iX, S, VM/ESA, VMS, Win32) =end original ��������Ƥ��ޤ��� (S, MPE/iX, S, VM/ESA, VMS, Win32) =item endhostent =begin original Not implemented. (S, Win32) =end original ��������Ƥ��ޤ��� (S, Win32) =item endnetent =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item endprotoent =begin original Not implemented. (S, Win32, S) =end original ��������Ƥ��ޤ��� (S, Win32, S) =item endservent =begin original Not implemented. (S, Win32) =end original ��������Ƥ��ޤ��� (S, Win32) =item getsockopt SOCKET,LEVEL,OPTNAME =begin original Not implemented. (S) =end original ��������Ƥ��ޤ��� (S) =item glob =begin original This operator is implemented via the File::Glob extension on most platforms. See L for portability information. =end original ���α黻�ҤϤۤȤ�ɤΥץ�åȥե�����Ǥ� File::Glob �������ƥ󥷥��� ��������Ƥ��ޤ��� �ܿ����ξ���ˤĤ��Ƥ� L �򻲾Ȥ��Ƥ��������� =item gmtime =begin original Same portability caveats as L. =end original L ��Ʊ���ܿ��������꤬����ޤ��� =item ioctl FILEHANDLE,FUNCTION,SCALAR =begin original Not implemented. (VMS) =end original ��������Ƥ��ޤ��� (VMS) =begin original Available only for socket handles, and it does what the ioctlsocket() call in the Winsock API does. (Win32) =end original �����åȥϥ�ɥ���Ф��ƤΤ����Ѳ�ǽ�ǡ�Winsock API �� ioctlsocket() �ƤӽФ��Ǥ��뤳�Ȥ򤷤ޤ��� (Win32) =begin original Available only for socket handles. (S) =end original �����åȥϥ�ɥ���Ф��ƤΤ����Ѳ�ǽ�Ǥ��� (S) =item kill =begin original C is implemented for the sake of taint checking; use with other signals is unimplemented. (S) =end original C �ϱ��������å��Τ���˼�������Ƥ��ޤ�; ¾�Υ����ʥ�Ǥλ��Ѥϼ�������Ƥ��ޤ��� (S) =begin original Not implemented, hence not useful for taint checking. (S) =end original ���������å��ˤ�ͭ�ѤǤϤʤ��Τǡ���������Ƥ��ޤ��� (S) =begin original C doesn't have the semantics of C, i.e. it doesn't send a signal to the identified process like it does on Unix platforms. Instead C terminates the process identified by $pid, and makes it exit immediately with exit status $sig. As in Unix, if $sig is 0 and the specified process exists, it returns true without actually terminating it. (Win32) =end original C �� C ��ư��Ϥ���ޤ���; �Ĥޤꡢ Unix �ץ�åȥե�����ǹԤ���褦�˼��̤��줿�ץ������إ����ʥ�� ����ޤ��� ����� C �� $pid �Ǽ��̤����ץ�������λ������ ��λ������ $sig ��ľ���˽�λ�����ޤ��� Unix �ǤΤ褦�ˡ�$sig �� 0 �ǻ��ꤵ�줿�ץ�������¸�ߤ���ʤ顢�ºݤˤ� ��λ�������˿����֤��ޤ��� (Win32) =begin original C will terminate the process specified by $pid and recursively all child processes owned by it. This is different from the Unix semantics, where the signal will be delivered to all processes in the same process group as the process specified by $pid. (Win32) =end original C �� $pid �ǻ��ꤵ�줿�ץ������ȡ����Υץ������� ��ͭ���Ƥ������Ƥλҥץ�������Ƶ�Ū�˽�λ�����ޤ��� ����ϡ�$pid �ǻ��ꤵ�줿�ץ�������Ʊ���ץ��������롼�פ����Ƥ� �ץ������˥����ʥ���������롢�Ȥ��� Unix �Ǥ�ư��Ȱۤʤ�ޤ��� (Win32) =begin original Is not supported for process identification number of 0 or negative numbers. (VMS) =end original �ץ����������ֹ� 0 ��������б����Ƥ��ޤ��� (VMS) =item link =begin original Not implemented. (S, MPE/iX, S) =end original ��������Ƥ��ޤ��� (S, MPE/iX, S) =begin original Link count not updated because hard links are not quite that hard (They are sort of half-way between hard and soft links). (AmigaOS) =end original �ϡ��ɥ�󥯤ϴ����˥ϡ��ɤǤϤʤ��Τǡ���󥯥�����ȤϹ�������ޤ��� (����ϥϡ��ɥ�󥯤ȥ��եȥ�󥯤���֤Τ褦�ʤ�ΤǤ�)�� (AmigaOS) =begin original Hard links are implemented on Win32 under NTFS only. They are natively supported on Windows 2000 and later. On Windows NT they are implemented using the Windows POSIX subsystem support and the Perl process will need Administrator or Backup Operator privileges to create hard links. =end original �ϡ��ɥ�󥯤� NTFS �� Win32 �ˤΤ߼�������Ƥ��ޤ��� ����� Windows 2000 �ʹߤǥͥ��ƥ��֤��б����Ƥ��ޤ��� Windows NT �Ǥ� Windows POSIX ���֥����ƥॵ�ݡ��Ȥ�Ȥä� ��������Ƥ��ơ�Perl �ץ������ϥϡ��ɥ�󥯤���ˤ� Administrator �ޤ��� Backup Operator ���¤�ɬ�פǤ��� =begin original Available on 64 bit OpenVMS 8.2 and later. (VMS) =end original 64 �ӥå� OpenVMS 8.2 �ʹߤ����Ѳ�ǽ�Ǥ��� (VMS) =item localtime =begin original Because Perl currently relies on the native standard C localtime() function, it is only safe to use times between 0 and (2**31)-1. Times outside this range may result in unexpected behavior depending on your operating system's implementation of localtime(). =end original Perl �ϸ��ߤΤȤ����ͥ��ƥ��֤�ɸ�� C localtime() �ؿ��˰�¸���Ƥ���Τǡ� 0 �� (2**31)-1 �δ֤ǤΤ� times ��Ȥ��Τ������Ǥ��� �����ϰϳ��� times �ϥ��ڥ졼�ƥ��󥰥����ƥ�� localtime() �μ����˰�¸���� ���곰�ο����񤤤ˤʤ뤳�Ȥ�����ޤ��� =item lstat =begin original Not implemented. (S) =end original ��������Ƥ��ޤ��� (S) =begin original Return values (especially for device and inode) may be bogus. (Win32) =end original �֤��� (�ä˥ǥХ����� i �Ρ���) �ϵ�ʪ���⤷��ޤ��� (Win32) =item msgctl =item msgget =item msgsnd =item msgrcv =begin original Not implemented. (S, Win32, VMS, S, S, VOS) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, S, VOS) =item open =begin original The C<|> variants are supported only if ToolServer is installed. (S) =end original C<|> ��Ϣ�� ToolServer �����󥹥ȡ��뤵��Ƥ���Ȥ��ˤΤ��б����ޤ��� (S) =begin original open to C<|-> and C<-|> are unsupported. (S, Win32, S) =end original C<|-> �� C<-|> �ؤΥ����ץ���б����Ƥ��ޤ��� (S, Win32, S) =begin original Opening a process does not automatically flush output handles on some platforms. (SunOS, Solaris, HP-UX) =end original �ץ������򥪡��ץ󤷤��Ȥ��˰����Υץ�åȥե�����ǤϽ��ϥϥ�ɥ��ưŪ�� �ե�å��夷�ޤ��� (SunOS, Solaris, HP-UX) =item pipe =begin original Very limited functionality. (MiNT) =end original �ȤƤ���ꤷ����ǽ��������ޤ��� (MiNT) =item readlink =begin original Not implemented. (Win32, VMS, S) =end original ��������Ƥ��ޤ��� (Win32, VMS, S) =item rename =begin original Can't move directories between directories on different logical volumes. (Win32) =end original �ۤʤä������ܥ�塼��Υǥ��쥯�ȥ�δ֤Ǥϥǥ��쥯�ȥ�ϰ�ư�Ǥ��ޤ��� (Win32) =item select =begin original Only implemented on sockets. (Win32, VMS) =end original �����åȤ��Ф��ƤΤ߼�������Ƥ��ޤ��� (Win32, VMS) =begin original Only reliable on sockets. (S) =end original �����åȤ��Ф��ƤΤ߿���Ǥ��ޤ��� (S) =begin original Note that the C �����ϰ���Ū�˰ܿ��������뤳�Ȥ����դ��Ƥ��������� =item semctl =item semget =item semop =begin original Not implemented. (S, Win32, VMS, S, VOS) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, VOS) =item setgrent =begin original Not implemented. (S, MPE/iX, VMS, Win32, S, VOS) =end original ��������Ƥ��ޤ��� (S, MPE/iX, VMS, Win32, S, VOS) =item setpgrp =begin original Not implemented. (S, Win32, VMS, S, VOS) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, VOS) =item setpriority =begin original Not implemented. (S, Win32, VMS, S, VOS) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, VOS) =item setpwent =begin original Not implemented. (S, MPE/iX, Win32, S, VOS) =end original ��������Ƥ��ޤ��� (S, MPE/iX, Win32, S, VOS) =item setsockopt =begin original Not implemented. (S) =end original ��������Ƥ��ޤ��� (S) =item shmctl =item shmget =item shmread =item shmwrite =begin original Not implemented. (S, Win32, VMS, S, VOS) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, VOS) =item sockatmark =begin original A relatively recent addition to socket functions, may not be implemented even in UNIX platforms. =end original ���Ū�Ƕ���ɲä��줿�����åȴؿ��ǡ�UNIX �ץ�åȥե�����Ǥ��äƤ� ��������Ƥ��ʤ����⤷��ޤ��� =item socketpair =begin original Not implemented. (S, VOS, VM/ESA) =end original ��������Ƥ��ޤ��� (S, VOS, VM/ESA) =begin original Available on 64 bit OpenVMS 8.2 and later. (VMS) =end original 64 �ӥå� OpenVMS 8.2 �ʹߤ����Ѳ�ǽ�Ǥ��� (VMS) =item stat =begin original Platforms that do not have rdev, blksize, or blocks will return these as '', so numeric comparison or manipulation of these fields may cause 'not numeric' warnings. =end original rdev, blksize, blocks ���ʤ��ץ�åȥե�����ǤϤ����� '' ���֤��Τǡ� �����Υե�����ɤο��ͤǤ���Ӥ����� 'not numeric' �ٹ�� �����������ޤ��� =begin original mtime and atime are the same thing, and ctime is creation time instead of inode change time. (S). =end original mtime �� atime ��Ʊ����Τǡ�ctime �� i �Ρ����ѹ�����ǤϤʤ���������Ǥ��� (S) =begin original ctime not supported on UFS (S). =end original ctime �� UFS �Ǥ��б����Ƥ��ޤ��� (S) =begin original ctime is creation time instead of inode change time (Win32). =end original ctime �� i �Ρ����ѹ�����ǤϤʤ���������Ǥ��� (Win32) =begin original device and inode are not meaningful. (Win32) =end original �ǥХ����� i �Ρ��ɤ�̵��̣�Ǥ��� (Win32) =begin original device and inode are not necessarily reliable. (VMS) =end original �ǥХ����� i �Ρ��ɤϿ���Ǥ���ɬ�פ�����ޤ��� (VMS) =begin original mtime, atime and ctime all return the last modification time. Device and inode are not necessarily reliable. (S) =end original mtime, atime, ctime �����ƺǽ�����������֤��ޤ��� �ǥХ����� i �Ρ��ɤϿ��ꤹ��ɬ�פϤ���ޤ��� (S) =begin original dev, rdev, blksize, and blocks are not available. inode is not meaningful and will differ between stat calls on the same file. (os2) =end original dev, rdev, blksize, blocks �����ѤǤ��ޤ��� inode ��̵��̣�ǡ�Ʊ���ե������ stat �ƤӽФ��δ֤Ǥ�ۤʤ�ޤ��� (os2) =begin original some versions of cygwin when doing a stat("foo") and if not finding it may then attempt to stat("foo.exe") (Cygwin) =end original cygwin �ΰ����ΥС������Ǥϡ�stat("foo") ��¹Ԥ��ơ��⤷ ���դ���ʤ���� stat("foo.exe") ��¹Ԥ��褦�Ȥ��ޤ��� (Cygwin) =begin original On Win32 stat() needs to open the file to determine the link count and update attributes that may have been changed through hard links. Setting ${^WIN32_SLOPPY_STAT} to a true value speeds up stat() by not performing this operation. (Win32) =end original Win32 �Ǥ� stat() �ϡ���󥯥�����Ȥȡ��ϡ��ɥ�󥯤��̤��� �ѹ�����뤫�⤷��ʤ�°���ι����ˤϥե�����򳫤�ɬ�פ�����ޤ��� ${^WIN32_SLOPPY_STAT} �򿿤��ͤ����ꤹ�뤳�Ȥǡ��������򤷤ʤ����Ȥ� stat() ���®�����ޤ��� (Win32) =item symlink =begin original Not implemented. (Win32, S) =end original ��������Ƥ��ޤ��� (Win32, S) =begin original Implemented on 64 bit VMS 8.3. VMS requires the symbolic link to be in Unix syntax if it is intended to resolve to a valid path. =end original 64 �ӥå� VMS 8.3 �Ǽ�������Ƥ��ޤ��� VMS �ϡ�ͭ���ʥѥ����褹�뤳�Ȥ���Ū�Ȥ��Ƥ���ʤ顢����ܥ�å���󥯤� Unix ��ʸˡ�Ǥ��뤳�Ȥ�ɬ�פǤ��� =item syscall =begin original Not implemented. (S, Win32, VMS, S, VOS, VM/ESA) =end original ��������Ƥ��ޤ��� (S, Win32, VMS, S, VOS, VM/ESA) =item sysopen =begin original The traditional "0", "1", and "2" MODEs are implemented with different numeric values on some systems. The flags exported by C (O_RDONLY, O_WRONLY, O_RDWR) should work everywhere though. (S, OS/390, VM/ESA) =end original ����Ū��l "0", "1", 2" �� MODE �ϰ����Υ����ƥ�Ǥϰۤʤ���ͤ� ��������Ƥ��ޤ��� ��������C �ǥ������ݡ��Ȥ����ե饰 (O_RDONLY, O_WRONLY, O_RDWR) �� �ɤ��Ǥ�ư���Ϥ��Ǥ��� (S, OS/390, VM/ESA) =item system =begin original Only implemented if ToolServer is installed. (S) =end original ToolServer �����󥹥ȡ��뤵��Ƥ���Ȥ��ˤΤ߼�������Ƥ��ޤ��� (S) =begin original As an optimization, may not call the command shell specified in C<$ENV{PERL5SHELL}>. C spawns an external process and immediately returns its process designator, without waiting for it to terminate. Return value may be used subsequently in C or C. Failure to spawn() a subprocess is indicated by setting $? to "255 << 8". C<$?> is set in a way compatible with Unix (i.e. the exitstatus of the subprocess is obtained by "$? >> 8", as described in the documentation). (Win32) =end original ��Ŭ���Ȥ��ơ�C<$ENV{PERL5SHELL}> �ǻ��ꤵ�줿���ޥ�ɥ������ �ƤӽФ��ʤ����⤷��ޤ��� C �ϳ����ץ�������ư���ơ����ν�λ���Ԥ����� ľ���ˤ��Υץ���������Ҥ��֤��ޤ��� �֤��ͤϰ���³�� C �� C �ǻȤ��ޤ��� ���֥ץ������� spawn() �μ��Ԥϡ�$? �� "255 << 8" �����ꤹ�뤳�Ȥ� ������ޤ��� C<$?> �� Unix �ȸߴ����Τ�����ˡ (�Ĥޤꡢ���֥ץ������ν�λ���ơ������� ʸ��˵��Ҥ���Ƥ����̤�� "$? >> 8" ��������) �����ꤵ��ޤ��� (Win32) =begin original There is no shell to process metacharacters, and the native standard is to pass a command line terminated by "\n" "\r" or "\0" to the spawned program. Redirection such as C<< > foo >> is performed (if at all) by the run time library of the spawned program. C I will call the Unix emulation library's C emulation, which attempts to provide emulation of the stdin, stdout, stderr in force in the parent, providing the child program uses a compatible version of the emulation library. I will call the native command line direct and no such emulation of a child Unix program will exists. Mileage B vary. (S) =end original �᥿ʸ����������륷����Ϥʤ����ͥ��ƥ��֤�ɸ��Ǥ� "\n", "\r", "\0" �ǽ�ü���줿���ޥ�ɥ饤��� spawn �����ץ������� �Ϥ��ޤ��� C<< > foo >> �Τ褦�ʥ�����쥯�Ȥ� spawn �����ץ������� ��󥿥���饤�֥��ˤ�äƼ¹Ԥ���ޤ��� C I �� Unix ���ߥ�졼�����饤�֥��� C ���ߥ�졼������ƤӽФ����ҥץ�����ब���ߥ�졼�����饤�֥��� �ߴ��Ǥ�ȤäƤ���ʤ顢�Ƥ� stdin, stdout, stderr �򥨥ߥ�졼������ �󶡤��褦�Ȥ��ޤ��� I �ϥͥ��ƥ��֤ʥ��ޥ�ɥ饤���ľ�ܸƤӽФ����� Unix �ץ������� ���ߥ�졼������¸�ߤ��ޤ��� ����Ͼ����ˤ�ä� B<�ۤʤ�ޤ�>�� (S) =begin original Far from being POSIX compliant. Because there may be no underlying /bin/sh tries to work around the problem by forking and execing the first token in its argument string. Handles basic redirection ("<" or ">") on its own behalf. (MiNT) =end original POSIX ��򤫤�Ϥۤɱ󤤤Ǥ��� ���äȤʤ� /bin/sh ���ʤ����⤷��ʤ��Τǡ�����ʸ����κǽ�Υȡ������ fork ���Ƽ¹Ԥ��뤳�Ȥ��������򤷤褦�Ȥ��ޤ��� ����Ū�ʥ�����쥯�� ("<" �� ">") �򼫿Ȥ����äư����ޤ��� (MiNT) =begin original Does not automatically flush output handles on some platforms. (SunOS, Solaris, HP-UX) =end original �����Υץ�åȥե�����ǤϽ��ϥϥ�ɥ��ưŪ�˥ե�å��夷�ޤ��� (SunOS, Solaris, HP-UX) =begin original The return value is POSIX-like (shifted up by 8 bits), which only allows room for a made-up value derived from the severity bits of the native 32-bit condition code (unless overridden by C). If the native condition code is one that has a POSIX value encoded, the POSIX value will be decoded to extract the expected exit value. For more details see L. (VMS) =end original �֤��ͤ� POSIX �� (8 �ӥåȥ��ե�) �ǡ�(C �� ��񤭤���ʤ��¤�)�ͥ��ƥ��֤� 32 �ӥåȾ�拾���ɤν����٥ӥåȤ��� ���夲��줿�ͤΤ���ξ�����������ޤ��� �ͥ��ƥ��֤ʾ�拾���ɤ� POSIX �ͤ򥨥󥳡��ɤ�����Τʤ顢 POSIX �ͤ����ꤵ��뽪λ�����ɤ�Ÿ�����뤿��˥ǥ����ɤ���ޤ��� ����ʤ�ܺ٤ˤĤ��Ƥ� L �򻲾Ȥ��Ƥ��������� (VMS) =item times =begin original Only the first entry returned is nonzero. (S) =end original �֤��줿�ǽ�Υ���ȥ꤬�� 0 �ΤȤ��ΤߤǤ��� (S) =begin original "cumulative" times will be bogus. On anything other than Windows NT or Windows 2000, "system" time will be bogus, and "user" time is actually the time returned by the clock() function in the C runtime library. (Win32) =end original �����ѡ׻��֤ϵ��꤫�⤷��ޤ��� Windows NT �� Windows 2000 �ʳ��Ǥϡ��֥����ƥ�׻��֤ϵ��꤫�⤷�줺�� �֥桼���׻��֤ϼºݤˤ� C ��󥿥���饤�֥��� clock() �ؿ����� �������줿����Ǥ��� (Win32) =begin original Not useful. (S) =end original �Ȥ�ƻ�Ϥ���ޤ��� (S) =item truncate =begin original Not implemented. (Older versions of VMS) =end original ��������Ƥ��ޤ��� (Older versions of VMS) =begin original Truncation to same-or-shorter lengths only. (VOS) =end original Ʊ�������û��Ĺ���ؤ��ڤ�ͤ�ΤߤǤ��� (VOS) =begin original If a FILEHANDLE is supplied, it must be writable and opened in append mode (i.e., use C<<< open(FH, '>>filename') >>> or C. If a filename is supplied, it should not be held open elsewhere. (Win32) =end original FILEHANDLE �����ꤵ���ȡ�����Ͻ񤭹��߲�ǽ�ǡ��ɵ��⡼�� (�Ĥޤ� C<<< open(FH, '>>filename') >>> �ޤ��� C ��ȤäƤ���)�Ǥʤ���Фʤ�ޤ��� �ե�����̾�����ꤵ���ȡ�¾�dz����Ƥ��ƤϤ����ޤ��� (Win32) =item umask =begin original Returns undef where unavailable, as of version 5.005. =end original �С������ 5.005 ���顢�����Բ�ǽ�ʾ��� undef ���֤��ޤ��� =begin original C works but the correct permissions are set only when the file is finally closed. (AmigaOS) =end original C ��ư��ޤ��������������¤ϥե����뤬�ǽ�Ū���Ĥ���줿�Ȥ��ˤΤ� ���ꤵ��ޤ��� (AmigaOS) =item utime =begin original Only the modification time is updated. (S, S, VMS, S) =end original �������郎�������줿�Ȥ��ΤߤǤ��� (S, S, VMS, S) =begin original May not behave as expected. Behavior depends on the C runtime library's implementation of utime(), and the filesystem being used. The FAT filesystem typically does not support an "access time" field, and it may limit timestamps to a granularity of two seconds. (Win32) =end original ���ꤷ���̤��ư��ʤ����⤷��ޤ��� �����񤤤� C ��󥿥���饤�֥��� utime() �μ����ȡ��Ȥ��� �ե����륷���ƥ�˰�¸���ޤ��� FAT �ե����륷���ƥ��ŵ��Ū�ˤϡ֥�����������ץե�����ɤ� �б����Ƥ��餺�������ॹ����פ����٤� 2 �ä����¤���Ƥ��뤫�� ����ޤ��� (Win32) =item wait =item waitpid =begin original Not implemented. (S) =end original ��������Ƥ��ޤ��� (S) =begin original Can only be applied to process handles returned for processes spawned using C or pseudo processes created with C. (Win32) =end original C ��Ȥäƺ������줿�ץ���������C �Ǻ������줿 �����ץ��������֤��줿�ץ������ϥ�ɥ���Ф��ƤΤ�Ŭ�ѤǤ��ޤ��� (Win32) =begin original Not useful. (S) =end original �Ȥ�ƻ�Ϥ���ޤ��� (S) =back =head1 Supported Platforms (�б����Ƥ���ץ�åȥե�����) =begin original As of July 2002 (the Perl release 5.8.0), the following platforms are able to build Perl from the standard source code distribution available at http://www.cpan.org/src/index.html =end original 2002 ǯ 7 �� (Perl ��꡼�� 5.8.0) ���ߡ��ʲ��Υץ�åȥե����ब http://www.cpan.org/src/index.html �������Ѳ�ǽ��ɸ�ॽ�������������ۤ��� �ӥ�ɲ�ǽ�Ǥ�: AIX BeOS BSD/OS (BSDi) Cygwin DG/UX DOS DJGPP 1) DYNIX/ptx EPOC R5 FreeBSD HI-UXMPP (Hitachi) (5.8.0 worked but we didn't know it) HP-UX IRIX Linux Mac OS Classic Mac OS X (Darwin) MPE/iX NetBSD NetWare NonStop-UX ReliantUNIX (formerly SINIX) OpenBSD OpenVMS (formerly VMS) Open UNIX (Unixware) (since Perl 5.8.1/5.9.0) OS/2 OS/400 (using the PASE) (since Perl 5.8.1/5.9.0) PowerUX POSIX-BC (formerly BS2000) QNX Solaris SunOS 4 SUPER-UX (NEC) Tru64 UNIX (formerly DEC OSF/1, Digital UNIX) UNICOS UNICOS/mk UTS VOS Win95/98/ME/2K/XP 2) WinCE z/OS (formerly OS/390) VM/ESA 1) in DOS mode either the DOS or OS/2 ports can be used 2) compilers: Borland, MinGW (GCC), VC6 =begin original The following platforms worked with the previous releases (5.6 and 5.7), but we did not manage either to fix or to test these in time for the 5.8.0 release. There is a very good chance that many of these will work fine with the 5.8.0. =end original �ʲ��Υץ�åȥե�����ϰ����Υ�꡼�� (5.6 �� 5.7) ��ư��Ƥ��ޤ������� 5.8.0 ��꡼���ΤȤ��˽�����ƥ��Ȥ��Ǥ��ޤ���Ǥ����� ������¿���� 5.8.0 �Ǥ��ޤ�ư����ǽ�������ʤꤢ��ޤ��� BSD/OS DomainOS Hurd LynxOS MachTen PowerMAX SCO SV SVR4 Unixware Windows 3.1 =begin original Known to be broken for 5.8.0 (but 5.6.1 and 5.7.2 can be used): =end original 5.8.0 �Dz���Ƥ��뤳�Ȥ��Τ��Ƥ��ޤ� (������ 5.6.1 �� 5.7.2 �ϻȤ��ޤ�): AmigaOS =begin original The following platforms have been known to build Perl from source in the past (5.005_03 and earlier), but we haven't been able to verify their status for the current release, either because the hardware/software platforms are rare or because we don't have an active champion on these platforms--or both. They used to work, though, so go ahead and try compiling them, and let perlbug@perl.org of any trouble. =end original �ʲ��Υץ�åȥե�����ϲ�� (5.005_03 ����) �˥��������� Perl �� �ӥ�ɤ������Ȥ��Τ��Ƥ��ޤ��������ߤΥ�꡼�����Ф�������� ��ǧ�Ǥ��ޤ���; �ϡ��ɥ�����/���եȥ������ץ�åȥե����ब�쥢�ʤ�Τ��� �����Υץ�åȥե�������Ф��륢���ƥ��֤ʿ�ʼԤ����ʤ����� ���뤤�Ϥ���ξ������ͳ�Ǥ��� ������������ư���Ƥ����Τǡ����ҥ���ѥ��뤷�Ƥߤơ� perlbug@perl.org �� ���������Τ餻�Ƥ��������� 3b1 A/UX ConvexOS CX/UX DC/OSx DDE SMES DOS EMX Dynix EP/IX ESIX FPS GENIX Greenhills ISC MachTen 68k MiNT MPC NEWS-OS NextSTEP OpenSTEP Opus Plan 9 RISC/os SCO ODT/OSR Stellar SVR2 TI1500 TitanOS Ultrix Unisys Dynix =begin original The following platforms have their own source code distributions and binaries available via http://www.cpan.org/ports/ =end original �ʲ��Υץ�åȥե������ http://www.cpan.org/ports/ ��ͳ���ȼ��� ���������������ۤȥХ��ʥ꤬���Ѳ�ǽ�Ǥ�: Perl release OS/400 (ILE) 5.005_02 Tandem Guardian 5.004 =begin original The following platforms have only binaries available via http://www.cpan.org/ports/index.html : =end original �ʲ��Υץ�åȥե������ http://www.cpan.org/ports/index.html ��ͳ�� �Х��ʥ�Τߤ����Ѳ�ǽ�Ǥ�: Perl release Acorn RISCOS 5.005_02 AOS 5.002 LynxOS 5.004_02 =begin original Although we do suggest that you always build your own Perl from the source code, both for maximal configurability and for security, in case you are in a hurry you can check http://www.cpan.org/ports/index.html for binary distributions. =end original ���������䤿���ϡ�����¤������ǽ���ȥ������ƥ���ξ���Τ���ˡ� ��ˤ��ʤ����Ȥ� Perl �򥽡�������ӥ�ɤ��뤳�Ȥ���Ƥ��Ƥ��ޤ�; �ޤ��Ǥ�����ˤ� http://www.cpan.org/ports/index.html �ˤ��� �Х��ʥ����ۤ�����å����Ƥ��������� =head1 SEE ALSO L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, and L. =head1 AUTHORS / CONTRIBUTORS Abigail , Charles Bailey , Graham Barr , Tom Christiansen , Nicholas Clark , Thomas Dorner , Andy Dougherty , Dominic Dunlop , Neale Ferguson , David J. Fiander , Paul Green , M.J.T. Guy , Jarkko Hietaniemi , Luther Huffman , Nick Ing-Simmons , Andreas J. KEnig , Markus Laker , Andrew M. Langmead , Larry Moore , Paul Moore , Chris Nandor , Matthias Neeracher , Philip Newton , Gary Ng <71564.1743@CompuServe.COM>, Tom Phoenix , AndrE Pirard , Peter Prymmer , Hugo van der Sanden , Gurusamy Sarathy , Paul J. Schinder , Michael G Schwern , Dan Sugalski , Nathan Torkington . John Malmberg =begin meta Translate: SHIRAKATA Kentaro Status: completed =end meta