Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: some const char * trivia
Date: Tue, 03 Jun 2003 22:08:00 -0000	[thread overview]
Message-ID: <3EDD1C56.3020102@redhat.com> (raw)
In-Reply-To: <ro1znkyhnbx.fsf@jackfruit.Stanford.EDU>

> On Tue, 03 Jun 2003 16:40:45 -0400, Andrew Cagney <ac131313@redhat.com> said:
> 
> 
>> I got slightly carried away with trying to eliminate some
>> -Wwrite-strings errors.  I'm trying to put the resultant mess on
>> cagney_writestrings-20030508-branch.
> 
> 
> Are you going to post patches, or are they too all-consuming/mindless
> to matter?  I wouldn't mind a brief description of changes you're
> making.  (E.g. what members of data structures are you turning into
> const char *'s?  All the name-like stuff?)

The doco in the cli.  It's where it tried to free it that I got scared :-)

> Anyways, looking at the patch to linespec.c, I was shocked to see that
> the changes were that simple, but actually you've been misled by the
> compiler.  Consider set_flags (from mainline, not from your branch):

I was using an iterative process:

	- compile with -Wwrite-strings
	- change one function signature to const char *
	- compile with -Wno-write-strings
	- fix up the parameter passing/assignment mess
	- repeat.

And gave up when things got really messy.  So don't take the branch too 
seriously.  I was carefully avoiding linespec.

Andrew




      reply	other threads:[~2003-06-03 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 20:40 Andrew Cagney
2003-06-03 21:18 ` David Carlton
2003-06-03 22:08   ` Andrew Cagney [this message]

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=3EDD1C56.3020102@redhat.com \
    --to=ac131313@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb-patches@sources.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