From: Andrew STUBBS <andrew.stubbs@st.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: $argc variable
Date: Wed, 09 Nov 2005 11:15:00 -0000 [thread overview]
Message-ID: <4371D9A6.40109@st.com> (raw)
In-Reply-To: <u7jbisp6n.fsf@gnu.org>
Eli Zaretskii wrote:
> Btw, Andrew, why do you post patches to gdb@sources.redhat.com, rather
> than to gdb-patches@ ? The latter is the right place.
I post patches to gdb-patches@ and other messages to gdb@ which, in this
case, has a patch as a follow up. Should I switch list as soon as I have
a patch? That seems a little disconnected to me, but I see your point. I
originally posted the new options I had to gdb@ because I thought they
might be a little more controversial - I also called them RFC.
>>In the documentation I changed a '@var' to '@code' because @var makes it
>>upper case in the info and I thought that misleading.
>
>
> Upper case is not the problem: makeinfo produces an uppercase word
> from @var since time immemoriam, so anyone who's used to read Info
> manuals is already used to that.
I would respectfully suggest that manuals should be written for those
that do NOT know what they are doing. However, as you say, using
upper-case for non-literal text is fine and I understand that and if
users try to type it then there are bigger problems than case.
> The problem here is that it's simply wrong to use @var in this case,
> because $arg0 etc. are literal strings, to be used verbatim in the
> actual script, not placeholders that stand for something else. So
> your change is correct, although for the wrong reasons. ;-)
Well, I would have been happy with the wrong mark-up if the end
type-face had been right - it just depends on your point of view ;)
>>-via @var{$arg0@dots{}$arg9}. A trivial example:
>
>
> However, there _is_ something wrong here: the $ part should be outside
> @var, since it's a literal character:
>
> via @code{$@var{arg0}@dots{}$@var{arg9}}.
Err, haven't you just put back the @var, and therefore upper case, that
we just agreed shouldn't be there?
>>+via @code{$arg0@dots{}$arg9}. A trivial example:
>>
>> @smallexample
>> define adder
>> print $arg0 + $arg1 + $arg2
>>+end
>> @end smallexample
>
>
> In the example, I would suggest to use something other than arg0 etc.,
> to avoid confusion with arg0..arg9 as placeholders in the paragraph
> where you wanted to remove @var.
But this is an example of how to use $arg0 ?!?!? Also, it isn't my
example, I only added the 'end'.
>
>
>>+@kindex $argc
>
>
> I'd replace this with "@cindex arguments for user-defined function".
Replace or augment? I considered adding a kindex for $arg0...$arg9.
I agree that a concept should be added, but how about:
@cindex user-defined functions, argument passing
Just a thought.
>
> Other than that, the documentation patch is okay with me. Thanks.
Great, I'll wait for judgement on the code then.
Thanks
Andrew Stubbs
next prev parent reply other threads:[~2005-11-09 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 13:11 Andrew STUBBS
2005-11-03 19:51 ` Dan Nicolaescu
2005-11-07 0:18 ` Daniel Jacobowitz
2005-11-07 11:12 ` Andrew STUBBS
2005-11-07 13:35 ` Daniel Jacobowitz
2005-11-08 13:05 ` Andrew STUBBS
2005-11-08 23:19 ` Eli Zaretskii
2005-11-09 11:15 ` Andrew STUBBS [this message]
2005-11-09 19:19 ` Eli Zaretskii
2005-11-10 10:11 ` Andrew STUBBS
2005-11-13 17:35 ` Daniel Jacobowitz
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=4371D9A6.40109@st.com \
--to=andrew.stubbs@st.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.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.
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).