From: hector <hectorlahoz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: unexpected byte-compiler behaviour
Date: Thu, 9 Mar 2017 18:46:14 +0100 [thread overview]
Message-ID: <20170309174614.GA3572@workstation> (raw)
Hi.
I'm trying to compile a file and it's driving me crazy.
At some point of the file I'm reading unexpected messages:
lyqi.el:137:1:Warning: `(abbrev :initarg :abbrev)' is a malformed function
There's something weird going on here. So I write a nonsense function call
at top level:
(djghalkjhg)
The byte-compiler just skips this and keeps showing the first message.
When I cut the file at this point the compiler says what I expect:
tmp.el:136:1:Warning: the function `djghalkjhg' is not known to be defined.
How can this be?
This leads me to think that the parser is doing more than one pass since
a text after this point is affecting compilation at this point.
If this is true, what the heck is causing it to not report that
function "djghalkjhg" is not defined?
Any ideas?
next reply other threads:[~2017-03-09 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 17:46 hector [this message]
2017-03-09 18:18 ` unexpected byte-compiler behaviour John Mastro
2017-03-09 18:20 ` John Mastro
2017-03-09 19:17 ` hector
2017-03-09 19:25 ` hector
2017-03-09 21:55 ` John Mastro
2017-03-09 22:49 ` hector
2017-03-09 23:28 ` John Mastro
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=20170309174614.GA3572@workstation \
--to=hectorlahoz@gmail.com \
--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).