public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@adacore.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, ADA, DOC] PR 15479: Crossrefs and links
Date: Sun, 16 Mar 2008 18:32:00 -0000	[thread overview]
Message-ID: <20080316182210.GA37514@adacore.com> (raw)
In-Reply-To: <20080315135145.GG17579@ins.uni-bonn.de>

> Right now, there is one crucial limitation to this patch: references
> from the Reference Manual to the User Manual have the name gnat_ugn_unw
> hard-coded; so it amounts to the wrong thing on VMS, I suppose.  Lifting
> this limitation would require some preprocessing of gnat_rm.texi similar
> to how gnat_ugn.texi is preprocessed, because texinfo doesn't like
> @value's in the info-file-name argument of cross-references.[1]
> Should I add that?

Hard coding the name is indeed not desirable and should be addressed before
doing this change.

> Smaller issues regarding this patch:
> 
> - gnat_rm.texi, node "Pragma Long_Float", refers to gnatlbr,
>   a node which exists in the VMS version of the User's Manual only.
>   I suppose this may be fixed along with above.

Sounds like a good idea.

> - gnat_ugn.texi, node "Ada tasks", refers to "tasking support"
>   inside GDB.  Should that link to the node "Threads" in gdb?

No, the ref is indeed to Ada tasks.

>   FWIW, my gdb does not understand the command "info tasks" at all,
>   which is explicitly documented in gnat_ugn.

That's indeed related. I do not know the state of the Ada specific
documentation in gdb, so this refers to GNAt additions that may not yet be
at the FSF, although will appear at some point if not already.

> OK for trunk and 4.3?

Not in the current form.

I'd suggest resubmitting a patch with the tricky parts left aside for now,
so that 90% of your changes can be OKed. You can then work on the
remaining 10% when you get a chance.

Arno

  reply	other threads:[~2008-03-16 18:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 14:12 Ralf Wildenhues
2008-03-16 18:32 ` Arnaud Charlet [this message]
2008-03-16 22:08   ` Ralf Wildenhues
2008-03-17  9:47     ` Arnaud Charlet
2008-03-17 20:56       ` Ralf Wildenhues
2008-03-18  9:05         ` Arnaud Charlet
2008-03-18 21:55           ` Ralf Wildenhues
2008-03-18 22:05             ` Arnaud Charlet
2008-03-18 22:27               ` Ralf Wildenhues
2008-03-19  8:44                 ` Arnaud Charlet
2008-03-20 19:58                   ` Ralf Wildenhues
2008-03-21 11:38                     ` Arnaud Charlet

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=20080316182210.GA37514@adacore.com \
    --to=charlet@adacore.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=gcc-patches@gcc.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.
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).