From: Eli Zaretskii <eliz@gnu.org>
To: fabrice nicol <fabrnicol@gmail.com>
Cc: 47408@debbugs.gnu.org
Subject: bug#47408: [PATCH] Etags support for Mercury -- fix explicit tags for existentially-quantified procedures
Date: Mon, 14 Jun 2021 20:42:37 +0300 [thread overview]
Message-ID: <83eed45omq.fsf@gnu.org> (raw)
In-Reply-To: <46a10b9f-91d7-63c4-1513-0af4743e0940@gmail.com> (message from fabrice nicol on Mon, 14 Jun 2021 19:10:53 +0200)
> Cc: 47408@debbugs.gnu.org, pot@gnu.org
> From: fabrice nicol <fabrnicol@gmail.com>
> Date: Mon, 14 Jun 2021 19:10:53 +0200
>
> If you take a look at other languages that implement explicit tags (like
> Fortran) you will see that there are buffers coming in to avoid having
> 'name' and 'linestart' (1st and 4th arguments to 'make_tag') share a
> same string pointer (here 's').
>
> This is explained in the header comment to 'make_tag':
>
> " 2. LINESTART contains name as either a rightmost, or rightmost but
> * one character, substring;"
This is just a condition for generating "implicitly named" tags.
There's nothing wrong with having explicitly named tags, if there are
good reasons for that.
> When I applied you suggestion and tested, the TAGS base was as expected
> accordingly: wrong.
"Wrong" in what sense? Can you show an example of such a wrong tag?
And how does Mercury differ from Prolog in this sense? prolog_pr
doesn't allocate new strings before calling make_tag.
Thanks.
next prev parent reply other threads:[~2021-06-14 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12421.1623412982.2554.bug-gnu-emacs@gnu.org>
2021-06-14 15:10 ` bug#47408: [PATCH] Etags support for Mercury -- fix explicit tags for existentially-quantified procedures fabrice nicol
2021-06-14 16:04 ` Eli Zaretskii
2021-06-14 17:10 ` fabrice nicol
2021-06-14 17:42 ` Eli Zaretskii [this message]
2021-06-14 18:52 ` fabrice nicol
2021-06-17 10:50 ` Eli Zaretskii
2021-06-17 11:19 ` Fabrice Nicol
2021-06-17 11:42 ` Eli Zaretskii
2021-06-17 18:36 ` fabrice nicol
2021-06-18 11:29 ` Eli Zaretskii
2021-06-18 11:54 ` Francesco Potortì
2021-06-18 12:33 ` Eli Zaretskii
2021-06-18 13:53 ` fabrice nicol
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=83eed45omq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47408@debbugs.gnu.org \
--cc=fabrnicol@gmail.com \
/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.