From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Find the longest word in the word list file.
Date: Thu, 12 Aug 2021 11:52:35 +0800 [thread overview]
Message-ID: <CAGP6POLH8MHV-kzdqABG4o2nYfVACGgsNugTEjWjQiM-d9uY=Q@mail.gmail.com> (raw)
In-Reply-To: <87pmujxrbx.fsf@zoho.eu>
On Thu, Aug 12, 2021 at 11:41 AM Emanuel Berg via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> > C is a compiled language, which makes it not as convenient
> > as an interpreted language for real-time interactive use.
> > Awk, in its way, becomes an advanced secondary packaging
> > based on C and provides a convenient interface for users as
> > an interpreted (script) language, which is exactly its
> > purpose. Just as python, with which many underlying
> > processing mechanisms are hidden to normal users. Though the
> > similar situations also exist in lisp [...]
>
> One of which would be that Emacs is also written in C :)
Right. All Turing-complete languages are equivalent. But the core is
not how superior the language itself is, but how advanced, good, and
complete the ideas on which it was founded. From this point of view,
LISP is probably the most complete, superlative language, just as the
``Greenspun's tenth rule'' says [1]:
Any sufficiently complicated C or Fortran program contains an ad hoc,
informally-specified, bug-ridden, slow implementation of half of
Common Lisp.
[1] https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule
Best, Hongyi
next prev parent reply other threads:[~2021-08-12 3:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 23:14 Find the longest word in the word list file Hongyi Zhao
2021-08-11 1:51 ` [External] : " Drew Adams
2021-08-11 3:00 ` Hongyi Zhao
2021-08-11 6:46 ` tomas
2021-08-11 8:58 ` Hongyi Zhao
2021-08-11 10:03 ` tomas
2021-08-11 9:52 ` Arthur Miller
2021-08-11 10:06 ` tomas
2021-08-11 13:32 ` Hongyi Zhao
2021-08-11 13:58 ` Stephen Berman
2021-08-11 14:17 ` Hongyi Zhao
2021-08-11 14:27 ` Stephen Berman
2021-08-11 16:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 2:10 ` Hongyi Zhao
2021-08-12 2:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 3:13 ` Hongyi Zhao
2021-08-12 3:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 3:34 ` Hongyi Zhao
2021-08-12 3:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 3:52 ` Hongyi Zhao [this message]
2021-08-12 4:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 4:25 ` Hongyi Zhao
2021-08-12 4:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 4:53 ` Hongyi Zhao
2021-08-12 5:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 6:25 ` Hongyi Zhao
2021-08-12 6:46 ` Hongyi Zhao
2021-08-12 6:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 6:59 ` Hongyi Zhao
2021-08-12 2:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 14:47 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
2021-08-12 15:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 15:53 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
2021-08-12 16:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-12 16:24 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGP6POLH8MHV-kzdqABG4o2nYfVACGgsNugTEjWjQiM-d9uY=Q@mail.gmail.com' \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).