From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: How to grok a complicated regex?
Date: Sat, 14 Mar 2015 04:58:04 +0100 [thread overview]
Message-ID: <874mpo1b8z.fsf@debian.uxu> (raw)
In-Reply-To: mailman.1984.1426288628.31049.help-gnu-emacs@gnu.org
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> Really? It's not /that/ difficult. You only need
> enough coffee (or tea, in my case), time and
> motivation. You don’t need a genius, or even IQ
> higher than, say, 90 or so. It's not really
> /difficult/. Intimidating, yes. Boring, possibly.
> Laborious (and mechanical), yes. But not
> /difficult/.
I mean to be able to read it like you read the code of
a programming language. What that takes is training
like everything else. Instead of deconstructing and
reconstructing complicated expressions like your
example I would recommend starting small - the most
basic building blocks over and over, then make them
gradually more complicated by combinations, then
combinations of combinations, ... It is the way a
machine would process it (only the other way around),
and it is the way a foreign natural language is
acquired (almost always). "IQ" is a joke and has
nothing to do with it unless IQ is defined by the
ability to understand regular expression, which by the
way I think isn't far away from how they test "IQ"
(which says alot).
> I disagree. I don’t think that such a translator
> would be a difficult one to write.
The compiler itself is perhaps not extremely difficult
tho certainly not trivial. But that's only the first
step. Then comes presenting it graphically, and make
an editor. To get that to actually work, polished, and
work better than just mastering and typing that form
of code - I'm not convinced.
> Wow, what a nice project for a bachelor’s thesis.
> Wait a minute. Ohboyohboyohboy. I have to put this
> in my faculty’s database of potential topics. Poor
> students... ;-)
That kind of autistic-genius, single-sided crazy stuff
doesn't appeal to me (in fact I think it is
destructive). I'm into execution and combinations -
i.e. not focusing on the technique per se. As an
example, when I did my Master in CS I had Lisp, C++,
zsh, and LaTeX (and more), everything working together
like glued to each other. I don't like one scientist
to do all the thinking, I like on engineer that does
everything and thinks at the same time.
--
underground experts united
next prev parent reply other threads:[~2015-03-14 3:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1979.1426282552.31049.help-gnu-emacs@gnu.org>
2015-03-13 22:46 ` How to grok a complicated regex? Emanuel Berg
2015-03-13 23:16 ` Marcin Borkowski
2015-03-14 0:12 ` Rasmus
2015-03-14 13:18 ` Stefan Monnier
[not found] ` <mailman.2003.1426339118.31049.help-gnu-emacs@gnu.org>
2015-03-15 4:31 ` Rusi
2015-03-22 2:29 ` Tom Tromey
2015-03-22 2:44 ` Rasmus
2015-03-14 5:14 ` Yuri Khan
2015-03-14 7:03 ` Drew Adams
[not found] ` <mailman.1984.1426288628.31049.help-gnu-emacs@gnu.org>
2015-03-14 3:58 ` Emanuel Berg [this message]
2015-03-14 4:44 ` Emanuel Berg
2015-03-14 4:58 ` Emanuel Berg
2015-03-14 8:43 ` Thien-Thi Nguyen
[not found] ` <mailman.1997.1426324089.31049.help-gnu-emacs@gnu.org>
2015-03-20 1:05 ` Emanuel Berg
2015-03-18 16:40 ` Alan Mackenzie
2015-03-19 8:15 ` Tassilo Horn
2015-04-25 4:23 ` Rusi
2015-04-27 13:26 ` Julien Cubizolles
2015-03-14 8:16 martin rudalics
-- strict thread matches above, loose matches on Subject: below --
2015-03-13 21:35 Marcin Borkowski
2015-03-13 21:45 ` Marcin Borkowski
2015-03-13 21:47 ` Alexis
2015-03-13 21:57 ` Marcin Borkowski
2015-03-23 12:18 ` Vaidheeswaran C
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=874mpo1b8z.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).