Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 93124 invoked from network); 28 Aug 2007 03:20:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Aug 2007 03:20:50 -0000 Received: (qmail 71481 invoked by uid 500); 28 Aug 2007 03:20:46 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 71469 invoked by uid 500); 28 Aug 2007 03:20:45 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 71453 invoked by uid 99); 28 Aug 2007 03:20:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2007 20:20:45 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.50.6.28] (HELO WM28.inbox.com) (208.50.6.28) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 28 Aug 2007 03:20:41 +0000 Received: from inbox.com (127.0.0.1:25) by inbox.com with [InBox.Com SMTP Server] id <708270022682.WM28> for from ; Mon, 27 Aug 2007 7:20:16 PM -0800 Mime-Version: 1.0 Date: Mon, 27 Aug 2007 19:20:15 -0800 Message-ID: <6F66EC5678A.00000805mbrown@inbox.com> From: Mark Brown Subject: Re: svn commit: r569152 - /incubator/stdcxx/branches/4.2.0/etc/config/src/LIMITS.cpp To: stdcxx-dev@incubator.apache.org In-Reply-To: <46D20E9E.7030806@roguewave.com> References: <566e5d0babe.0000053embrown@inbox.com> <20070823212907.722af1a983a@eris.apache.org> X-Mailer: INBOX.COM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-IWM-ACU: lUSRuHDNKDhkEfrmxwAJ4iapsHDTPO10whkGmXLLWeCc9QaMhTPy3i0xKaTh HybGYnMGLigWS1snwYIE71-FxUcOJ84QnQciws9UMsMM3j4iCTJYvEOpVr3s DQPJzda0r80dhtCg@ X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: sebor=40roguewave.com > Sent: Sun, 26 Aug 2007 17:37:02 -0600 > To: stdcxx-dev=40incubator.apache.org > Subject: Re: svn commit: r569152 - > /incubator/stdcxx/branches/4.2.0/etc/config/src/LIMITS.cpp >=20 > Mark Brown wrote: >>> -----Original Message----- >>> From: sebor=40roguewave.com >>> Sent: Fri, 24 Aug 2007 09:29:36 -0600 >>> To: stdcxx-dev=40incubator.apache.org >>> Subject: Re: svn commit: r569152 - >>> /incubator/stdcxx/branches/4.2.0/etc/config/src/LIMITS.cpp >>>=20 >>> Andrew, please be sure to observe the 78 characters/line limit >>> in Change Log entries as documented in bullet (3) of the Patch >>> Format section on the Bugs page: >>> http://incubator.apache.org/stdcxx/bugs.html=23patch_format >>>=20 >>> The reason for this limit in both ChangeLogs and source files >>> is that they all need to be readable on traditional VT100 text >>> terminals. >>=20 >> I have seen coding styles with a 79 character limit (for instance >> Python) but I am curious what the rationale for the 78 character limit >> is when even the VT100 displays have 80 columns? >=20 > Opening a file with 80 characters per line in emacs with a buffer > width set to 80 columns will wrap the last character of the next > line. So if all you have to work with is an 80x24 text terminal > and want to run emacs in it you want files to have no more than > 79 characters per line. You can recreate this experience in an > xterm or similar terminal by setting it to 80 characters and > starting emacs with the -nw option. If I understand correctly what you're describing, emacs -nw will display = lines with up to 79 characters in a 80 column frame without wrapping. = What, then, is the rationale for at most 78 characters? -- Mark