[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

unexpected byte-compiler behaviour

From: hector
Subject: unexpected byte-compiler behaviour
Date: Thu, 9 Mar 2017 18:46:14 +0100
User-agent: Mutt/1.5.20 (2009-06-14)


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:

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?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]