Larry Wall wrote :
>
> Well, if anything, we're going the other direction, and enriching what
> you can do with a backslash in single quotes slightly. But it ought
> to be pretty easy to define your own hyperquotes. We might also have
> options on quotes like we do on regexen. Then we could te
On Tue, 2002-05-21 at 13:22, Buddha Buck wrote:
> At 01:10 PM 05-21-2002 -0400, Aaron Sherman wrote:
> >The quesiton here is that C<\\'>, which means something different in
> >your recommendation than it means in Perl5, but still does the same
> >thing
>
> And the other question is how to ge
On 05/21/02 Aaron Sherman wrote:
> On Tue, 2002-05-21 at 12:57, Michael G Schwern wrote:
>
> > Here's an easier one: backslash followed by the delimiter is that thing.
> > Everything else is literal.
> >
> > print 'c:\it\'s\easier\to\write\win32\paths\this\way';
> > print q{this is ok {
At 01:10 PM 05-21-2002 -0400, Aaron Sherman wrote:
>On Tue, 2002-05-21 at 12:57, Michael G Schwern wrote:
>
> > Here's an easier one: backslash followed by the delimiter is that thing.
> > Everything else is literal.
> >
> > print 'c:\it\'s\easier\to\write\win32\paths\this\way';
> > print
On Tue, 2002-05-21 at 12:57, Michael G Schwern wrote:
> Here's an easier one: backslash followed by the delimiter is that thing.
> Everything else is literal.
>
> print 'c:\it\'s\easier\to\write\win32\paths\this\way';
> print q{this is ok { and so is \} } C:\this };
I desire you print y
On 5/21/02 9:56 AM, "Aaron Sherman" <[EMAIL PROTECTED]> claimed:
> I guess the run-time checks will be required, and inlining of small
> chunks of code will never really be all that useful (as you cannot rip
> open that scope and optimize the whole context).
I think that a number of these issues
On Tue, May 21, 2002 at 11:03:42AM +0100, Nicholas Clark wrote:
> I believe that the correct rule for single quote context in perl should have
> been that backslash followed by anything is that thing.
That leaves Win32 users stuck in the same rut as now:
print 'c:\\it\'s\\going\\to\\be\\hard
On Mon, 2002-05-20 at 00:27, Larry Wall wrote:
> Aaron Sherman writes:
> : > Alternately, I think we should be able to mark subs as 'final' or 'inline'
> : > to indicate our guarantee that they won't be modified. Of course, it'll
> : > conflict with auto memoizing or auto currying modules that'd w
