The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] long lived programs
Date: Thu, 05 Apr 2018 22:57:49 -0700	[thread overview]
Message-ID: <20180406055756.A6927156E510@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 05 Apr 2018 22:03:40 -0400." <1522980220.3263789.1328338032.3CD6D7F7@webmail.messagingengine.com>

On Thu, 05 Apr 2018 22:03:40 -0400 Random832 <random832 at fastmail.com> wrote:
Random832 writes:
> On Thu, Apr 5, 2018, at 17:38, Bakul Shah wrote:
> > May be case itself is such a historical artifact?  AFAIK all non-roman 
> > scripts are without case distinction.
> 
> Greek and Cyrillic both have cases. And the Hiragana/Katakana distinction in 
> Japanese is similar to case in some ways (including limited computer systems 
> using only one)
> 
> Full list of scripts in unicode that have case distinctions (based on analyzi
> ng character names): Adlam, Armenian, Cherokee, Coptic, Cyrillic, Deseret, Ge
> orgian, Glagolitic, Greek, Latin, Old Hungarian, Osage, and Warang Citi.

Thanks. I was being lazy. I understand old Latin, Greek &
Cyrillic scripts used only one case?  And that modern Georgian
does not distinguish cases though its alphabet has *several*
variants.  Osage is very new and Cherokee script was designed
in early 1800s (influenced by the europeans). So it seems
a) case sensitive scripts are mainly alphabets and 
b) lower case letters must've been a later addition. 
[I can see why case was never added to abugida languages like
 the Indian languages -- they already have a large number of
 glyphs and complex shapes to remember!]

Getting back to programming languages, I am not sure case
distinction really helps. Many of the earlier languages such
as Algol, PL/I, APL, Pascal, Fortran, Cobol, Lisp didn't have
it and I don't think it was solely due to an attempt to pack
more chars in a word. Capitalization can improve legibility in
written languages but the meaning of a word often doesn't
change in spite of case change. In modern PLs the meaning can
be entirely different, and even the category (DO vs do) and I
am not sure that increases legibility. Not to mention the
camelCaseHorror. Much prefer hyphenated-words (and use of
space before the negative sign when needed).


  parent reply	other threads:[~2018-04-06  5:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 21:03 Norman Wilson
2018-04-05 21:23 ` Clem Cole
2018-04-05 21:38   ` Bakul Shah
2018-04-06  2:03     ` Random832
2018-04-06  4:27       ` Warner Losh
2018-04-06  4:31         ` Jon Steinhart
2018-04-06  4:58         ` Steve Nickolas
2018-04-06  5:02           ` Jon Steinhart
2018-04-06  4:29       ` Steve Johnson
2018-04-06  5:57       ` Bakul Shah [this message]
2018-04-06 21:52         ` Peter Jeremy
2018-04-05 22:46   ` Arthur Krewat
2018-04-05 23:23   ` Paul Winalski
2018-04-05 23:33     ` Arthur Krewat
2018-04-06  0:05       ` Toby Thain
2018-04-06  4:51 ` Dave Horsfall
2018-04-06 15:00 ` Tony Finch
2018-04-07 20:41 ` Paul Winalski
  -- strict thread matches above, loose matches on Subject: below --
2018-04-06 22:33 Doug McIlroy
2018-04-07  1:01 ` Paul Winalski
2018-04-07  1:09   ` Larry McVoy
2018-03-23 18:27 [TUHS] long lived programs (was Re: RIP John Backus Bakul Shah
2018-03-23 20:50 ` [TUHS] long lived programs Steve Johnson
2018-03-23 21:07   ` Clem Cole
2018-03-23 15:51 Ron Natalie
2018-03-23 15:57 ` Clem Cole
2018-03-23 16:25   ` Lars Brinkhoff
2018-03-23 16:59     ` Lawrence Stewart
2018-03-23 17:31       ` Steve Nickolas
2018-03-23 16:32   ` Ron Natalie

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=20180406055756.A6927156E510@mail.bitblocks.com \
    --to=bakul@bitblocks.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).