Re: byte-compile making erroneous *Compile Log*

[David Vanderschel <DJV5@Austin.RR.com>]

Drew Adams <drew.adams <at> oracle.com> writes:

DV wrote:
> > My initialization is a bit too large to try to narrow it down
> > by partial execution...
 
> No, it's not too large. What you need to do (unless someone here has
> a direct answer for your problem) is to look for the problem using
> _binary_ search.

Yes, I am familiar with binary search; and, in this case, it will be
my last resort.  My initialization file is over 3000 lines long, so
successive halving still takes a while to get down to something
specific.  Such binary search works well when the problem is an
execution bug, as the 'test' is very quick.  However, in this case,
testing whether the problem still exists at each stage is not at all
trivial.  That is why I am hoping that someone can help me come at
this problem with better insight - which I believe is possible for this
particular problem.

> ... (Alternatively, you can use  `eval-region'.)

Indeed.  That is, in fact, how I have normally done it.  
Too many times.  :(