Luke Palmer wrote:
Ooh! Why don't we have a dont command! With several variants:
dont FILE
dont BLOCK
dont { print Boo }
Would print:
You really *should* be more careful what you wish for Luke.
The following was just uploaded to the CPAN...
Damian
So, after all our discussions, my thinking regarding alternate blocks for
loops is now running like this:
1. It would definitely be useful to be able to catch the failure of a
block to iterate.
2. This ability should be available for all three types of block: Cwhile,
Miko O'Sullivan [EMAIL PROTECTED] writes:
Damian, now having terrible visions of someone suggesting Celswhen ;-)
Then may I also give you nightmares on: elsdo, elsdont, elsgrep, elstry ...
To quote from the INTERCAL manual (and I doubt I'm the first to steal
features from that powerful
I'm basically sold on Damian's conclusions. On the other
hand the 'otherwise' clause still feels to me like a CAPITALS
block.
So, as a tweak, I suggest:
while condition() {
...
}
NONE {
...
}
--
ralph
ralph wrote:
I'm basically sold on Damian's conclusions. On the other
hand the 'otherwise' clause still feels to me like a CAPITALS
block.
So, as a tweak, I suggest:
while condition() {
...
}
NONE {
...
}
Would you also change Celse to CELSE?
Luke Palmer wrote:
I'd rather have an in-betweener block too. Loops like this are very
common, and I hate doing prefix commas, if you know what I mean. I
realize NEXT often used for cleanup, so maybe you could introduse Yet
Another block, BETWEEN (or SQUEEZE).
Or are we just going to
Luke Palmer [EMAIL PROTECTED] writes:
On Tue, 30 Apr 2002, Miko O'Sullivan wrote:
Damian, now having terrible visions of someone suggesting Celswhen ;-)
Then may I also give you nightmares on: elsdo, elsdont, elsgrep, elstry ...
Ooh! Why don't we have a dont command! With several
Damian said:
6. Cotherwise would seem to fit the bill rather nicely.
To me, otherwise is a synonym for else, and that makes it too
confusingly similar. I foresee forever explaining to people the difference
between Celse and Cotherwise. I'm not sure if Cotherwise is popular
because it is
Damian Conway wrote:
Luke Palmer wrote:
Ooh! Why don't we have a dont command! With several variants:
dont FILE
dont BLOCK
dont { print Boo }
Would print:
You really *should* be more careful what you wish for Luke.
The following was just uploaded to the CPAN...
Damian
Damian posted:
NAME
Acme::Don't - The opposite of `do'
Wonderful job, Damian! I'll get to work on the complementary Acme::TryNotTo
module.
:-)
-Miko
On Wed, May 01, 2002 at 08:27:41AM -0400, Miko O'Sullivan wrote:
Damian said:
6. Cotherwise would seem to fit the bill rather nicely.
To me, otherwise is a synonym for else, and that makes it too
confusingly similar. I foresee forever explaining to people the difference
between Celse
Jonathan said:
I actually think exactly the opposite. In my mind otherwise would
just be a synonym for else so that
loop { ... } else { ... }
loop { ... } otherwise { ... }
would both be syntactically valid.
I believe that the intention is that they *aren't* synonyms, i.e. they look
Jonathan Scott Duff [EMAIL PROTECTED] wrote:
Miko O'Sullivan wrote:
Damian said:
6. Cotherwise would seem to fit the bill rather nicely.
To me, otherwise is a synonym for else, and that makes it too
confusingly similar. I foresee forever explaining to people the difference
In the true sprirt of perverseness, why not make loops into functions that
return the number of iterations taken. Then you can have
loop {
}
or die loop not taken\n;
;-)
--
A walk of a thousand miles begins with a single step...
then continues for another 1,999,999
On Wed, May 01, 2002 at 04:14:49PM +0100, Dave Mitchell wrote:
In the true sprirt of perverseness, why not make loops into functions that
return the number of iterations taken. Then you can have
loop {
}
or die loop not taken\n;
;-)
Right. This was my initial
On Wed, May 01, 2002 at 09:03:42AM -0500, Jonathan Scott Duff wrote:
Hmm. I wonder why the python community (apparently) have no problems
with elses on loops:
7.2 The while statement
The while statement is used for repeated execution as long as an
expression is
On Wed, May 01, 2002 at 04:22:29PM +1000, Damian Conway wrote:
NAME
Acme::Don't - The opposite of `do'
DESCRIPTION
...
Note that the code in the `don't' block must be syntactically valid
Perl. This is an important feature: you get the accelerated performance
of
At 11:44 AM 5/1/2002 -0500, Allison Randal wrote:
On Wed, May 01, 2002 at 04:22:29PM +1000, Damian Conway wrote:
NAME
Acme::Don't - The opposite of `do'
DESCRIPTION
...
Note that the code in the `don't' block must be syntactically valid
Perl. This is an
On Wed, May 01, 2002 at 12:53:39PM -0400, Melvin Smith wrote:
At 11:44 AM 5/1/2002 -0500, Allison Randal wrote:
Um... I know it's scary, but I can actually imagine using this (or
something like this) in development. I'll occasionally work on a section
of code I'm not ready to integrate yet.
On Wed, 2002-05-01 at 08:27, Miko O'Sullivan wrote:
Damian said:
6. Cotherwise would seem to fit the bill rather nicely.
To me, otherwise is a synonym for else, and that makes it too
confusingly similar. I foresee forever explaining to people the difference
between Celse and
On Wed, 2002-05-01 at 12:22, Allison Randal wrote:
On Wed, May 01, 2002 at 09:03:42AM -0500, Jonathan Scott Duff wrote:
[... in python ...]
while_stmt ::= while expression : suite
[else : suite]
That's straight from
On Wed, May 01, 2002 at 12:11:58PM -0700, Brent Dax wrote:
It's far too late to make it into 5.8, but it looks like it'll be in
5.10 when that comes out (in a year or two).
.. . . by which time 6.0 will have already been released, right?
Right?
--
Mark J. REED[EMAIL PROTECTED]
Mark J. Reed:
# On Wed, May 01, 2002 at 12:11:58PM -0700, Brent Dax wrote:
# It's far too late to make it into 5.8, but it looks like
# it'll be in
# 5.10 when that comes out (in a year or two).
# .. . . by which time 6.0 will have already been released, right?
#
# Right?
*bites back
On 4/17/02 10:02 PM, Brent Dax [EMAIL PROTECTED] claimed:
I'm working on a preliminary version right now. So far it's been
surprisingly easy--touches toke.c, perly.y, opcode.pl, pp.c, and
pp_hot.c. (Of course, it's also off an old bleadperl, but I doubt those
files change that actively.)
David Wheeler:
# On 4/17/02 10:02 PM, Brent Dax [EMAIL PROTECTED] claimed:
#
# I'm working on a preliminary version right now. So far it's been
# surprisingly easy--touches toke.c, perly.y, opcode.pl, pp.c, and
# pp_hot.c. (Of course, it's also off an old bleadperl, but I doubt
# those
On 5/1/02 12:11 PM, Brent Dax [EMAIL PROTECTED] claimed:
It's far too late to make it into 5.8, but it looks like it'll be in
5.10 when that comes out (in a year or two).
I figured. Too bad. ;-) A year or two is long time to wait!
Regards,
David
--
David Wheeler
On Wed, May 01, 2002 at 12:17:52PM -0700, David Wheeler wrote:
On 5/1/02 12:11 PM, Brent Dax [EMAIL PROTECTED] claimed:
It's far too late to make it into 5.8, but it looks like it'll be in
5.10 when that comes out (in a year or two).
I figured. Too bad. ;-) A year or two is long time to
On Wed, May 01, 2002 at 02:47:56PM -0400, Aaron Sherman wrote:
On Wed, 2002-05-01 at 12:22, Allison Randal wrote:
You also avoid totally annoying Pythonists who occasionally use (and
might be converted to) Perl. :)
...
Perl is fundamentally different in its approach and just as a
On Wed, May 01, 2002 at 01:04:10PM -0700, Brent Dax wrote:
*bites back sarcastic comment about the pace of Perl 6's development*
*fails to squelch reply about the survival rate of prematurely birthed
babies*
Some things just take time.
Allison Randal:
# On Wed, May 01, 2002 at 01:04:10PM -0700, Brent Dax wrote:
#
# *bites back sarcastic comment about the pace of Perl 6's
# development*
#
# *fails to squelch reply about the survival rate of prematurely birthed
# babies*
#
# Some things just take time.
I know, and I'm not
Damian said:
The CBETWEEN block can't decide whether to execute until
it knows whether the loop is going to iterate again. And it can't
know *that* until it has evaluated the condition again. At which
point, the $filename variable has the wrong value. :-(
The example is a little contrived
I now realize that my previous message was a little hard to read (plus I
sounded a bit harsh, which I did not mean to be, I was just excited,
thinking about this), because I insisted on being sort of stilted in my
pseudo-BNF. Here's a cleaner shot at what I meant:
flow:
Graham Barr:
# On Wed, May 01, 2002 at 12:17:52PM -0700, David Wheeler wrote:
# On 5/1/02 12:11 PM, Brent Dax [EMAIL PROTECTED] claimed:
#
# It's far too late to make it into 5.8, but it looks like
# it'll be in
# 5.10 when that comes out (in a year or two).
#
# I figured. Too bad.
On Wed, May 01, 2002 at 05:08:14PM -0400, Miko O'Sullivan wrote:
Damian said:
The CBETWEEN block can't decide whether to execute until
it knows whether the loop is going to iterate again. And it can't
know *that* until it has evaluated the condition again. At which
point, the $filename
i've made this entry form for the dungeons and dragons
game. it works as far as sending by email, but the
problem is that the stuff that you click on or type in
from the 3rd line of the form does not show up when
you click to send the results by email. please help me
in fixing this entry form to
35 matches
Mail list logo
