Re: bizarre byte-compile issue, possibly due to EIEIO

[Ted Zlatanov <tzz@lifelogs.com>]

On Fri, 01 Apr 2011 15:29:38 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> In other words, the registry.elc file is breaking the tests.  I can't
TZ> figure out what's wrong, but it seems EIEIO-related.  If I try to
TZ> edebug, that evaluates the problematic methods (e.g. `registry-lookup')
TZ> and then they don't exhibit the problem.

TZ> Using "(eval-when-compile (require 'registry))" instead of 
TZ> "(require 'registry)" doesn't help.  All the registry.el ERT tests pass.

(CC to ding mailing list; see prior messages on emacs-devel for context)

I've been able to work around it with:

(let ((load-suffixes '(".el")))
  (require 'registry))

in gnus-registry.el, but that makes the registry.el functionality really
slow and generates this byte-compile warning:

In end of data:
gnus-registry.el:910:1:Warning: the following functions are not known to be
    defined: registry-db, eieio-persistent-read, registry-size,
    registry-prune, eieio-persistent-save, registry-delete, registry-insert,
    registry-lookup-secondary-value, registry-lookup-secondary,
    registry-lookup

So I hope someone can help me out :)

Ted