]>
Commit | Line | Data |
---|---|---|
8b982d63 JR |
1 | diff -urN perl5.005_03.old/lib/File/Spec/Functions.pm perl5.005_03/lib/File/Spec/Functions.pm |
2 | --- perl5.005_03.old/lib/File/Spec/Functions.pm Thu Jan 1 01:00:00 1970 | |
3 | +++ perl5.005_03/lib/File/Spec/Functions.pm Sun Dec 6 05:22:30 1998 | |
4 | @@ -0,0 +1,37 @@ | |
5 | +package File::Spec::Functions; | |
6 | + | |
7 | +use File::Spec; | |
8 | +use strict; | |
9 | + | |
10 | +use vars qw(@ISA @EXPORT); | |
11 | + | |
12 | +require Exporter; | |
13 | + | |
14 | +@ISA = qw(Exporter); | |
15 | + | |
16 | +@EXPORT = qw( | |
17 | + canonpath | |
18 | + catdir | |
19 | + catfile | |
20 | + curdir | |
21 | + rootdir | |
22 | + updir | |
23 | + no_upwards | |
24 | + file_name_is_absolute | |
25 | + path | |
26 | + nativename | |
27 | +); | |
28 | + | |
29 | +sub canonpath { File::Spec->canonpath(@_); } | |
30 | +sub catdir { File::Spec->catdir(@_); } | |
31 | +sub catfile { File::Spec->catfile(@_); } | |
32 | +sub curdir { File::Spec->curdir(@_); } | |
33 | +sub rootdir { File::Spec->rootdir(@_); } | |
34 | +sub updir { File::Spec->updir(@_); } | |
35 | +sub no_upwards { File::Spec->no_upwards(@_); } | |
36 | +sub file_name_is_absolute { File::Spec->file_name_is_absolute(@_); } | |
37 | +sub path { File::Spec->path(@_); } | |
38 | +sub nativename { File::Spec->nativename(@_); } | |
39 | + | |
40 | +1; | |
41 | + | |
42 | diff -urN perl5.005_03.old/lib/File/Spec/Mac.pm perl5.005_03/lib/File/Spec/Mac.pm | |
43 | --- perl5.005_03.old/lib/File/Spec/Mac.pm Thu Jan 7 05:41:53 1999 | |
44 | +++ perl5.005_03/lib/File/Spec/Mac.pm Sun Feb 22 16:31:58 1998 | |
45 | @@ -52,7 +52,7 @@ | |
46 | File::Spec->catdir(split(":",$path)) eq $path | |
47 | ||
48 | But because of the nature of Macintosh paths, some additional | |
49 | -possibilities are allowed to make using this routine give reasonable results | |
50 | +possibilities are allowed to make using this routine give resonable results | |
51 | for some common situations. Here are the rules that are used. Each | |
52 | argument has its trailing ":" removed. Each argument, except the first, | |
53 | has its leading ":" removed. They are then joined together by a ":". | |
54 | @@ -78,7 +78,7 @@ | |
55 | File::Spec->catfile("LWP","Protocol","http.pm") | |
56 | ||
57 | be relative or absolute? There's no way of telling except by checking for the | |
58 | -existence of LWP: or :LWP, and even there he may mean a dismounted volume or | |
59 | +existance of LWP: or :LWP, and even there he may mean a dismounted volume or | |
60 | a relative path in a different directory (like in @INC). So those checks | |
61 | aren't done here. This routine will treat this as absolute. | |
62 | ||
63 | diff -urN perl5.005_03.old/lib/File/Spec.pm perl5.005_03/lib/File/Spec.pm | |
64 | --- perl5.005_03.old/lib/File/Spec.pm Thu Jan 7 05:41:53 1999 | |
65 | +++ perl5.005_03/lib/File/Spec.pm Sun Dec 6 05:48:23 1998 | |
66 | @@ -14,7 +14,7 @@ | |
67 | use strict; | |
68 | use vars qw(@ISA $VERSION $Verbose); | |
69 | ||
70 | -$VERSION = '0.6'; | |
71 | +$VERSION = '0.7'; | |
72 | ||
73 | $Verbose = 0; | |
74 | ||
75 | @@ -52,11 +52,15 @@ | |
76 | ||
77 | =head1 SYNOPSIS | |
78 | ||
79 | -C<use File::Spec;> | |
80 | + use File::Spec; | |
81 | ||
82 | -C<$x=File::Spec-E<gt>catfile('a','b','c');> | |
83 | + $x=File::Spec->catfile('a', 'b', 'c'); | |
84 | ||
85 | -which returns 'a/b/c' under Unix. | |
86 | +which returns 'a/b/c' under Unix. Or: | |
87 | + | |
88 | + use File::Spec::Functions; | |
89 | + | |
90 | + $x = catfile('a', 'b', 'c'); | |
91 | ||
92 | =head1 DESCRIPTION | |
93 | ||
94 | @@ -78,8 +82,8 @@ | |
95 | File::Spec::VMS | |
96 | ||
97 | The module appropriate for the current OS is automatically loaded by | |
98 | -File::Spec. Since some modules (like VMS) make use of OS specific | |
99 | -facilities, it may not be possible to load all modules under all operating | |
100 | +File::Spec. Since some modules (like VMS) make use of facilities only under | |
101 | +that OS, it may not be possible to load all modules under all operating | |
102 | systems. | |
103 | ||
104 | Since File::Spec is object oriented, subroutines should not called directly, | |
105 | @@ -91,9 +95,17 @@ | |
106 | ||
107 | File::Spec->catfile('a','b'); | |
108 | ||
109 | -For a reference of available functions, please consult L<File::Spec::Unix>, | |
110 | -which contains the entire set, and inherited by the modules for other | |
111 | -platforms. For further information, please see L<File::Spec::Mac>, | |
112 | +Alternatively, File::Spec::Functions can be used instead, which exports | |
113 | +functions for all of the class methods provided by File::Spec, including | |
114 | +catfile, so you may say: | |
115 | + | |
116 | + use File::Spec::Functions; | |
117 | + | |
118 | + catfile('a','b'); | |
119 | + | |
120 | +For a reference of available functions, pleaes consult L<File::Spec::Unix>, | |
121 | +which contains the entire set, and which is inherited by the modules for | |
122 | +other platforms. For further information, please see L<File::Spec::Mac>, | |
123 | L<File::Spec::OS2>, L<File::Spec::Win32>, or L<File::Spec::VMS>. | |
124 | ||
125 | =head1 SEE ALSO |