Re: OT: pronouncing "www" (was: Re: ... as a term)

Thus it was written in the epistle of Austin Hastings, > "foo.bar" ne "www.foo.bar" > > pronounce("foo.bar") eq pronounce("www.foo.bar") > > As in, "Surf to www.perl.org and read the new ..." > > sounds like > > "Surf to perl dot org and read the new ..." > > =Austin Just to be absolutely ce

Re: OT: pronouncing "www" (was: Re: ... as a term)

"foo.bar" ne "www.foo.bar" pronounce("foo.bar") eq pronounce("www.foo.bar") As in, "Surf to www.perl.org and read the new ..." sounds like "Surf to perl dot org and read the new ..." =Austin --- Tom Christiansen <[EMAIL PROTECTED]> wrote: > >The "www" in e.g., "www.netscape.com" is pronounce

Re: OT: pronouncing "www" (was: Re: ... as a term)

>The "www" in e.g., "www.netscape.com" is pronounced, IMO, in >the same way as other useless, should-be-obvious punctuation. >It's silent. Seems like something you should take up with RFC 819, or maybe with RFC 881, considering that they and their ramifying successors all seem to be in flagrant

Re: OT: pronouncing "www" (was: Re: ... as a term)

The "www" in e.g., "www.netscape.com" is pronounced, IMO, in the same way as other useless, should-be-obvious punctuation. It's silent. --- Dave Storrs <[EMAIL PROTECTED]> wrote: > > > On Thu, 24 Aug 2000, Bart Lateur wrote: > > On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: >

OT: pronouncing "www" (was: Re: ... as a term)

On Thu, 24 Aug 2000, Bart Lateur wrote: > On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: > >If you want to save the world, come up with a better way to say "www". > >(And make it stick...) > > "The world"? This problem only exists in English! > > We pronounce it something similar

Re: [OT] How to pronounce 'www' (was Re: ... as a term)

On Wed, 23 Aug 2000 20:58:02 -0700, Daniel Chetlin wrote: >I use "dub dub dub", which I picked up at Intel. I find it much easier to >pronounce quickly than anything that uses an approximant. I do like "wibbly". Or "wibble". It ha

[OT] How to pronounce 'www' (was Re: ... as a term)

On Wed, Aug 23, 2000 at 11:43:04PM -0400, Uri Guttman wrote: >>> On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: If you want to save the world, come up with a better way to say "www". (And make it stick...) [snip of other possibilities] > the variation i learned somewhere was

Re: ... as a term

> "BCW" == Bryan C Warnock <[EMAIL PROTECTED]> writes: BCW> On Wed, 23 Aug 2000, Bart Lateur wrote: >> On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: >> >> >If you want to save the world, come up with a better way to say "www". >> >(And make it stick...) >> >> "Th

Re: ... as a term

On Wed, 23 Aug 2000, Bart Lateur wrote: > On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: > > >If you want to save the world, come up with a better way to say "www". > >(And make it stick...) > > "The world"? This problem only exists in English! > > We pronounce it something similar

Re: ... as a term

On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: >If you want to save the world, come up with a better way to say "www". >(And make it stick...) "The world"? This problem only exists in English! We pronounce it something similar to "way way way". -- Bart.

Re: ... as a term

> If you want to save the world, come up with a better way to say "www". > (And make it stick...) The funniest thing I've ever read is that Tim Berners-Lee's wife supposedly criticized the term "www" because "world wide web" was shorter to say than "www" (3 syllables vs. 9). -Nate

Re: ... as a term

> > I think this is fraught with peril. I'd have expected: > > > > print (1, 2, 3, ...) or die; > > > > to print > > > > 12345678910111213141516171819202122232425262728etc > > No, if that's what you wanted, you'd get it with > >print( 1, 2, 3 ..

Re: ... as a term

Larry Wall wrote: > John Porter writes: > : Could you make it "evaporate" and compile time, just like the (proposed) qc()? > > Hard to make it evaporate at compile time and still give a warning at > run time. :-) Eh, eh... Curdle it into the appropriate warn() call! -- John Porter

Re: ... as a term

John Porter writes: : Could you make it "evaporate" and compile time, just like the (proposed) qc()? Hard to make it evaporate at compile time and still give a warning at run time. :-) Larry

Re: ... as a term

Larry Wall wrote: > > I'd entertain a proposal that ... be made a valid term that happens > to do nothing, so that you can run your examples through perl -c for > syntax checks. Or better, make it an official "stub" for rapid > prototyping, with some way of getting a warning whenever you execute

Re: ... as a term

Piers Cawley wrote: > > You forgot: > print (1, 11, 21, 1211, ...) print( 'M', 'MI', 'MIU', ... ) ALso, Larry, how about making the various common emoticons meaningful? please do come from 10; :-) I.e. "belay that command". -- John Porter We're building the

Re: ... as a term

Damian Conway wrote: > > I think this is fraught with peril. I'd have expected: > > print (1, 2, 3, ...) or die; > > to print > > 12345678910111213141516171819202122232425262728etc No, if that's what you wanted, you'd get it with print( 1, 2, 3 .. ) # RFC 24 -- Jo

Re: ... as a term

Larry Wall wrote: > > Either that, or it's a funny unary operator that can take 0 or 1 argument. > > But I'd be happy with just ... as a statement. Dwimming the unary > operator may not be worth it. Especially since it might be confused > with the binary operator. Could you make it "evapora

