From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] early cc variable and function names
Date: Sat, 18 Oct 2014 18:25:56 +1100 [thread overview]
Message-ID: <20141018072556.GC41494@eureka.lemis.com> (raw)
In-Reply-To: <CADxT5N4x_q8zreY_ky7SwNn2OqK07OnqO+uUAm_pRfALo-5iZA@mail.gmail.com>
On Thursday, 16 October 2014 at 21:51:56 -0400, Mark Longridge wrote:
> So it would seem that function names can only be 7 characters in
> length. I am not sure if limitations of early cc were documented
> anywhere.
This is really an identifier issues, and it's documented in K&R 1st
edition, page 179:
DEC PDP-11 7 characters, 2 cases
Honeywell 6000 6 characters, 1 case
IBM 360/370 7 characters, 1 case
Interdata 8/32 8 characters, 2 cases
Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141018/eafed5ba/attachment.sig>
next prev parent reply other threads:[~2014-10-18 7:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2014-10-17 20:42 ` Larry McVoy
2014-10-17 16:11 Noel Chiappa
2014-10-18 10:32 Noel Chiappa
2014-10-18 23:03 ` Ron Natalie
2014-10-18 23:11 ` Dave Horsfall
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=20141018072556.GC41494@eureka.lemis.com \
--to=grog@lemis.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).