Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion if not C<,> then what?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Juerd  
View profile  
 More options Jul 9 2004, 5:09 am
Newsgroups: perl.perl6.language
From: ju...@convolution.nl (Juerd)
Date: Fri, 9 Jul 2004 11:09:38 +0200
Local: Fri, Jul 9 2004 5:09 am
Subject: Re: if not C<,> then what?
Michele Dondi skribis 2004-07-09 10:39 (+0200):

> kinda syntax too, and I, for one, will regret not having it anymore, I
> wonder wether something vaguely like the following example could (be made
> to) work:
>   print.then{next} if /stgh/;

Ehm. It can probably be made to work with sufficient black magic, but I
fail to see how:

- then as a method of print makes sense

- a hash returned by that method makes sense

If evaluation of hash keys is delayed until necessary, all you have to
do is make print return an object that has a then method. And it doesn't
have to do anything, even.

I think "then" as an infix operator is the way to go, if comma really
won't allow us to write this. "then" as a method my brain won't grok.

Juerd


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.