Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, ukleinek@informatik.uni-freiburg.de,
	        jimb@codesourcery.com
Subject: Re: [rfa] Clarify remote protocol RLE example
Date: Sat, 03 Nov 2007 22:08:00 -0000	[thread overview]
Message-ID: <ur6j7q8zh.fsf@gnu.org> (raw)
In-Reply-To: <20071103191822.GA17820@caradoc.them.org> (message from Daniel 	Jacobowitz on Sat, 3 Nov 2007 15:18:22 -0400)

> Date: Sat, 3 Nov 2007 15:18:22 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org, ukleinek@informatik.uni-freiburg.de,
> 	Jim Blandy <jimb@codesourcery.com>
> 
> On Sat, Nov 03, 2007 at 09:01:21PM +0200, Eli Zaretskii wrote:
> >  Response @var{data} can be run-length encoded to save space.
> >  Run-length encoding replaces runs of identical characters with the
> >  character @samp{*} followed by a repeat count.
> 
> How about "with an initial character, the character @samp{*}, and a
> repeat count"?  With that, I quite like your version.

How about

 Run-length encoding replaces runs of identical characters with a
 @samp{*} followed by a repeat count.

?

> > This part I simply don't understand.  What does it mean ``should not
> > be used''? what should be done instead? break the string into several
> > smaller ones?
> 
> May not be used (they have special syntactical meaning in the
> protocol).  So you need to stop the RLE string one character earlier,

It strikes me that it would be easier and more clear to say that runs
of 7 and 8 characters should be sent as 6+1 and 6+2, respectively.


  reply	other threads:[~2007-11-03 22:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 16:20 Daniel Jacobowitz
2007-11-03 18:43 ` Eli Zaretskii
2007-11-03 19:02 ` Eli Zaretskii
2007-11-03 19:18   ` Daniel Jacobowitz
2007-11-03 22:08     ` Eli Zaretskii [this message]
2007-11-04  4:03       ` Eli Zaretskii
2007-12-16 20:33         ` Daniel Jacobowitz
2007-12-16 22:57           ` Eli Zaretskii
2007-12-16 23:01             ` Daniel Jacobowitz
2007-11-06 18:31     ` Jim Blandy
2007-11-07 19:33       ` Michael Snyder

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=ur6j7q8zh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.com \
    --cc=ukleinek@informatik.uni-freiburg.de \
    /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