From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: For text processing, which is more powerful, emacs or perl?
Date: Sun, 20 Dec 2020 11:03:08 +0800 [thread overview]
Message-ID: <CAGP6POJoHj3ei6Zao-_2OU8HvBMbDjD5pUG1ptOj9iYJ09S=4Q@mail.gmail.com> (raw)
In-Reply-To: <87tushbawm.fsf@zoho.eu>
On Sun, Dec 20, 2020 at 8:04 AM Emanuel Berg via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Jean Louis wrote:
>
> > CPAN and Perl are not obsolete, not at all
>
> Today most people will turn to Python instead of Perl for
> solving a general task. Development in Python is very fast and
> the code is to the untrained eye easier to read than Perl code
> which has a more cryptic and esoteric style.
Although with that said, it's an indisputable fact that the top 1
capability for text-based regex processing capability is still belongs
to Perl.
>
> But that doesn't mean Perl is obsolete and people will still
> use it for many years to come.
>
> For Emacs there should be many alternatives and packages that
> deal with Perl code. `perl-mode' is built-in (defined in
> perl-mode.el.gz), you get that when you open a .pl file.
>
> Interestingly, while Perl feels old, and Python pretty new,
> the difference is only 4 years: Perl is from 1987,
> Python 1991.
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
--
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Polytechnic Vocational and Technical University
NO. 552 North Gangtie Road, Xingtai, China
next prev parent reply other threads:[~2020-12-20 3:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 7:43 For text processing, which is more powerful, emacs or perl? Hongyi Zhao
2020-12-19 9:00 ` Jean Louis
2020-12-19 12:17 ` Hongyi Zhao
2020-12-19 12:25 ` Jean Louis
2020-12-20 0:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20 1:42 ` Hongyi Zhao
2020-12-20 3:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20 5:31 ` Jean Louis
2020-12-20 6:18 ` Hongyi Zhao
2020-12-20 6:52 ` Jean Louis
2020-12-20 7:49 ` Hongyi Zhao
2020-12-20 13:42 ` Jean Louis
2020-12-20 3:03 ` Hongyi Zhao [this message]
2020-12-20 3:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-08 16:42 ` Marcin Borkowski
2020-12-19 14:36 ` Harald Jörg
2020-12-20 4:38 ` Jean Louis
2020-12-19 16:01 ` Stefan Monnier
2020-12-20 5:23 ` Jean Louis
2020-12-20 6:17 ` Hongyi Zhao
2020-12-20 6:25 ` Jean Louis
2020-12-20 13:58 ` Stefan Monnier
2020-12-20 14:47 ` tomas
2020-12-20 9:01 ` tomas
2021-10-08 16:52 ` Marcin Borkowski
2021-10-09 1:42 ` Hongyi Zhao
2021-10-10 14:26 ` Emanuel Berg 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='CAGP6POJoHj3ei6Zao-_2OU8HvBMbDjD5pUG1ptOj9iYJ09S=4Q@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).