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/.
next prev parent reply other threads:[~2019-03-11 14:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 18:01 Scan of regexp mistakes Mattias Engdegård
2019-03-05 2:04 ` Paul Eggert
2019-03-05 4:30 ` Clément Pit-Claudel
2019-03-05 15:06 ` Mattias Engdegård
2019-03-08 6:02 ` Stefan Monnier
2019-03-08 17:13 ` Paul Eggert
[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: " Davis Herring
2019-03-11 14:20 ` Eli Zaretskii [this message]
2019-03-09 12:36 ` Mattias Engdegård
2019-03-09 17:14 ` Paul Eggert
2019-03-09 13:09 ` Mattias Engdegård
2019-03-09 17:12 ` Paul Eggert
2019-03-09 20:16 ` Mattias Engdegård
-- strict thread matches above, loose matches on Subject: below --
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
* 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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.