The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: random832@fastmail.us (random832@fastmail.us)
Subject: [TUHS] early cc variable and function names
Date: Fri, 17 Oct 2014 16:37:08 -0400	[thread overview]
Message-ID: <1413578228.125790.180311153.48CF1319@webmail.messagingengine.com> (raw)
In-Reply-To: <20141017025242.GH6963@mcvoy.com>

On Thu, Oct 16, 2014, at 22:52, Larry McVoy wrote:
> abc.st_size
> 
> Huh, abc is a struct stat.
> 
> I get that it was a bug and needed to be fixed but I wish that everyone 
> still pretended that it was one namespace, makes code so much easier to
> read.

I'm not sure what your design is that you're more than a screen away
from either its declaration, a stat call, or the fact that it's got size
_and_ mode _and_ mtime etc.

And if you do that, why stop there? Why not require the type to be
repeated to dereference any pointer?

while(*x == 0)

is x a pointer to int, to char, to another pointer, etc?



  parent reply	other threads:[~2014-10-17 20:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17  2:29 Noel Chiappa
2014-10-17  2:40 ` John Cowan
2014-10-17  2:52   ` Larry McVoy
2014-10-17  3:46     ` John Cowan
2014-10-17  3:54       ` Larry McVoy
2014-10-17 19:41       ` Clem Cole
2014-10-17 20:37     ` random832 [this message]
2014-10-17 20:42       ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2014-10-18 10:32 Noel Chiappa
2014-10-18 23:03 ` Ron Natalie
2014-10-18 23:11   ` Dave Horsfall
2014-10-17 16:11 Noel Chiappa
2014-10-17  1:51 Mark Longridge
2014-10-17  2:20 ` Milo Velimirovic
2014-10-17  2:21 ` Dave Horsfall
2014-10-17 13:35   ` random832
2014-10-17 13:44     ` Warner Losh
2014-10-17 14:07       ` arnold
2014-10-17 14:22         ` Milo Velimirović
2014-10-17 19:29         ` random832
2014-10-18  7:25 ` Greg 'groggy' Lehey

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=1413578228.125790.180311153.48CF1319@webmail.messagingengine.com \
    --to=random832@fastmail.us \
    /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).