Re: [RFC 11/12] entryval: "@entry" in input expressions

[Eli Zaretskii <eliz@gnu.org>]

> Date: Mon, 18 Jul 2011 22:24:10 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> it would be good if one can also:
> (gdb) print refparam@entry
> $1 = 5
> 
> I am not sure if the entry values should be really indicated by the @entry
> suffix.  Also as @entry values are not not_lval it may be enough to display
> them either by `bt full' and `info args' or even by some new command:
> (gdb) entryval param
> #1 = 5

Again, why not just

 (gdb) print refparam

?

> +If you append @code{@@entry} string to a function parameter name you get its
                 ^^^^^^^^^^^^^^
This should be @kbd{@@entry}, since it's something the user should
type at the keyboard.

>                  Entry values are available only since @value{NGCC}
> +version 4.7.

Suggest not to talk about GCC explicitly, but about something more
vague, like "only with some compilers".  You yourself said in this
thread that Ubuntu back-ported the patch to GCC 4.6.x, so saying
"since 4.7" would be misleading.

> +Breakpoint 1, d (i=30) at gdb.base/entry-value.c:29
> +29	  i++;
> +(gdb) next
> +30	  e (i);
> +(gdb) print i
> +$1 = 31
> +(gdb) print i@@entry
> +$2 = 30

Which doesn't add any information beyond what is already shown in the
first line.  What's the point?

Thanks.