Re: strange byte compiler behavior

[Stefan Monnier]

> A deeper solution would be to get rid of the boundp test.

> I'm sure it was added for a reason -- there must have been lots of
> spurious warnings without that boundp test.  But nowadays we have done
> a lot to eliminate such warnings with defvars.  Perhaps now if we get
> rid of that boundp test the results would be ok.

> Does someone want to try it?

No need to try: the boundp test is still needed to catch the case of
a variable defined globally in all cases (e.g. in C code or in preloaded
packages) as well as for variables defined in packages that are
`require'd (or loaded transitively by some of the `require'd packages).


        Stefan