Re: ... as a term

On Tue, Aug 22, 2000 at 09:49:12AM -0400, John Porter wrote: > Damian Conway wrote: > > > > Easy. I'll just add a C operator to Q::S. It would take no > > arguments and return a (lazy?) list of every possible Perl subroutine. > > > > PS: Can you tell whether I'm joking? > > I think you're both

Re: ... as a term

Damian Conway wrote: > > Easy. I'll just add a C operator to Q::S. It would take no > arguments and return a (lazy?) list of every possible Perl subroutine. > > PS: Can you tell whether I'm joking? I think you're both joking AND not joking, at the same time. -- John Porter We're buil

Re: ... as a term

Numerical python uses "..." in the same sense for axis lists in multi-dim arrays. (Improved syntax for multidim arrays is one wishlist item from PDL for the perl core. See RFC117) NumPy allows you to say: a[..., :]; where "..." means "however many", - so this is a slice along the last dimen

Re: ... as a term

Larry Wall <[EMAIL PROTECTED]> writes: > If you're into dwimmery, you could make all of these work, too: > > print (1, 2, 4, ...) > print (1, 4, 9, 16, 25, ...) > print (1, 1, 2, 3, 5, ...) > print ('a', 'b', 'c', ...) > print (3, 1, 4, 1, 5, 9, 6, 2, 5, ...) You forgot:

Re: ... as a term

On Mon, Aug 21, 2000 at 01:01:20PM -0600, Nathan Torkington wrote: >Larry Wall writes: >> I'd entertain a proposal that ... be made a valid term that happens >> to do nothing, so that you can run your examples through perl -c for >> syntax checks. Or better, make it an official "stub" for rapid >

Re: ... as a term

> [EMAIL PROTECTED] writes: > : We already have plenty of statements with implied semicolons: > : > : print "foo"; > : for @list {} > : print "bar"; > > Yes, we do, and I'm trying to figure out how to write a prototype for > one of those. :-) / 2 Under RFC 128 and

Re: ... as a term

[EMAIL PROTECTED] writes: : We already have plenty of statements with implied semicolons: : : print "foo"; : for @list {} : print "bar"; Yes, we do, and I'm trying to figure out how to write a prototype for one of those. :-) / 2 : I'd have expected: : : print (1, 2,

Re: ... as a term

> The interesting thing about ... is that you have to be able to > deal with it a statement with an implied semicolon: > > print "foo"; > ... > print "bar"; We already have plenty of statements with implied semicolons: print "foo"; for @list {}

Re: ... as a term

On Mon, Aug 21, 2000 at 05:49:39PM -0700, Larry Wall wrote: > [EMAIL PROTECTED] writes: > : I take it the existing C<...> operator would be unaffected? > > Essentially. The lexer is (and will continue to be) quite aware of the > difference between terms and operators. Oops, just read this. Ign

Re: ... as a term

On Mon, Aug 21, 2000 at 09:09:01AM -0700, Larry Wall wrote: > Randal L. Schwartz writes: > : if ($a == $b) { ... } # should this be string or number comparison? > > Actually, it's a syntax error, because of the ... there. :-) > > But that reminds me of something I wanted a few months ag

Re: ... as a term

[EMAIL PROTECTED] writes: : I take it the existing C<...> operator would be unaffected? Essentially. The lexer is (and will continue to be) quite aware of the difference between terms and operators. The interesting thing about ... is that you have to be able to deal with it a statement with an

Re: ... as a term

> Larry Wall writes: > > I'd entertain a proposal that ... be made a valid term that happens > > to do nothing, so that you can run your examples through perl -c for > > syntax checks. Or better, make it an official "stub" for rapid > > prototyping, with some way of getting a warni

Re: ... as a term

> I've always wished it was the famous "do what I mean" operator: > > if ($a eq "input") { > ... # let perl figure out what to do here > } else { > print "I need more input!\n"; > } > > That'd make "rapid application developm

Re: ... as a term

Larry Wall writes: > I'd entertain a proposal that ... be made a valid term that happens > to do nothing, so that you can run your examples through perl -c for > syntax checks. Or better, make it an official "stub" for rapid > prototyping, with some way of getting a warning whenever you execute >

Re: ... as a term

Ed Mills writes: : But don't {} or {1} sort of do the same thing? Well, { warn "Encountered stub"; (); } would be more like it. But the biggest problem with {} or {1} is that they don't resemble an ellipsis. Larry

RE: ... as a term

-Original Message- From: Ed Mills [mailto:[EMAIL PROTECTED]] > >Excellent idea- anything to get to production faster! > >But don't {} or {1} sort of do the same thing? I think the point here is readability, not unique functionality. There more then one way to do it :) -Corwin

Re: ... as a term

Excellent idea- anything to get to production faster! But don't {} or {1} sort of do the same thing? >From: Larry Wall <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: ... as a term >Date: Mon, 21 Aug 2000 09:09:01 -0700 (PDT) > >Randal L. Schwartz writes: >: if ($a == $b) { ... }

Re: ... as a term

> "Larry" == Larry Wall <[EMAIL PROTECTED]> writes: Larry> Randal L. Schwartz writes: Larry> : if ($a == $b) { ... } # should this be string or number comparison? Larry> Actually, it's a syntax error, because of the ... there. :-) Larry> But that reminds me of something I wanted a