From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Why Pascal is Not My Favorite Programming Language Unearthed!
Date: Fri, 01 Sep 2017 12:19:27 +1200 (NZST) [thread overview]
Message-ID: <1504225167.59a8a78fdd078@www.paradise.net.nz> (raw)
In-Reply-To: <201708311749.v7VHnTH1029745@tahoe.cs.Dartmouth.EDU>
No, such a Pascal would've been more of an Ada if developed like C++; more of an Oberon or Modula-2
if minimalist.
I (officially) learned programming with Turbo Pascal. However, I'd already read both Comer's and
Tanenbaum's books on operating system design and implementation, and likewise Brinch Hansen's
book on Solo and Concurrent Pascal.
It didn't take long to work out that you could put together larger projects even with Turbo C than you
could with Turbo Pascal, and the Turbo Pascal efforts towards handling large projects were a fudge.
I liked Oberon - I think Wirth came closer to the minimalism of C with Oberon.
Wesley Parish
Quoting Doug McIlroy <doug at cs.dartmouth.edu>:
> > If Unix was written in Pascal I would've happily continued using
> Pascal!
>
> Amusing in the context of Brian's piece, which essentially says if Unix
> could have been written in Pascal, then Pascal wouldn't have been
> Pascal.
>
> doug\
>
"I have supposed that he who buys a Method means to learn it." - Ferdinand Sor,
Method for Guitar
"A verbal contract isn't worth the paper it's written on." -- Samuel Goldwyn
next prev parent reply other threads:[~2017-09-01 0:19 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 [this message]
2017-09-01 0:47 ` Larry McVoy
2017-09-01 2:45 ` Ian Zimmerman
2017-09-01 3:53 ` Warner Losh
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=1504225167.59a8a78fdd078@www.paradise.net.nz \
--to=wes.parish@paradise.net.nz \
/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).