From: Otto Moerbeek <otto@drijf.net>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Debugging help sought
Date: Thu, 6 Aug 2020 09:16:34 +0200 [thread overview]
Message-ID: <20200806071634.GA96322@clue.drijf.net> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2008061455180.61909@aneurin.horsfall.org>
On Thu, Aug 06, 2020 at 02:57:25PM +1000, Dave Horsfall wrote:
> On Wed, 5 Aug 2020, Warner Losh wrote:
>
> > On Wed, Aug 5, 2020, 8:12 PM Jim Capp <jcapp@anteil.com> wrote:
> > Looking through the code, I see some awfully long function names.
> > Does anyone recall if there are/were limits on the size of
> > variable and function names?
> >
> > 8 I think was the limit.
>
> Seven plus the leading (implied) underscore?
>
> -- Dave
K&R 1st edition Reference Manual section 2.2 mentions 8 (including
underscore) as the number of significant characters, though names can
be longer. External names are more restricted: it has a table of
limits for external names for various targerts. PDP-11 is 7 chars,
Honeywell 6000 is 6 chars (with no case distinction).
-Otto
next prev parent reply other threads:[~2020-08-06 7:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 1:28 Adam Thornton
2020-08-06 2:01 ` Jim Capp
2020-08-06 3:04 ` Warner Losh
2020-08-06 3:08 ` Warner Losh
2020-08-06 5:55 ` Adam Thornton
2020-08-06 4:57 ` Dave Horsfall
2020-08-06 7:16 ` Otto Moerbeek [this message]
2020-08-06 15:47 ` Paul Winalski
2020-08-06 16:09 ` Larry McVoy
2020-08-06 16:19 ` Paul Winalski
2020-08-06 16:24 ` Larry McVoy
2020-08-06 23:41 ` Adam Thornton
2020-08-07 0:35 ` Warner Losh
2020-08-07 4:30 ` Adam Thornton
2020-08-07 5:49 ` Warner Losh
2020-08-07 5:54 ` Adam Thornton
2020-08-07 16:07 Noel Chiappa
2020-08-07 17:11 ` John Cowan
2020-08-07 20:48 ` 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=20200806071634.GA96322@clue.drijf.net \
--to=otto@drijf.net \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/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).