A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-November/030063.html below:

[Python-Dev] Reindenting unicodedata.c

[Python-Dev] Reindenting unicodedata.c [Python-Dev] Reindenting unicodedata.cSkip Montanaro skip@pobox.com
Mon, 11 Nov 2002 08:45:34 -0600
    >> Just like Fredrik, I prefer 4 spaces indents over TABs and since the
    >> RE and Unicode code base used these 4 spaces indents all along, I'd
    >> also prefer to keep it that way.

    Guido> As long as you're actively maintaining that code, I see no reason
    Guido> to reformat it then.  But, as they say, you snooze, you lose. :-)

It seems to me that any files with "special needs" (unicodedata.c and the
various sre files come to mind) should have comments right near the top
which indicate the constraints which must be maintained (4-space indents,
1.5.2 compatibility, etc).

Skip



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4