Re: RFC 328 (v1) Single quotes don't interpolate ' and by David L. Nicol- September 28, 2000 I don&39;t like it, and here&39;s why:> currently single quoted here docs don&39;t interpolate C<> or C<&39;>.We already have a way to read in arbitrary literals. I _like_ thefact that C<q> allows backslash to be used to allow including the delimiter.It works for any delimiter, too, not just single-quote.Could I go for getting rid of C<> except directly preceding the delimiterI think not, since if you really need to quote a series of backslashes youcan do it using a..http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg452.html RFC 328 (v1) Single quotes don't interpolate ' and by Perl6 RFC Librarian- September 28, 2000 This and other RFCs are available on the web at http:dev.perl.orgrfc=head1 TITLESingle quotes don&39;t interpolate &39; and =head1 VERSION Maintainer: Nicholas Clark <nicktalking.bollo.cx> Date: 28 Sep 2000 Mailing List: perl6-language-dataperl.org Number: 328 Version: 1 Status: Developing=head1 ABSTRACTRemove all interpolation within single quotes and the C<q()> operator, tomake single quotes 100% shell-like. C<> rather than C<> gives a singlebackslash; use...http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg451.html RFC 327 (v1) C<v> for Vertical Tab by Perl6 RFC Librarian- September 28, 2000 This and other RFCs are available on the web at http:dev.perl.orgrfc=head1 TITLEC<v> for Vertical Tab=head1 VERSION Maintainer: Nicholas Clark <nicktalking.bollo.cx> Date: 26 Sep 2000 Mailing List: perl6-language-dataperl.org Number: 327 Version: 1 Status: Developing=head1 ABSTRACTperl5 includes all of C&39;s escapes except C<v> (vertical tab). TreatingC<v> the same as C<a> C<b> C<e> C<f> C<h> C<r> C<t> would remove...http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg450.html Re: RFC 231 (v1) Data: Multi-dimensional arrayshashes and slices by Ilya Zakharevich- September 28, 2000 On Thu, Sep 28, 2000 at 11:39:51AM -0400, Karl Glazebrook wrote:> > > so what is wrong with the statement &39;y = 3x;&39; then > > > > That other constructs also create an array context, in which the> > behaviour of multiplication you propose is not appropriate.> > for exampleA prototypeless-function call.Ilyahttp://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg449.html Re: RFC 231 (v1) Data: Multi-dimensional arrayshashes and slices by Karl Glazebrook- September 28, 2000 Ilya Zakharevich wrote:> > so what is wrong with the statement &39;y = 3x;&39; then > > That other constructs also create an array context, in which the> behaviour of multiplication you propose is not appropriate.for example> I did not see any viable proposal on changing things in a major way.> To design such a change is a major work. We need to keep a lot of> possible combinations with other features in mind, and understand all> the ramifications and...http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg448.html Re: RFC 204 (v2) Arrays: Use list reference for multidimensional array access by Nathan Wiger- September 27, 2000 Bart Lateur wrote:> > >The problem is that> >> > $name = "myarray";> > $name = (1,2,3);> > print $name0,1; 1,2> >> >Is very consistent currently. Change one and you have to change the> >precedence and parsing of all symbolic refs.> > You are suggesting to keep a weird precedence rule, just to ease> symbolic dereferencing!! That&39;s... obscene.Where did I say that! I even said: I&39;m not necessarily against it, but.http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg447.html Re: RFC 204 (v2) Arrays: Use list reference for multidimensional array access by Bart Lateur- September 26, 2000 On Mon, 25 Sep 2000 19:26:38 -0700, Nathan Wiger wrote:>> I agree with both of you. It would be nice if $ precedence worked as Bart>> specified, but I still think that arrays should be arrays.>>The problem is that>> $name = "myarray";> $name = (1,2,3);> print $name0,1; 1,2>>Is very consistent currently. Change one and you have to change the>precedence and parsing of all symbolic refs.You are suggesting to keep a weird precedence rule,...http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg446.html Re: RFC 231 (v1) Data: Multi-dimensional arrayshashes and slices by Ilya Zakharevich- September 26, 2000 On Mon, Sep 25, 2000 at 06:30:22PM -0400, Karl Glazebrook wrote:> > Well, this shows that you entirely miss the problem of cryptocontexts.> > Context is determined by the "environment" of the operation, not by> > the operation. Context is propagated:> > > > the-left-hand-side-of-assignment ---> the-right-hand-side-of-assignment> > > so what is wrong with the statement &39;y = 3x;&39; then That other constructs also create an array context,..http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg445.html Re: RFC 204 (v2) Arrays: Use list reference for multidimensional array access by Nathan Wiger- September 25, 2000 > I agree with both of you. It would be nice if $ precedence worked as Bart> specified, but I still think that arrays should be arrays.The problem is that $name = "myarray"; $name = (1,2,3); print $name0,1; 1,2Is very consistent currently. Change one and you have to change theprecedence and parsing of all symbolic refs. I&39;m not sure this is a goodidea. I&39;m not necessarily against it, but it&39;s a deep issue not justconstrained to arrays in this one specific...http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg444.html Re: RFC 204 (v2) Arrays: Use list reference for multidimensional array access by Jeremy Howard- September 25, 2000 Buddha Buck wrote:> The main problem I see are these:>> array = (1,2,3,4); 2-dimensional array, using LOL syntax> print $array1,1; prints 4, OK> print $array1; prints > print $array1,1,1; prints > print $array1; prints >> According to RFC 204, $array1 should return 3,4, $array1 should> return (3,4), and $array1,1,1 should cause a runtime error.>> Interestingly enough, my original version of RFC204 had all three of> the...http://www.nntp.perl.org/group/perl.perl6.language.data/2000/09/msg443.html |