From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: use Elisp to improve your Elisp - some code issues
Date: Thu, 06 Aug 2015 01:40:34 +0200 [thread overview]
Message-ID: <871tfhtibx.fsf@nl106-137-147.student.uu.se> (raw)
In-Reply-To: 87pp353doq.fsf@robertthorpeconsulting.com
Robert Thorpe <rt@robertthorpeconsulting.com> writes:
> I agree with Pascal & Marcin.
>
> Why not use the "read" function to read in the code
> of the file. Then you have everything as a tree.
> You can use car and cdr to walk the tree and find
> the relevant function calls. Then you're in the
> right place in the Chomsky heirachy.
>
> Suppose "a" and "b" are expressions rather than
> variables. Suppose that the two instances of "a"
> have different whitespace and comments between them.
> In that case they can't be differentiated by regex.
> Regex can't count parenthesis either.
>
> Another possibility is editing the byte-compiler
> source to provide more warnings.
If you read the code, you find the two most important
functions are `regexp-hits-find-hit' and
`search-regexp-in-files'. regexp means regexps!
That there are examples - which work - applied on Lisp
files don't change that.
Now, it doesn't say *one word* about re-parsing or
otherwise analyzing the code with respect imbecile,
ten million times accursed computer science theory.
If you want to do that - just do it! See if I will
come and have 42 degrees of expedition fever and
purposely misunderstand and be all negativistic.
Of course, I will not - and why do you think that is?
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-08-05 23:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7671.1438302261.904.help-gnu-emacs@gnu.org>
2015-07-31 2:39 ` use Elisp to improve your Elisp - some code issues Pascal J. Bourguignon
2015-08-01 4:09 ` Emanuel Berg
[not found] ` <mailman.7712.1438402251.904.help-gnu-emacs@gnu.org>
2015-08-01 8:54 ` Pascal J. Bourguignon
2015-08-01 12:41 ` Emanuel Berg
[not found] ` <mailman.7727.1438432975.904.help-gnu-emacs@gnu.org>
2015-08-01 15:59 ` Pascal J. Bourguignon
2015-08-02 0:06 ` Emanuel Berg
2015-08-03 1:23 ` Ian Zimmerman
[not found] ` <mailman.7751.1438474104.904.help-gnu-emacs@gnu.org>
2015-08-02 0:44 ` Pascal J. Bourguignon
2015-08-02 1:29 ` Emanuel Berg
2015-08-02 15:36 ` Robert Thorpe
2015-08-02 16:44 ` Pascal J. Bourguignon
2015-08-05 23:40 ` Emanuel Berg [this message]
2015-08-06 0:59 ` John Mastro
[not found] ` <mailman.7758.1438529790.904.help-gnu-emacs@gnu.org>
2015-08-02 16:25 ` Rusi
2015-08-01 16:13 ` Michael Heerdegen
2015-07-31 20:24 ` Sam Halliday
2015-08-01 4:20 ` Emanuel Berg
2015-08-01 6:26 ` Marcin Borkowski
[not found] ` <mailman.7714.1438410426.904.help-gnu-emacs@gnu.org>
2015-08-01 8:57 ` Pascal J. Bourguignon
2015-08-01 12:48 ` Emanuel Berg
2015-08-01 13:05 ` Marcin Borkowski
2015-08-01 13:14 ` Emanuel Berg
2015-08-01 13:21 ` Emanuel Berg
[not found] ` <mailman.7713.1438402953.904.help-gnu-emacs@gnu.org>
2015-08-02 10:42 ` Sam Halliday
2015-08-05 23:21 ` Emanuel Berg
2015-07-31 0:22 Emanuel Berg
2015-07-31 2:30 ` Marcin Borkowski
2015-07-31 7:42 ` Stefan Monnier
2015-07-31 12:11 ` Navy Cheng
2015-08-03 7:56 ` Tassilo Horn
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=871tfhtibx.fsf@nl106-137-147.student.uu.se \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.