>> Is there a need for vgdb to stick with 2 letters? I much would prefer "clg"
>> instead. Since years I use the alias clg='valgrind --tool=callgrind', and in
>> the callgrind sources I use the CLG_ prefix quite often.
>>
>
>I agree with Josef it would be best if we could drop the
>2-letter-acronym requirement. My preference would be to use the tool
>name instead (and not some form of abbreviation). That increases
>usability as it eliminates all confusion. I fail to see the value of
>having to use an abbreviated tool name in certain contexts. It's just
>one more thing to remember. And it's not clear to me what the value is
>in return.
The 2 letters is just a convention, we can use more letters.
The only "requirement" are:
* it should be non-ambiguous, i.e. it is better to have
a command for a certain tool to not be confused with a command
from another tool or with a standard core valgrind command.
So, the idea was that standard core commands are starting
with vg. while tool commands starts with their own unique
prefix (e.g. mc. ms. and the to be chosen for callgrind).
* It should not be to long to type: gdb monitor command
does not have completion for its arguments.
e.g. to get the v bits for 8 bytes at addr 0x1234
I prefer to type (gdb) mo mc.g 0x1234 8
than mo memcheck.g 0x1234 8
mo is extended by gdb as monitor
the .g is sufficient for gdbserver memcheck code
to disambiguate if there is only one memcheck command
starting with the same letter which I have ensured
up to now for most(all?) command and most(all?) of their
arguments.
The main reason to have short prefix is that that such commands
are typed often, and the prefix must be typed in full.
So, for callgrind, we can use clg. as suggested by Josef
or use cl or ...
I would not like long commands (and/or long arguments that are
ambiguous unless you type many of the leading characters).
But if I am in the very few that likes short things to type, I can
survive with long prefixes and start typing
list-files-in-directories --output-long-format-with-dates :).
(of course, I like a lot the gnu convention to have both short and
long option names, but that looks an overkill for gdbsrv in valgrind).
Philippe
____
This message and any files transmitted with it are legally privileged and
intended for the sole use of the individual(s) or entity to whom they are
addressed. If you are not the intended recipient, please notify the sender by
reply and delete the message and any attachments from your system. Any
unauthorised use or disclosure of the content of this message is strictly
prohibited and may be unlawful.
Nothing in this e-mail message amounts to a contractual or legal commitment on
the part of EUROCONTROL, unless it is confirmed by appropriately signed hard
copy.
Any views expressed in this message are those of the sender.
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
