On Fri, 15 Sep 2000 10:29:31 +1100 (EST), Damian Conway wrote:
>Why not just give \I..\E a special "turn-on-interpolation" meaning in
>q{} docs?
This has been uppered already in the pre-discussion to this RFC.
Currently, '\I' is nothing special in q{}, and a lot of people don't
want to chage tha
My first preference is for overriding constant strings.
My second preference is to provide a user-defined quoting operator mechanism,
possibly as part of a user-defined operator mechanism.
My third preference is for a new operator.
I personally do not want to see q() screwed with.
Nat
Michael G Schwern writes:
> I have misgivings. I like single-quote context *because* you don't
> have to worry about anything magical (except ' and \).
Genericise it.
Alter the overloaded string constant behaviour of perl5 so that
when you say:
use MagicInterpolativeStrings;
$foo = '$bar <
Damian Conway wrote:
>
> Why not just give \I..\E a special "turn-on-interpolation" meaning in
> q{} docs?
>
> $code = '
>
> $x = $y;
> @a = (1..10);
> $name = \I$funcname\E;
>
> # etc.
>
> ';
>
> Damian
Yes. M
On Fri, Sep 15, 2000 at 10:29:31AM +1100, Damian Conway wrote:
> Why not just give \I..\E a special "turn-on-interpolation" meaning in
> q{} docs?
>
> $code = '
>
>
> $x = $y;
> @a = (1..10);
> $name = \I$funcname\E;
That would be four keystrokes
Why not just give \I..\E a special "turn-on-interpolation" meaning in
q{} docs?
$code = '
$x = $y;
@a = (1..10);
$name = \I$funcname\E;
# etc.
';
Damian
Michael G Schwern wrote:
[...]
> Personally, I'd solve this with sprintf():
>
> print F sprintf <<'END', $filename;
> $!
> $! execute a.com, copy and purge
> $!
> $ @sys$login:a.com
> $ copy %s sys$login:*.*
> $ purge sys$login:$filename
> $!
> $ exit
>
> but
On Thu, Sep 14, 2000 at 06:17:07PM -0400, Mark-Jason Dominus wrote:
>
> > > One could for example have a pragma to *really* tag variables
> > > lexically to be expanded within singlequotes.
>
> Or a pragma that simply changes the semantics of q{...} so that it has
> the proposed feature for th
> > One could for example have a pragma to *really* tag variables
> > lexically to be expanded within singlequotes.
Or a pragma that simply changes the semantics of q{...} so that it has
the proposed feature for the rest of the scope of the current block.
On Thu, Sep 14, 2000 at 05:11:39PM -0500, Jarkko Hietaniemi wrote:
> On Thu, Sep 14, 2000 at 06:04:41PM -0400, Mark-Jason Dominus wrote:
> >
> > > seconded by Mark-Jason Dominus <[EMAIL PROTECTED]>
> >
> > Except that I don't think adding this feature to the existing q{...}
> > is a good idea.
On Thu, Sep 14, 2000 at 06:04:41PM -0400, Mark-Jason Dominus wrote:
>
> > seconded by Mark-Jason Dominus <[EMAIL PROTECTED]>
>
> Except that I don't think adding this feature to the existing q{...}
> is a good idea. If I had to vote on your proposal, I would instantaly
> vote against it. I thi
I have misgivings. I like single-quote context *because* you don't
have to worry about anything magical (except ' and \).
On Thu, Sep 14, 2000 at 09:52:12PM -, Perl6 RFC Librarian wrote:
> print F < \$!
> \$! execute a.com, copy and purge
> \$!
> \$ \@sys\$log
> seconded by Mark-Jason Dominus <[EMAIL PROTECTED]>
Except that I don't think adding this feature to the existing q{...}
is a good idea. If I had to vote on your proposal, I would instantaly
vote against it. I think you should have invented a new operator or a
pragma or something.
13 matches
Mail list logo
