Re: $*CWD and chdir()

2009-08-18 Thread Carlin Bingham
2009/8/19 Timothy S. Nelson : > >        Ok, so suppose we only allowed direct assignment to absolute paths? > That would be currently how it works. -- Carlin

Re: $*CWD and chdir()

2009-08-18 Thread Carlin Bingham
2009/8/19 Timothy S. Nelson : > >        So, if P5 does it for some global (note: global != environment) > variables, then why not do it for some in P6? > Because if (for some reason) I do: $> = 5; # Which calls setuid(5); print $>; # 5 Whereas: $*CWD = '..'; # which hypothetically calls chdir

Re: $*CWD and chdir()

2009-08-18 Thread Carlin Bingham
2009/8/18 David Green : > On 2009-Aug-18, at 3:27 am, Timothy S. Nelson wrote: >> >> On Tue, 18 Aug 2009, David Green wrote: >>> > or however that would work in P6.  It may have problems, but by definition > they're the same problems as chdir() has.  What am I missing? > > chdir is a familar funct

Re: r28017 - in docs/Perl6/Spec: . S32-setting-library

2009-08-18 Thread Carlin Bingham
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

Re: r28017 - in docs/Perl6/Spec: . S32-setting-library

2009-08-18 Thread Carlin Bingham
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