Re: gdb-ui.el assumes images support

[storm@cua.dk (Kim F. Storm)]

Kevin Rodgers <ihs_4664@yahoo.com> writes:

> Kim F. Storm wrote:
>  > Nick Roberts <nickrob@snap.net.nz> writes:
>  >>I added the last require after Gerd Moellmann included the others. My
>  >>understanding now is that a file only requires another, at compilation,
>  >>if it uses a macro defined in that other file.
>  >
>  > It may also require another file simply to avoid warnings for using
>  > undefined functions that are defined in that file.
>  >
>  > How else would you avoid such warnings?
>
> With (require 'feature) at the top level, since it is needed at runtime.


file a.el has this:
 (require 'b)
 ;;;#autoload
 (defun a-fun1 ()
   (b-fun))
 (defun a-fun2 ()
   t)
 (provide 'a)

file b.el has this:
 (defun b-fun ()
    (a-fun2))
 (provide 'b)

Assuming that b is never used directly, this works fine.


Now, when you byte-compile b.el, you get warning for a-fun2.

So according to your advise, we add
  (require 'a)
to b.el, and compile again with this result:

b.el:1:2:Error: Recursive `require' for feature `a'


What if

(defun a-fun2)

would be a dummy defun for the byte-compiler just like

(defvar a-var)

?


--
Kim F. Storm <storm@cua.dk> http://www.cua.dk