unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: sds@gnu.org
Cc: 30035@debbugs.gnu.org
Subject: bug#30035: 27.0.50; stream of messages about ‘semantic-flex’
Date: Tue, 09 Jan 2018 13:57:27 -0500	[thread overview]
Message-ID: <7ushbe3lns.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <vy1siy27wv.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 09 Jan 2018 13:39:44 -0500")


Anyway, I guess the following works around it. AFAICS, this code is
unchanged since Cedet was added to Emacs.

commit 34b41e3 (HEAD, origin/emacs-26, emacs-26)
Date:   Tue Jan 9 13:54:11 2018 -0500

    Quieten semantic normal usage
    
    * lisp/cedet/semantic/lex.el (semantic-flex): Mark obsolete at
    compile time in the normal way, not at run-time.  (Bug#30035)

diff --git a/lisp/cedet/semantic/lex.el b/lisp/cedet/semantic/lex.el
index 9a35dd8..3a8b0c7 100644
--- a/lisp/cedet/semantic/lex.el
+++ b/lisp/cedet/semantic/lex.el
@@ -471,6 +471,7 @@ semantic-lex-types
 ;;; Lexical Analyzer framework settings
 ;;
 
+;; FIXME change to non-obsolete default.
 (defvar semantic-lex-analyzer 'semantic-flex
   "The lexical analyzer used for a given buffer.
 See `semantic-lex' for documentation.
@@ -1857,7 +1858,7 @@ semantic-flex
 scanning, use `narrow-to-region'.
 The last argument, LENGTH specifies that `semantic-flex' should only
 return LENGTH tokens."
-  (message "`semantic-flex' is an obsolete function.  Use `define-lex' to create lexers.")
+  (declare (obsolete define-lex "23.2"))
   (if (not semantic-flex-keywords-obarray)
       (setq semantic-flex-keywords-obarray [ nil ]))
   (let ((ts nil)





  reply	other threads:[~2018-01-09 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 23:04 bug#30035: 27.0.50; stream of messages about ‘semantic-flex’ Sam Steingold
2018-01-09 18:39 ` Glenn Morris
2018-01-09 18:57   ` Glenn Morris [this message]
2018-01-09 19:15     ` Sam Steingold
2018-01-09 19:11   ` Sam Steingold
2020-10-27  1:18 ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7ushbe3lns.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=30035@debbugs.gnu.org \
    --cc=sds@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).