Re: [PATCH] An implementation of pipe to make I/O communication between gdb and shell.

[Abhijit Halder <abhijit.k.halder@gmail.com>]

On Fri, Aug 5, 2011 at 3:54 PM, Abhijit Halder
<abhijit.k.halder@gmail.com> wrote:
> On Fri, Aug 5, 2011 at 3:26 PM, Pedro Alves <pedro@codesourcery.com> wrote:
>> On Friday 05 August 2011 10:41:09, Abhijit Halder wrote:
>>> I am not sure whether this restriction is meaningful. Ideally we
>>> should not support any alpha-numeric character as a delimiter just
>>> because of readability purpose. e.g.
>>> (gdb) pipe dthread apply all btdvim -
>>> Here d is delimiter. I don't think the above one is acceptable. Please
>>> suggest me if we simply can put a restriction of not using any
>>> alpha-numeric character as delimiter and that will do.
>>> Secondly I believe by FOO you meant a single character and not a
>>> string. Between delimiter and command there is no restriction of
>>> having any white-space.
>>
>> Speaking for myself, when I wrote PIPE and FOO before, I really
>> meant a string (with no whitespace), not a single character.
>>
>> In your example above:
>>
>>  (gdb) pipe dthread apply all btdvim -
>>
>> the delimiter would be `dthread'.  I see no reason to
>> require it to be a single character.
>>
> Just a thought. Can't using a single character make the life simple?
Just a bit clarification on my statement. If we use some string as
delimiter, space has be used again as a delimiter between between two
tokens. If someone use simply a single character as a delimiter, he
has to provide a space between delimiters and commands.
(gdb) pipe |
> That will surely reduce the options for delimiter. But as you said,
> like sed this can be used.
>> --
>> Pedro Alves
>>
>