Computer Old Farts Forum
 help / color / mirror / Atom feed
From: cym224 at gmail.com (Nemo Nusquam)
Subject: [COFF] What languges would you like to learn?
Date: Fri, 27 Dec 2019 12:46:28 -0500	[thread overview]
Message-ID: <2edaa4e4-f842-93c6-8c8b-9f89349863d7@gmail.com> (raw)
In-Reply-To: <20191225173101.GA13390@tau1.ceti.pl>

On 12/25/19 12:31, Tomasz Rola wrote (in part):
> On Mon, Dec 23, 2019 at 06:27:48PM -0500, Nemo Nusquam wrote:
>> A recent thread makes me wonder which languages would people like to
>> learn?  (I confess to trying, as Dave does, but time prevents
>> anything more that learing syntax and writing toy programmes.  One
>> must write something substantial -- not synonomous with large -- to
>> really learn a language.)
>>
>> Erlang, Smalltalk, Prolog, Haskell, and Scheme come to mind...
> I will swim upstream and say: if I had more free time, I would
> probably want to finish reading "The AWK Programming Language" by Aho,
> Kernighan snd Weinberger.
A former colleague wrote an assembler in AWK.  We had a contract to 
supply s/w for a chip still being developed.  The (binary -- no source) 
assembler supplied by the customer was not only buggy and slow, it 
core-dumped on reaching an unknown op-code and they changed op-codes on 
every iteration!

[...]
> But if you have not had experience with Scheme yet, try it out. LISPs
> in general are worth learning, IMHO. And much more practical than what
> a popular opinion says.
>
Indeed -- I have played with Racket on and off (especially as it builds 
on my Sparc box).

N.


  parent reply	other threads:[~2019-12-27 17:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 23:27 cym224
2019-12-24  9:54 ` thomas.paulsen
2019-12-24 16:28 ` toby
2019-12-24 16:35   ` lm
2019-12-24 17:50     ` 
2019-12-24 18:04       ` lm
2019-12-25  3:34     ` dave
2019-12-25 16:02     ` cym224
2019-12-25 17:05     ` thomas.paulsen
2019-12-24 20:27 ` dave
2019-12-25 17:31 ` rtomek
2019-12-25 19:13   ` athornton
2019-12-26  0:23     ` me
2019-12-26  1:54       ` wobblygong
2019-12-26  3:44         ` dave
2019-12-26  4:00           ` lm
2019-12-26  5:43             ` wobblygong
2019-12-26 11:49               ` tih
2019-12-26 15:33                 ` lm
2019-12-26 16:34                 ` thomas.paulsen
2019-12-26 16:53                   ` lm
2019-12-27  3:00                 ` dave
2019-12-27  7:02                   ` thomas.paulsen
2019-12-26 17:57               ` bakul
2019-12-26 21:28                 ` davida
2019-12-26 21:37                   ` lm
2019-12-26 21:57                     ` sauer
2019-12-26 22:13                     ` 
2019-12-27  3:41                     ` bakul
2019-12-27  4:00                       ` lm
2019-12-27  4:28                         ` bakul
2019-12-26 22:16                   ` imp
2019-12-27  3:41                   ` bakul
2019-12-26 15:43         ` dfawcus+lists-coff
2019-12-27 17:46   ` cym224 [this message]
2019-12-27 21:33     ` tih

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=2edaa4e4-f842-93c6-8c8b-9f89349863d7@gmail.com \
    --to=coff@minnie.tuhs.org \
    /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).