Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Richard Henderson <rth@redhat.com>,
	gdb-patches@sources.redhat.com,
	"J. Johnston" <jjohnstn@redhat.com>
Subject: Re: [commit] Order parameters "rw", not "wr"
Date: Thu, 13 Nov 2003 15:40:00 -0000	[thread overview]
Message-ID: <20031113154027.GA12374@nevyn.them.org> (raw)
In-Reply-To: <3FB3A2E8.8050003@redhat.com>

On Thu, Nov 13, 2003 at 10:27:36AM -0500, Andrew Cagney wrote:
> >On Mon, Nov 10, 2003 at 04:20:13PM -0500, Andrew Cagney wrote:
> >
> >>The attached patch re-orders the xfer_partial interface so its 
> >>read/write buffers are ordered read/write (i.e., sanely).
> >
> >
> >Eh??  The entire standard C library uses write/read.  I don't
> >see what's so unusual or non-canonical about it...
> 
> O_RDWR Open for reading and writing
> S_IRWXU 00700 user (file owner) has read, write and execute permission
> drwxr-xr-x    2 cagney   cagney       8192 Nov 11 13:52 bin

Those aren't arguments, just a couple occurances of "read, write", so I
fail to see the connection.  Consider memcpy, strcat, fgets, sprintf. 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-11-13 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 21:20 Andrew Cagney
2003-11-12  2:18 ` Richard Henderson
2003-11-13 15:27   ` Andrew Cagney
2003-11-13 15:40     ` Daniel Jacobowitz [this message]
2003-11-13 16:36       ` Andrew Cagney
2003-11-13 16:39         ` Daniel Jacobowitz
2003-11-13 17:46           ` Andrew Cagney
2003-11-13 18:01             ` Andrew Cagney
2003-11-13 19:19               ` Daniel Jacobowitz

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=20031113154027.GA12374@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.com \
    --cc=rth@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