On 16:21 Fri 09 Jul , John Meacham wrote:
I would think it is a typo in the report. Every language out there seems
to think 0**0 is 1 and 0**y | y /= 0 is 0. I am not sure whether it is
mandated by the IEEE standard but a quick review doesn't say they should
be undefined (and the report
On Jul 11, 2010, at 9:20 PM, Daniel Fischer wrote:
* Prove the binomial theorem *without* the convention 0**0 := 1
Except that in the binomial theorem, one uses (^) and not (**).
For (^), setting x ^ 0 = 1 is, as far as I'm aware, uncontested.
This is not so: the exponent in the binomial
On Sat, Jul 10, 2010 at 6:40 PM, Julian Fleischer
julian.fleisc...@fu-berlin.de wrote:
I guess I'm actually messing things up using the word natural - how can
expand the multiplication of zero with itself zero times be natural?
How could it not be?
That is to say, what initial value would
On Sunday 11 July 2010 00:40:07, Julian Fleischer wrote:
Hi wren,
x**0 := 1, by convention.
[...]
So far as I'm aware, the x**0=1 vs 0**y=0 conflict leads to 0**0
[being] undefined
x**0 is 1 /by definition, 0**y naturally is 0, since (for example) 0**2
expands to 0*0 (being 0 of
Hi wren,
x**0 := 1, by convention.
[...]
So far as I'm aware, the x**0=1 vs 0**y=0 conflict leads to 0**0 [being]
undefined
x**0 is 1 /by definition, 0**y naturally is 0, since (for example) 0**2 expands
to 0*0 (being 0 of course). So there is not a conflict of two definitions, it's
simply
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/8/10 22:25 , Alex Stangl wrote:
1. I.E. and e.g. should be followed by commas -- unless UK usage
differs from US standards. (Page 3 and elsewhere, although FFI chapter
I don't think I've ever seen them *followed* by commas. Preceded, always.
On Fri, 09 Jul 2010 10:07:06 -0400, you wrote:
I don't think I've ever seen them *followed* by commas. Preceded, always.
In American English, they're always followed by commas, and preceded by
comma, semicolon, dash or left parenthesis, depending on the specific
context.
Examples from various
On Fri, Jul 9, 2010 at 16:23, Steve Schafer wrote:
On Fri, 09 Jul 2010 10:07:06 -0400, brandon s. allbery wrote:
I don't think I've ever seen them *followed* by commas. Preceded,
always.
In American English, they're always followed by commas, and preceded by
comma, semicolon, dash or left
On Fri, 9 Jul 2010 17:14:31 +0200, you wrote:
One of the nice things about English is that there is often never an
always. See http://grammar.quickanddirtytips.com/ie-eg-oh-my.aspx for a
discussion.
Well, that page pretty much confirms what I said. In AMERICAN English,
they're always followed by
On Fri, Jul 9, 2010 at 18:35, Steve Schafer wrote:
On Fri, 9 Jul 2010 17:14:31 +0200, Sean Leather wrote:
One of the nice things about English is that there is often never an
always. See http://grammar.quickanddirtytips.com/ie-eg-oh-my.aspx for a
discussion.
Well, that page pretty much
I don't know what the rule is, but I personally just replace i.e.
with that is and e.g. with for example in my head, and then apply
whatever punctuation makes sense with those substitutions.
Cheers,
Greg
On 7/9/10 12:17 PM, Sean Leather wrote:
On Fri, Jul 9, 2010 at 18:35, Steve Schafer
Hi,
8. [...] Saying 0**0 is undefined seems reasonable,
but why 0**y?
I agree on 0**y being 0 (not undefined), but why should 0**0 be undefined? x**0
:= 1, by convention. Of course this is a still ongoing debate (regarding
analysis of functions etc.), but the most usefull approach for /any/
On Sat, Jul 10, 2010 at 12:12:15AM +0200, Julian Fleischer wrote:
8. [...] Saying 0**0 is undefined seems reasonable,
but why 0**y?
I agree on 0**y being 0 (not undefined), but why should 0**0 be undefined?
x**0 := 1, by convention. Of course this is a still ongoing debate (regarding
On Fri, Jul 09, 2010 at 06:07:04PM -0500, Alex Stangl wrote:
I wasn't arguing that 0**0 *ought* to be undefined, but that it
is a reasonable policy, since, as you point out, it's a matter
of ongoing debate. What I don't understand is why for y /= 0,
0**y would be undefined. Maybe the
Brandon S Allbery KF8NH allb...@ece.cmu.edu writes:
On 7/8/10 22:25 , Alex Stangl wrote:
1. I.E. and e.g. should be followed by commas -- unless UK usage
differs from US standards. (Page 3 and elsewhere, although FFI chapter
I don't think I've ever seen them *followed* by commas. Preceded,
On 10 July 2010 01:22, Ivan Lazar Miljenovic ivan.miljeno...@gmail.com wrote:
Brandon S Allbery KF8NH allb...@ece.cmu.edu writes:
On 7/8/10 22:25 , Alex Stangl wrote:
1. I.E. and e.g. should be followed by commas -- unless UK usage
differs from US standards. (Page 3 and elsewhere,
Julian Fleischer wrote:
Hi,
8. [...] Saying 0**0 is undefined seems reasonable,
but why 0**y?
I agree on 0**y being 0 (not undefined), but why should 0**0 be undefined? x**0
:= 1, by convention.
I'm not familiar with that convention. So far as I'm aware, the x**0=1
vs 0**y=0 conflict
Christopher Done wrote:
On 10 July 2010 01:22, Ivan Lazar Miljenovic ivan.miljeno...@gmail.com wrote:
Brandon S Allbery KF8NH allb...@ece.cmu.edu writes:
On 7/8/10 22:25 , Alex Stangl wrote:
1. I.E. and e.g. should be followed by commas -- unless UK usage
differs from US standards. (Page 3
based upon final version PDF created 7/6/2010 11:44:27
1. I.E. and e.g. should be followed by commas -- unless UK usage
differs from US standards. (Page 3 and elsewhere, although FFI chapter
seems to have the commas.) Also, inconsistent mix of British and American
usage throughout (-ize and -ise,
19 matches
Mail list logo
