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 09:35:11 -0400	[thread overview]
Message-ID: <1413552911.3770380.180156925.37C2AFA9@webmail.messagingengine.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1410171317090.1909@aneurin.horsfall.org>

On Thu, Oct 16, 2014, at 22:21, Dave Horsfall wrote:
> On Thu, 16 Oct 2014, Mark Longridge wrote:
> 
> > It seems like early cc could only use variable and function names up to 
> > 8 characters.
> 
> In those days it took only the first seven and ignored the rest, 
> prepending an underscore as you discovered.  I don't remember when longer 
> names were recognised; for all I know it could've been around when 
> pathnames could be longer than 14 chars (which I think may have been a 
> BSDism).

For externals, it's a limitation of the PDP-11 a.out format. Other
systems may or may not have had the same limit or a different limit.

For VAX, 4BSD appears to use an "index into file string table", whereas
3BSD still has an 8-character string. I don't see any provision in the
4BSD linker for loading 3BSD binaries.

Filenames over 14 characters appear to have been introduced in 4.1BSD.



  reply	other threads:[~2014-10-17 13:35 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 [this message]
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
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=1413552911.3770380.180156925.37C2AFA9@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).