inclusive-lower-bound, exclusive-upper-bound (was Re: Range Operation pre-PEP)
news at myNOSPAM.org
Sun May 13 09:26:37 CEST 2001
I meant, I find "1.0." to look uncool :) With the period on the end, not
that I dislike having to type "1.0" nessearily... i've never typed a
floating point without the decimal part, can't fathom why someone else
would... but the second period seeming to be connected to the floating point
is what bothers me. :)
But its your language. *grin*
"Andrew Maizels" <andrew at one.net.au> wrote in message
news:3AFDF826.17FAE504 at one.net.au...
> Stephen Hansen wrote:
> > I realize you said that you do not like semi-colons, but it seems to
> > that your use of a period as a statement seperator has its own problems.
> > Consider the following:
> > print 1.
> > In Python, that is printing a floating point number. In Pixy, that
> > printing an integer. Now, It'd be all fine and dandy to just make it a
> > language requirement that all floating points *have* a number after the
> > decimal point, but it eats at the clairity and starts looking uncool:
> > print 1.0.
> > Just an example. :)
> Yep, that's exactly what you have to do. Personally, I don't find 1.0
> uncool at all, unless it's a release number (I'd wait for 1.2, myself).
> To be precise, a period followed by whitespace is a statement separator;
> periods are allowed in other contexts with other meanings.
> There's only one game in town.
> You can't win.
> You can't break even.
> You can't quit the game. -- The four laws of thermodynamics.
More information about the Python-list