I've added in the declare-functions, so the new warnings should be gone.
I'm using emacs 22, where declare-function is a no-op, so I still get the
warnings, but the calls are there.

Troy

On Thu, Apr 1, 2010 at 2:03 AM, Len Trigg
<lenbok+mlj...@gmail.com<lenbok%2bmlj...@gmail.com>
> wrote:

> You can nicely make the warnings go away by using declare-function
> (which we have started to do in several places).
>
> http://www.gnu.org/software/emacs/elisp/html_node/Declaring-Functions.html
>
> Cheers,
> Len.
>
> On Thu, Apr 1, 2010 at 4:05 PM, Troy Daniels
> <udalrich.scher...@gmail.com> wrote:
> > I'm cleaning up those warnings, but there's one I'm not certain how to
> > handle.
> >
> > In end of data:
> > jde-db.el:2018:1:Warning: the following functions are not known to be
> > defined:
> >     jde-find-class-source-file, jde-build-classpath, jde-normalize-path,
> >     jde-jdb-get-jdb
> >
> > has now become
> >
> > In end of data:
> > jde-db.el:2017:1:Warning: the following functions are not known to be
> > defined:
> >     jde-find-class-source-file, jde-build-classpath, jde-normalize-path,
> >     jde-jdb-get-jdb, jde-expand-wildcards-and-normalize
> >
> > The new function is defined in the jde.el, the same file as
> > jde-normalize-path, and that seems to be the logical place to define it
> (as
> > it is related to jde-normalize-path).  Is there a standard way to make
> > "forward declarations" for the compiler?  Since there is already a
> warning
> > for jde-normalize-path, it seems that there probably is not a way.  If
> so,
> > is it acceptable to add this warning to the build?
> >
> > There is a similar warning in jde-javadoc-gen.el
> >
> > I've attached the updated patch in case these warnings are acceptable.
> >
> > Troy
> >
> >
> >> Cheers,
> >> Len.
> >
> >
>

Attachment: jdee-wildcards.patch
Description: Binary data

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
jdee-devel mailing list
jdee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jdee-devel

Reply via email to