Indent testers needed (Prothon)

Mark Hahn mark at prothon.org
Sat Apr 3 01:29:03 EST 2004


I have a newer better-working version to download and test:

 http://prothon.org/pub/prothon/prothon-unstable-b266-win32.zip

The instructions are the same except the folder name will be Prothon:

Unzip the file which will make a folder called Prothon.  Drop your .pr file
into the folder.  Open a dos command window. CD to the win32 folder and run
the prothon.exe file with the .pr file name:

prothon.exe code.pr

Features:

1) You must use only tabs or only spaces for indents in any one file. You
cannot mix them.

2) Each indent level can have any number of characters more than the
previous level, whether you are using tabs or spaces.  If you drop back to
the left to dedent, and your column position does not match any level above,
you will get a lexer error.

3) If you  increase the indentation level above the previous line by even
one space, and that previous line does not end in a colon, then the new line
will be considered a continuation of the previous line.

4) If a line contains an active (not quoted or commented)  (, {, or [
without a matching end character, then the following line is always a
continuation, no matter what that following line contains.

5) There is still support for using the trailing backslash ( \ ) to indicate
that the next line is a continuation.  This may be removed in the future if
everyone agrees to do so.

6) A continuation line is effectively added to the end of the previous line
so any line following a continuation line uses the last non-continuation
line for the "previous line" in all the rules above.






More information about the Python-list mailing list