Manuel M. Garcia mgarcia at cole-switches.com
Thu Dec 19 13:03:49 EST 2002

• Previous message (by thread): PYC Files
• Next message (by thread): How can I force the use-only-after-declaration?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Thu, 19 Dec 2002 12:45:44 +0100, "Marco Spedaletti"
<NOSPAM at NOSPAM.IT> wrote:
(edit)
>    int a, c;
>
>    a = 100; /* Ok! */
>    b = 200; /* Error! */

http://pychecker.sourceforge.net/

This is one of the many types of errors that PyChecker checks for.

Once my Python source is more than 3 screens long, I run PyChecker on
it regularly.

Frankly, I like Python's permissiveness and PyChecker's fussiness.
For me I code correct code faster with this pair than with languages
that force declaration of identifiers before use.

Manuel

---

• Previous message (by thread): PYC Files
• Next message (by thread): How can I force the use-only-after-declaration?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list