Steve Holden wrote:
> r0g wrote:
>> David Robinow wrote:
>>> On Sun, Jan 3, 2010 at 10:42 PM, Roy Smith wrote:
In article ,
David Robinow wrote:
> On Sun, Jan 3, 2010 at 8:09 PM, Tim Roberts wrote:
>> More than "not required", it was "not relevant". This led to one of th
r0g wrote:
> David Robinow wrote:
>> On Sun, Jan 3, 2010 at 10:42 PM, Roy Smith wrote:
>>> In article ,
>>> David Robinow wrote:
>>>
On Sun, Jan 3, 2010 at 8:09 PM, Tim Roberts wrote:
> More than "not required", it was "not relevant". This led to one of the
> most infamous program
On Sun, 03 Jan 2010 23:42:44 -0500, David Robinow wrote:
> On Sun, Jan 3, 2010 at 10:42 PM, Roy Smith wrote:
>> In article ,
>> David Robinow wrote:
>>
>>> On Sun, Jan 3, 2010 at 8:09 PM, Tim Roberts wrote:
>>> > More than "not required", it was "not relevant". This led to one of
>>> > the mo
David Robinow wrote:
> On Sun, Jan 3, 2010 at 10:42 PM, Roy Smith wrote:
>> In article ,
>> David Robinow wrote:
>>
>>> On Sun, Jan 3, 2010 at 8:09 PM, Tim Roberts wrote:
More than "not required", it was "not relevant". This led to one of the
most infamous programming blunders in the
On Sun, Jan 3, 2010 at 10:42 PM, Roy Smith wrote:
> In article ,
> David Robinow wrote:
>
>> On Sun, Jan 3, 2010 at 8:09 PM, Tim Roberts wrote:
>> > More than "not required", it was "not relevant". This led to one of the
>> > most infamous programming blunders in the early days of the space pr
In article ,
David Robinow wrote:
> On Sun, Jan 3, 2010 at 8:09 PM, Tim Roberts wrote:
> > More than "not required", it was "not relevant". This led to one of the
> > most infamous programming blunders in the early days of the space program,
> > when one programmer accidentially typed a period
On Sun, Jan 3, 2010 at 8:09 PM, Tim Roberts wrote:
> More than "not required", it was "not relevant". This led to one of the
> most infamous programming blunders in the early days of the space program,
> when one programmer accidentially typed a period instead of a comma
> resulting in the loss o
In article ,
Tim Roberts wrote:
> Roy Smith wrote:
> >
> >2) Whitespace was not required in many places. For example, the following
> >two statements (this will only make sense in a fixed-width font) are
> >identical:
> >
> > DO 10 I = 1, 10
> > DO10I=1,10
>
> More than "not req
Roy Smith wrote:
>
>2) Whitespace was not required in many places. For example, the following
>two statements (this will only make sense in a fixed-width font) are
>identical:
>
> DO 10 I = 1, 10
> DO10I=1,10
More than "not required", it was "not relevant". This led to one of the
On Jan 1, 4:02�pm, Dan Stromberg wrote:
> I put together a page about significant whitespace (and the lack thereof).
The real problem is your use of proportional spaced fonts.
>
> You're invited to check it out:
>
> http://stromberg.dnsalias.org/~dstromberg/significant-whitespace.html
--
http:
On Jan 2, 10:29 am, Roy Smith wrote:
>
> To address your question more directly, here's a couple of ways Fortran
> treated whitespace which would surprise the current crop of
> Java/PHP/Python/Ruby programmers:
>
> 1) Line numbers (i.e. the things you could GOTO to) were in column 2-7
> (column 1
On Jan 2, 4:19 pm, Emile van Sebille wrote:
> On 1/1/2010 5:05 PM Steven D'Aprano said...
>
> > In Python terms, imagine if we could write
>
> > foriinrange(10):
>
> > instead of the usual
>
> > for i in range(10):
>
> > Since the colon makes it unambiguous that it is some sort of block
On 1/1/2010 5:05 PM Steven D'Aprano said...
In Python terms, imagine if we could write
foriinrange(10):
instead of the usual
for i in range(10):
Since the colon makes it unambiguous that it is some sort of block
construct, and it starts with "for", it must be a for loop. Pretty
horr
On Sat, 02 Jan 2010 10:42:39 +, Duncan Booth wrote:
> Donn wrote:
>
>> On Saturday 02 January 2010 00:02:36 Dan Stromberg wrote:
>>> I put together a page about significant whitespace (and the lack
>>> thereof).
>> The only thing about Python's style that worries me is that it can't be
>> co
Donn wrote:
> On Saturday 02 January 2010 00:02:36 Dan Stromberg wrote:
>> I put together a page about significant whitespace (and the lack
>> thereof).
> The only thing about Python's style that worries me is that it can't
> be compressed like javascript can*, and perhaps that will prevent it
>
On Fri, Jan 1, 2010 at 9:56 PM, Donn wrote:
> On Saturday 02 January 2010 00:02:36 Dan Stromberg wrote:
>> I put together a page about significant whitespace (and the lack thereof).
> The only thing about Python's style that worries me is that it can't be
> compressed like javascript can*, and per
On Saturday 02 January 2010 00:02:36 Dan Stromberg wrote:
> I put together a page about significant whitespace (and the lack thereof).
The only thing about Python's style that worries me is that it can't be
compressed like javascript can*, and perhaps that will prevent it becoming a
browser-side
In article
<3db95947-1e35-4bd1-bd4c-37df646f9...@v25g2000yqk.googlegroups.com>,
John Machin wrote:
> On Jan 2, 10:29 am, Roy Smith wrote:
>
> >
> > To address your question more directly, here's a couple of ways Fortran
> > treated whitespace which would surprise the current crop of
> > Java/
Dan Stromberg wrote:
I put together a page about significant whitespace (and the lack thereof).
You're invited to check it out:
http://stromberg.dnsalias.org/~dstromberg/significant-whitespace.html
You might also want to mention that programmers tend to indent anyway
for clarity.
--
http://m
On Fri, 01 Jan 2010 14:19:28 -0800, Chris Rebert wrote:
> For those of us who weren't around during the heyday of FORTRAN, can
> anyone describe this apparently much-reviled significant whitespace
> feature that continues to make some programmers unjustly fearful about
> Python's use of indentatio
In article ,
Chris Rebert wrote:
> On Fri, Jan 1, 2010 at 2:02 PM, Dan Stromberg wrote:
> > I put together a page about significant whitespace (and the lack thereof).
> >
> > You're invited to check it out:
> >
> > http://stromberg.dnsalias.org/~dstromberg/significant-whitespace.html
>
> For t
On Fri, Jan 1, 2010 at 2:02 PM, Dan Stromberg wrote:
> I put together a page about significant whitespace (and the lack thereof).
>
> You're invited to check it out:
>
> http://stromberg.dnsalias.org/~dstromberg/significant-whitespace.html
For those of us who weren't around during the heyday of F
22 matches
Mail list logo
