The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Why Pascal is Not My Favorite Programming Language Unearthed!
Date: Thu, 31 Aug 2017 21:53:15 -0600	[thread overview]
Message-ID: <CANCZdfo4kpg8h85bU20iA_dg8KeSm=9zOjqpYj9B+H2mB+8nog@mail.gmail.com> (raw)
In-Reply-To: <20170901024548.khkx3y3ggkbylukt@matica.foolinux.mooo.com>

On Thu, Aug 31, 2017 at 8:45 PM, Ian Zimmerman <itz at very.loosely.org> wrote:

> On 2017-08-31 17:47, Larry McVoy wrote:
>
> >       IF (expr)
> >       BEGIN
> >               blah
> >               blah
> >               blah
> >       END
> >
> > I'm sorry but I'm with whoever it was that said { } are better than
> > BEGIN END.  Seems trivial but it's not to me.
>
> IMO, that's taking 1 part of a large coherent whole and judging by that.
> I am terrible with metaphors and similes, but maybe a bit like saying "I
> don't like the GPL because it restricts what I can do with my code."
>
> Here's another construct from C:
>
> for (i = n; i > 0; --i) {
>     blah();
> }
>
> In a language like Pascal (really Algol), that is
>
> FOR i = n TO 0 DO
>     Blah()
> DONE
>
> That's much closer typing-wise, isn't it?  That's because of the melding
> of the brackets with the control structure keywords.  But you can't do
> that _and_ have braces.
>

Today  I might agree with you because of the fancy IDEs coupled with the
huge screen size makes this a little easier to read.

When I learned, screen space was at a premium (24x80) so I had to make
every line count and pack in as much as I could. And any short cut to
typing also helped me write things faster, so I gravitated to C as soon as
it was available at an affordable price... It also was easier to do via
dialup at 1200 or 2400 baud.

But then again, I still write in 'C' because I find it easiest to grok
after 35 years of use... I'm also teaching python to my son and haven't
introduced C and compilers and makefiles. python just runs and the
indenting thing, though it offends my aesthetic, isn't a big deal with a
decent editor.

Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170831/a625f8e5/attachment.html>


  reply	other threads:[~2017-09-01  3:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 17:49 Doug McIlroy
2017-08-31 23:36 ` Bakul Shah
2017-09-01  0:19 ` Wesley Parish
2017-09-01  0:47   ` Larry McVoy
2017-09-01  2:45     ` Ian Zimmerman
2017-09-01  3:53       ` Warner Losh [this message]
2017-09-01  3:56         ` Larry McVoy
2017-09-01  4:45         ` Lyndon Nerenberg
2017-09-01 14:19           ` Steffen Nurpmeso

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='CANCZdfo4kpg8h85bU20iA_dg8KeSm=9zOjqpYj9B+H2mB+8nog@mail.gmail.com' \
    --to=imp@bsdimp.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).