The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] C question for the historians
Date: Wed, 8 Nov 2017 13:39:19 -0700	[thread overview]
Message-ID: <CANCZdfrCBimhEWib8OUqy12_8qu5BjrdRY696ajeTSC3nrttOQ@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYKVyTAmOTT944md+0Lmg-yN=2=qwrDm+n3p_6+QvQ2JFg@mail.gmail.com>

Terminals used to have 80 columns almost universally back in the 80's (yes,
you can find exceptions). CGA/MHA/VGA consoles still do because they were
designed to replace said terminals. The notion, at least for FreeBSD, was
that you'd want to be able to easily hack on the code if you had to on the
console. Likely a bit antiquated, but there's a solid reason for it.

There's other side effects of that, most of which are good, but some
crazy...

Warner

On Wed, Nov 8, 2017 at 1:13 PM, ron minnich <rminnich at gmail.com> wrote:

> There's a lot of weird lore around use of C nowadays, a lot of it in my
> experience from folks who come from Java. But this w & MASK discussion is
> one of the weirder ones.
>
> For me one of the worst is the 80-column requirement that came from out of
> I don't know where. Let's see, we're all getting 4k monitors, and yet
> somehow
> 80 columns is how we have to write code? Hollerith would be proud.
>
>
>
> On Wed, Nov 8, 2017 at 11:05 AM Larry McVoy <lm at mcvoy.com> wrote:
>
>> On Wed, Nov 08, 2017 at 06:14:20PM +0000, Ralph Corderoy wrote:
>> > is better then why stop there?  Why not
>> >
>> >     if (((w & MASK) != FALSE) == TRUE)
>>
>>
>> Thanks for this, that's the perfect come back to the pedantic folks.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171108/04ffd755/attachment-0001.html>


  parent reply	other threads:[~2017-11-08 20:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 16:17 Arthur Krewat
2017-11-08 16:27 ` Warner Losh
2017-11-09 10:17   ` Michael Kjörling
2017-11-08 18:14 ` Ralph Corderoy
2017-11-08 18:34   ` Arthur Krewat
2017-11-08 19:05   ` Larry McVoy
2017-11-08 20:13     ` ron minnich
2017-11-08 20:23       ` Larry McVoy
2017-11-08 20:32         ` Ron Natalie
2017-11-08 20:39       ` Warner Losh [this message]
2017-11-08 20:41       ` Chet Ramey
2017-11-09  1:22         ` Ralph Corderoy
2017-11-09  1:41           ` Chet Ramey
2017-11-09  1:49             ` Arthur Krewat
2017-11-08 20:43       ` Bakul Shah
2017-11-08 20:55       ` Steve Nickolas
2017-11-08 20:36     ` Warner Losh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANCZdfrCBimhEWib8OUqy12_8qu5BjrdRY696ajeTSC3nrttOQ@mail.gmail.com \
    --to=imp@bsdimp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).