Well, I'm careful with my indenting, so I might get used to it quickly,
also, but that doesn't mean I would like it as a design choice.  Also, am I
remembering something that mitigates this issue? . . . Does it also require
a blank line, too.

In other words, would this be caught by the "compiler"

LOOP CONSTRUCT
        one line
        another line
                third line that should be indented under line two

Would Python complain about this because line two was not a loop construct
or something that would have a block of code associated with it and it found
an indention?
 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ed Leafe
Sent: Wednesday, September 27, 2006 11:31 AM
To: [EMAIL PROTECTED]
Subject: Re: [NF] Python - Thinking Differently

On Sep 27, 2006, at 11:21 AM, john harvey wrote:

> Ed, how is it easier when you have to indentation and  
> caPitaliZation issues?

        I agree on capitalization - it just sucks.

        As I noted in another post, I originally thought that indentation  
would be an issue. Turns out that since I am used to indenting my  
code anyway, it wasn't a problem at all. It actually forces you to  
create readable code, since you can't write code like this (which is  
perfectly legal in Fox):

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
lnDir = ADIR(laDir, lcDir + "*." + tcExt)
        IF tcExt $ "SCX,VCX"
        FOR lnCnt = 1 TO lnDir
lcFile = laDir[lnCnt, 1]
        USE (lcDir + lcFile) ALIAS LIB
                SCAN
        IF ATC(tcText, methods) > 0
pnFound = pnFound + 1
                lcRetVal = lcRetVal + CRLF + CHR(9) + "File: " +
FULL(lcFile)
                lcRetVal = lcRetVal + CRLF + CHR(9) + CHR(9) + "Object: " +
objname
                                ELSE
                IF ATC(tcText, properties) > 0
                        pnFound = pnFound + 1
lcRetVal = lcRetVal + CRLF + CHR(9) + "File: " + FULL(lcFile)
                lcRetVal = lcRetVal + CRLF + CHR(9) + CHR(9) + "Object: " +
objname
ENDIF
ENDIF
ENDSCAN
USE
ENDFOR
ENDIF
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

        Don't laugh, as I've had to deal with crazy code like this in  
several projects I've inherited. This is completely unreadable, yet  
Fox loves it.

-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com




[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to