Re: Language Discussion Summaries
Miko O'Sullivan wrote: The idea of discussion summaries has been well received, ... I read this thread over the past couple of days. It's only today that, having thought about it, an objection occurred to me. I've no problem with people summarizing threads, but with this bit: The summaries will be located at http://www.idocs.com/perl6/ Why? I read the Perl 6 language list with a news-reader, which conveniently shows new articles when it's run. People subscribed to read this by e-mail get similar service. I don't want to have to remember to check a webpage on a regular basis just to see if anything new has cropped up there. Couldn't thread summaries just be sent to this list? Piers would almost certainly link to them in his weekly summaries -- he has done previously when people, most notably MikeL, have posted ad hoc summaries of particular topics. So Damian, and anybody else who doesn't read every message but still follows Piers's excellent updates, would still have thread summaries drawn to his attention and be able to read them. Smylers
Re: newline as statement terminator
On Tue, Feb 04, 2003 at 01:57:00AM +0100, Stéphane Payrard wrote:
In the tradition of Perl concision, I would like newline to be a
statement terminator everywhere it can: that is when
a) the parser expects an operator
_and_ b) we are not in the middle of a parenthesised expression.
Accessorily, it would also help people to switch back and forth
between language that use newline as statement terminator and perl6:
they will not be burn anymore when forgetting a semicolon.
Semicolons are still allowed everywhere as statement terminator
because empty statements are.
So, In the common case, oneliner atomic statements, the proposed rule
means: you can drop the ending semicolon.
BTW: Atomic statement are statement composed of one expression only.
For composite multiline statements, see About the b) rule below.
Multiline atomic statements just have to be broken at the right
place to avoid to break them:
a +
b
is equivalent to
a + b
But
a
+ b
are two statements.
And
$a = $something-{very}-[$complex] - $that('goes')-to(qw(the line end))
+ and_then('wrapped_like_this');
is two statements?
(and not even a Useless use of a constant in a void context warning)
Although I use this all the time, grovelling round the perl5 source, I could
only find this sort of idiom used in Match::BigInt's tests. And that was
like this:
plan tests = 669
+ 16; # own tests
On Mon, Feb 03, 2003 at 07:37:44PM -0600, Allison Randal wrote:
Miko O'Sullivan wrote:
NOTE TO ALLISON RANDAL: in your face-to-face meetings next week, please
make sure that Larry Wall isn't really Guido van Rossum with a fake
mustache.
Righto. No reptiles, only jewels and birds. And possibly the occasional
snark. ;)
There's nothing wrong with stealing, er borrowing the good bits of
reptiles though, is there?. I didn't think that perl was fussy about where
it gets its inspiration from. And they shouldn't complain, as imitation is
the sincerest form of flattery.
On Tue, Feb 04, 2003 at 02:24:48PM +1100, Deborah Ariel Pickett wrote:
Personally, as a Perl programmer, I *like* semicolons. They are the
programming equivalent of the end-of-phrase markers you get in music to
tell your brain to take a breath.
Hmm. So if some saboteur erases all end-of-phrase markers from the musical
score you are reading, does that mean that after a while you turn blue and
then fall over? :-)
Nicholas Clark
Re: newline as statement terminator
Nicholas Clark wrote: There's nothing wrong with stealing, er borrowing the good bits of reptiles though, is there?. I didn't think that perl was fussy about where it gets its inspiration from. It isn't and never will be. We're openly friendly to all languages. But Perl is also quite different from most languages, so what works for them may not work for us. It's a balance, like everything else in design. Allison
Re: Language Discussion Summaries
Smylers [EMAIL PROTECTED] writes: Miko O'Sullivan wrote: The idea of discussion summaries has been well received, ... I read this thread over the past couple of days. It's only today that, having thought about it, an objection occurred to me. I've no problem with people summarizing threads, but with this bit: The summaries will be located at http://www.idocs.com/perl6/ Why? I read the Perl 6 language list with a news-reader, which conveniently shows new articles when it's run. People subscribed to read this by e-mail get similar service. I don't want to have to remember to check a webpage on a regular basis just to see if anything new has cropped up there. Couldn't thread summaries just be sent to this list? Piers would almost certainly link to them in his weekly summaries -- he has done previously when people, most notably MikeL, have posted ad hoc summaries of particular topics. That's definitely a good idea. With the added advantage that, if a reader wants, the whole thread is immediately accessible for further investigation. -- Piers
