Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: $argc variable
Date: Tue, 15 Nov 2005 17:54:00 -0000	[thread overview]
Message-ID: <4379D57C.50208@st.com> (raw)
In-Reply-To: <20051115044045.GA12833@nevyn.them.org>

[-- Attachment #1: Type: text/plain, Size: 274 bytes --]

Daniel Jacobowitz wrote:
>>OK for the documentation patch.
> 
> 
> The code is fine too.

Thanks, commited.


> Should this go on the branch?  Should it go in NEWS?  My inclination is
> "both".

I have no objection to putting it in. How about the attached for NEWS?

Andrew

[-- Attachment #2: 6.4-news-2.patch --]
[-- Type: text/plain, Size: 700 bytes --]

2005-11-15  Andrew Stubbs  <andrew.stubbs@st.com>

	* NEWS (6.4): Mention $argc.

Index: src/gdb/NEWS
===================================================================
--- src.orig/gdb/NEWS	2005-11-15 12:09:47.000000000 +0000
+++ src/gdb/NEWS	2005-11-15 12:15:45.000000000 +0000
@@ -70,6 +70,12 @@ behavior.
 
 GDB now supports the not-quite-ieee VAX F and D floating point formats.
 
+* User-defined command support
+
+In addition to using $arg0..$arg9 for argument passing, it is now possible
+to use $argc to determine now many arguments have been passed. See the
+section on user-defined commands in the user manual for more information.
+
 *** Changes in GDB 6.3:
 
 * New command line option

  reply	other threads:[~2005-11-15 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <436A0BD2.5080505@st.com>
     [not found] ` <20051107001800.GF19200@nevyn.them.org>
     [not found]   ` <436F35E9.4070808@st.com>
     [not found]     ` <20051107133538.GA2331@nevyn.them.org>
     [not found]       ` <43709E94.4070004@st.com>
     [not found]         ` <u7jbisp6n.fsf@gnu.org>
     [not found]           ` <4371D9A6.40109@st.com>
     [not found]             ` <u3bm5sk6i.fsf@gnu.org>
     [not found]               ` <43731C16.2040203@st.com>
     [not found]                 ` <20051113173524.GC1945@nevyn.them.org>
2005-11-14 22:12                   ` Andrew STUBBS
2005-11-15 12:35                     ` Eli Zaretskii
2005-11-15 12:39                       ` Daniel Jacobowitz
2005-11-15 17:54                         ` Andrew STUBBS [this message]
2005-11-16  5:52                           ` Eli Zaretskii
2005-11-16 14:43                             ` Andrew STUBBS
2005-11-16 16:19                               ` Daniel Jacobowitz
2005-11-16  4:01                         ` 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=4379D57C.50208@st.com \
    --to=andrew.stubbs@st.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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