David Green wrote:
> Maybe setting $*CWD just calls chdir() under the hood? Same implementation,
> brand new shiny Perl-style interface!
I don't think that's a good idea. Suppose you have code like this:
$*CWD = '/some/absolute/path';
$*CWD = '../relative/path';
my $cwd = $*CWD;
Assumin
I don't think python is the only one with that problem, try saving a file with
non utf8 chars in subversion and see what happens.
We should be liberal in what we accept and strict in what we send as we really
don't know the filesystem will return to us. I guess a file read from the
filesystem coul
On Tue, Aug 18, 2009 at 01:10:58PM +0200, Jan Ingvoldstad wrote:
> On Tue, Aug 18, 2009 at 12:54 PM, Troels Liebe Bentsen
> wrote:
> > Besides that, a simple check on Unix for what the locale is set to might
> > also be
> > nice, so we don't write UTF8 files on a filesystem where the rest for th
On Tue, Aug 18, 2009 at 6:59 AM, Carlin Bingham wrote:
> 2009/8/18 Timothy S. Nelson :
>> On Tue, 18 Aug 2009, Mark J. Reed wrote:
>>
>> It's not in the revised spec, but I think that, even though we've
>> revived chdir, we should still have it so that changing $*CWD will do a
>> chdir under
On Tue, Aug 18, 2009 at 13:10, Jan Ingvoldstad wrote:
> On Tue, Aug 18, 2009 at 12:54 PM, Troels Liebe Bentsen
> wrote:
>
>> My idea with portable by default was only portability for modern Unix and
>> modern Windows. So DOS and VMS limitations would not apply. The problem of
>> enforcing truly "p
On Tue, Aug 18, 2009 at 12:54 PM, Troels Liebe Bentsen wrote:
> My idea with portable by default was only portability for modern Unix and
> modern Windows. So DOS and VMS limitations would not apply. The problem of
> enforcing truly "portable" filenames is that the files names get too
> restrictiv
2009/8/18 Timothy S. Nelson :
> On Tue, 18 Aug 2009, Mark J. Reed wrote:
>
> It's not in the revised spec, but I think that, even though we've
> revived chdir, we should still have it so that changing $*CWD will do a
> chdir under the hood.
>
While in the spirit of TIMTOWTDI, having a "magic
>> Perl 5 runs on (at least) VMS and VOS too. So, if Perl 6 is to adopt a policy
>> of enforced portable filenames by default, it should (at least) also exclude
>> - as the first character, and forbid more than one . in a filename.
>
> And, as I mentioned in an earlier post during the discussion, t
On Tue, 18 Aug 2009, Mark J. Reed wrote:
On Tue, Aug 18, 2009 at 11:04 AM, David Green wrote:
On 2009-Aug-18, at 2:29 am, Carlin Bingham wrote:
chdir provides functionality that would be quite convoluted to mimic
through manually setting $*CWD, such as changing to a relative
directory.
Mayb
> On Tue, Aug 18, 2009 at 11:04 AM, David Green wrote:
>> On 2009-Aug-18, at 2:29 am, Carlin Bingham wrote:
>>>
>>> chdir provides functionality that would be quite convoluted to mimic
>>> through manually setting $*CWD, such as changing to a relative
>>> directory.
>>
>> Maybe setting $*CWD just c
On Tue, 18 Aug 2009, David Green wrote:
On 2009-Aug-18, at 2:29 am, Carlin Bingham wrote:
chdir provides functionality that would be quite convoluted to mimic
through manually setting $*CWD, such as changing to a relative
directory.
Maybe setting $*CWD just calls chdir() under the hood? Same
On Tue, Aug 18, 2009 at 11:04 AM, David Green wrote:
> On 2009-Aug-18, at 2:29 am, Carlin Bingham wrote:
>>
>> chdir provides functionality that would be quite convoluted to mimic
>> through manually setting $*CWD, such as changing to a relative
>> directory.
>
> Maybe setting $*CWD just calls chdi
On Tue, Aug 18, 2009 at 10:58 AM, Nicholas Clark wrote:
> Oh gosh yes. I forgot. AUX.TXT
> And all the the other CP/M device file names, with our without extensions...
>
>
> [And of course, IIRC, DOS filenames can't be more than 64 characters. Which
> means that your code thinks that it knows what
On 2009-Aug-18, at 2:29 am, Carlin Bingham wrote:
chdir provides functionality that would be quite convoluted to mimic
through manually setting $*CWD, such as changing to a relative
directory.
Maybe setting $*CWD just calls chdir() under the hood? Same
implementation, brand new shiny Perl-st
On Tue, Aug 18, 2009 at 10:36:45AM +0200, Jan Ingvoldstad wrote:
> On Tue, Aug 18, 2009 at 10:01 AM, Nicholas Clark wrote:
> > On Tue, Aug 18, 2009 at 09:24:08AM +0200, pugs-comm...@feather.perl6.nl
> > wrote:
> >
> >> +=head3 Default constraints
> >> +
> >> +The default p{} only allows "/" as sep
On Tue, Aug 18, 2009 at 10:01 AM, Nicholas Clark wrote:
> On Tue, Aug 18, 2009 at 09:24:08AM +0200, pugs-comm...@feather.perl6.nl wrote:
>
>> +=head3 Default constraints
>> +
>> +The default p{} only allows "/" as separator and does not allow path
>> elements
>> +to contain
>> +characters that won
2009/8/18 :
> Author: wayland
> Date: 2009-08-18 09:24:07 +0200 (Tue, 18 Aug 2009)
> New Revision: 28017
>
> +=item chdir FILENAME
> +X X
> +
> +=item chdir
> +
> +Gone, just set $*CWD (which throws an exception if it fails).
> +
chdir provides functionality that would be quite convoluted to mimi
On Tue, Aug 18, 2009 at 09:24:08AM +0200, pugs-comm...@feather.perl6.nl wrote:
> +=head3 Default constraints
> +
> +The default p{} only allows "/" as separator and does not allow path
> elements
> +to contain
> +characters that won't work on modern Windows and Unix like \ / ? % * : | " >
> <,
Author: wayland
Date: 2009-08-18 09:24:07 +0200 (Tue, 18 Aug 2009)
New Revision: 28017
Modified:
docs/Perl6/Spec/S02-bits.pod
docs/Perl6/Spec/S16-io.pod
docs/Perl6/Spec/S28-special-names.pod
docs/Perl6/Spec/S32-setting-library/IO.pod
Log:
[S02] Changed :io to :p and :path
[S16] Documen
19 matches
Mail list logo
