unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Davis Herring <herring@lanl.gov>
Cc: 34789@debbugs.gnu.org
Subject: bug#34789: Scan of regexp mistakes
Date: Mon, 11 Mar 2019 16:20:40 +0200	[thread overview]
Message-ID: <83d0mx5w7b.fsf@gnu.org> (raw)
In-Reply-To: <44d068d3-613c-be0c-b4c4-45fff79f53dc@lanl.gov> (message from Davis Herring on Fri, 8 Mar 2019 13:46:38 -0700)

> From: Davis Herring <herring@lanl.gov>
> Date: Fri, 8 Mar 2019 13:46:38 -0700
> 
> This style of code is rare, and will if anything become rarer still in 
> C++20, when code in a header file that uses a particular specialization 
> (e.g., std::vector<A>) can be put into a module that is compiled only 
> once.  Even if someone were doing this, mantemp.el could at most 
> generate the one indicated line in templates.cxx _after_ the very 
> similar line in foo.hxx was added in some other fashion.
> 
> Hope this helps clarify,

Thanks, it does.  I think we indeed should move this package into
obsolete/.





  reply	other threads:[~2019-03-11 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EDAEDDB6-5182-41F4-91CD-8B6FA3C57A31@acm.org>
     [not found] ` <3ef768c2-98d9-a42d-067a-4a5ffc945cf4@cs.ucla.edu>
     [not found]   ` <D3E6A383-1368-46F0-8D37-7C45FD322DDC@acm.org>
     [not found]     ` <e2c83a03-a6ba-5b44-b49e-d2c4da447213@cs.ucla.edu>
     [not found]       ` <1c44342f-01ab-1bc6-4b5c-3485a6f01fda@lanl.gov>
     [not found]         ` <61035fed-564a-8766-8982-0d05acea341c@cs.ucla.edu>
2019-03-08 20:46           ` bug#34789: Scan of regexp mistakes Davis Herring
2019-03-11 14:20             ` Eli Zaretskii [this message]
2019-03-08 19:16 bug#34789: mantemp.el should be obsoleted Paul Eggert
2019-06-13 12:13 ` bug#34789: Scan of regexp mistakes Stefan Kangas
2019-06-13 12:48   ` Eli Zaretskii
2019-06-13 13:42     ` Stefan Kangas
2019-06-22  9:09       ` Eli Zaretskii

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=83d0mx5w7b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34789@debbugs.gnu.org \
    --cc=herring@lanl.gov \
    /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).