compiler warnings

* compiler warnings
@ 2007-12-29 22:23 Adam Spiers
  2008-01-02 22:17 ` Carsten Dominik
  0 siblings, 1 reply; 3+ messages in thread
From: Adam Spiers @ 2007-12-29 22:23 UTC (permalink / raw)
  To: org-mode mailing list

Does anyone else get a lot of warnings during compile of org.el?

In org-remember-insinuate:
org.el:13175:9:Warning: assignment to free variable
    `remember-annotation-functions'
org.el:13176:9:Warning: assignment to free variable
    `remember-handler-functions'

In end of data:
org.el:27707:1:Warning: the following functions might not be defined at
    runtime: gnus-summary-last-subject, rmail-show-message,
    calendar-forward-day, parse-time-string, calendar-goto-date,
    calendar-goto-today, calendar-iso-date-string,
    calendar-julian-date-string, calendar-astro-date-string,
    calendar-hebrew-date-string, calendar-islamic-date-string,
    calendar-french-date-string, calendar-bahai-date-string,
    calendar-mayan-date-string, calendar-coptic-date-string,
    calendar-ethiopic-date-string, calendar-persian-date-string,
    calendar-chinese-date-string
org.el:27707:1:Warning: the following functions are not known to be defined:
    add-local-hook, table--at-cell-p, bbdb-record-name, bbdb-current-record,
    bbdb-record-getprop, vm-summarize, vm-follow-summary-cursor,
    vm-select-folder-buffer, vm-su-subject, vm-get-header-contents,
    vm-su-message-id, wl-summary-message-number, elmo-message-field,
    elmo-msgdb-overview-get-entity, wl-summary-buffer-msgdb,
    wl-summary-line-from, elmo-message-entity-field, wl-summary-line-subject,
    rmail-narrow-to-non-pruned-header, gnus-article-show-summary,
    dired-get-filename, bbdb-name, bbdb-company, bbdb, vm-isearch-update,
    vm-isearch-narrow, vm-beginning-of-message, elmo-folder-exists-p,
    wl-folder-get-elmo-folder, wl-summary-goto-folder-subr,
    wl-summary-jump-to-msg-by-message-id, wl-summary-redisplay,
    rmail-what-message, mh-index-previous-folder, mh-get-msg-num,
    mh-show-buffer-message-number, mh-display-msg, mh-header-display,
    mh-show-header-display, mh-get-header-field, mh-show, mh-show-show,
    mh-find-path, mh-visit-folder, mh-normalize-folder-name, mh-search-choose,
    mh-search, mh-show-msg, bibtex-generate-autokey,
    bibtex-beginning-of-entry, bibtex-parse-entry, bibtex-url, remember,
    remember-buffer-desc, add-to-diary-list, cdlatex-tab,
    org-export-latex-cleaned-string, speedbar-line-directory

It seems pretty clear that these are all due to references on external
packages which are not automatically loaded at start-up, and hence are
(mostly?) harmless - but should we try to clear them up anyway?  If
so, what would the best way be?  `autoload' or `eval-when-compile' are
presumably better than just a bunch of stub defun and defvar
statements, but maybe there's a better way?

^ permalink raw reply	[flat|nested] 3+ messages in thread