From: Andrew Cagney <ac131313@ges.redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add one "const" keyword
Date: Thu, 12 Sep 2002 17:43:00 -0000 [thread overview]
Message-ID: <3D8134C1.8030807@ges.redhat.com> (raw)
In-Reply-To: <20020913002803.GO1105@gnat.com>
> 2002-09-12 Joel Brobecker <brobecker@gnat.com>
>> >
>> > * value.h (find_function_in_inferior): Add const keyword to
>> > one of the parameters. Allows us to invoke this function with
>> > a const char *.
>> > * valops.c (find_function_in_inferior): Likewise.
>
>>
>> So yes, obvious.
>
>
> Thank you, it's in.
>
> BTW: Would it be worth having a page with a list of easy changes that
> could help the gdb project? This one would qualify, and being able to
> compile with -WWwrite-strings would be quite useful. I remember when I
> was doing my military service (this stopped being an obligation only a
> few years after I did mine) that I found myself with a lot of free time.
> I moved my computer on my desk, and I was wondering how I could
> contribute back to the free software community, to say thank you. I
> looked at helping on certain projects I was interested in, but ended up
> creating GtkAda with another friend of mine, as most of the assignments
> I would be able to get from the already existing projects seemed a bit
> too hard as a first step in the project. Maybe a page with such a list
> of easy changes for some people looking for some ways to contribute
> would help? Just some out of the box thinking...
I think the best starting point is the bug database (under change
request). Some of the GDB developers activly monitor it (Some don't
though :-( ). After that, the ARI, but I tend to save that one for
rainy days :-)
Neither of these are sorted in ``easyness'' order though :-(
Andrew
prev parent reply other threads:[~2002-09-13 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 16:51 Joel Brobecker
2002-09-12 17:13 ` Andrew Cagney
2002-09-12 17:28 ` Joel Brobecker
2002-09-12 17:43 ` 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=3D8134C1.8030807@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=brobecker@gnat.com \
--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