emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#15862: closed (aliases to macros at compile time)


From: GNU bug Tracking System
Subject: bug#15862: closed (aliases to macros at compile time)
Date: Mon, 04 May 2020 12:13:01 +0000

Your message dated Mon, 04 May 2020 14:12:25 +0200
with message-id <address@hidden>
and subject line Re: bug#15862: Status: aliases to macros at compile time
has caused the debbugs.gnu.org bug report #15862,
regarding aliases to macros at compile time
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
15862: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15862
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: aliases to macros at compile time Date: Mon, 11 Nov 2013 15:03:08 -0500 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Package: emacs
Version: 24.3
Severity: minor

[ From http://lists.gnu.org/archive/html/emacs-devel/2013-09/msg00354.html ]

(defvar foo-var 0)

(defmacro foo-mac ()
  '(setq foo-var (1+ foo-var)))

(define-obsolete-function-alias 'old-mac #'foo-mac "24.4")

(defun foo-fails ()
  (old-mac))

(defun foo-works ()
  (foo-mac))


Compile:
foo.el:13:4:Warning: the function `foo-mac' is not known to be defined.

Load compiled version:
(foo-fails) ; -> (invalid-function old-mac)


Also, neither version warns that old-mac is obsolete.

I see now that

(eval-and-compile
  (define-obsolete-function-alias 'old-mac #'foo-mac "24.4"))

works. So maybe that should happen automatically at top-level.



--- End Message ---
--- Begin Message --- Subject: Re: bug#15862: Status: aliases to macros at compile time Date: Mon, 04 May 2020 14:12:25 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
Lars Ingebrigtsen <address@hidden> writes:

> I don't get anything about invalid functions.  So has this been fixed,
> or am I misinterpreting what the invalid function issue is?

More information was requested, but none was given within 6 months, so
I'm closing this bug.

If this is still an issue, please reply to this email (use "Reply to
all" in your email client) and we can reopen the bug report.

Best regards,
Stefan Kangas


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]