From: Fabian Cenedese <Cenedese@indel.ch>
To: <gdb@sources.redhat.com>
Subject: RE: Discussion: Formalizing the deprecation process in GDB
Date: Fri, 08 Oct 2004 08:54:00 -0000 [thread overview]
Message-ID: <5.2.0.9.1.20041008090820.0abedf30@NT_SERVER> (raw)
In-Reply-To: <NUTMEGYiufL0xJdQdSe00000308@NUTMEG.CAM.ARTIMI.COM>
>> A running joke between several of the GDB developers at the last GCC
>> summit was that we should present a 1hr paper titled "porting
>> GDB to a
>> new architecture". Only instead of presenting slides, we'd
>> just write the code.
>
> I find it hard to believe that's possible for anyone who comes to the code
>from fresh. You have spent years working with gdb and have the advantage of
>knowing your way round the code, and what the replacements for each
>deprecated thing are; anyone else has to do lots of research. If there's
>going to be a formalization of the deprecation process, my 'feature request'
>would be that there be one single central place where all deprecated
>features are listed together with brief pointers to the new functionality
>that has taken their place.
I also have been looking for this kind of document as I have come across
deprecated functions. As I couldn't find something I started using them
knowing that the code won't be accepted like this. Following now this
discussion that would mean that I haven't read the accompanying
comments of the deprecated functions or I would have seen the proposed
replacements. I guess I need to look harder. So even if you don't come
to a conclusion you have helped a newbie :)
Thanks
bye Fabi
next prev parent reply other threads:[~2004-10-08 7:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 17:55 Joel Brobecker
2004-09-27 20:35 ` Eli Zaretskii
2004-10-06 6:14 ` Andrew Cagney
2004-10-06 13:39 ` Eli Zaretskii
2004-10-07 4:48 ` Joel Brobecker
2004-10-07 14:27 ` Dave Korn
2004-10-07 15:12 ` Joel Brobecker
2004-10-07 16:16 ` Andrew Cagney
2004-10-07 18:50 ` Dave Korn
2004-10-07 16:14 ` Andrew Cagney
2004-10-07 18:08 ` Dave Korn
2004-10-07 19:18 ` Joel Brobecker
2004-10-07 19:28 ` Dave Korn
2004-10-08 7:08 ` Joel Brobecker
2004-10-08 12:13 ` Eli Zaretskii
2004-10-08 12:05 ` Eli Zaretskii
2004-10-08 8:54 ` Fabian Cenedese [this message]
2004-10-08 11:45 ` Eli Zaretskii
2004-10-08 19:22 ` Andrew Cagney
2004-10-10 21:31 ` Eli Zaretskii
2004-10-08 10:45 ` Eli Zaretskii
2004-10-08 13:31 ` Dave Korn
2004-10-08 13:38 ` Eli Zaretskii
2004-10-08 13:43 ` Dave Korn
2004-10-08 13:44 ` Dave Korn
2004-10-08 19:16 ` Eli Zaretskii
2004-10-08 19:45 ` Eli Zaretskii
2004-10-08 22:10 ` Andrew Cagney
2004-10-08 10:38 ` Eli Zaretskii
2004-10-11 15:11 ` Andrew Cagney
2004-10-12 7:34 ` Eli Zaretskii
2004-10-12 13:42 ` Mark Kettenis
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=5.2.0.9.1.20041008090820.0abedf30@NT_SERVER \
--to=cenedese@indel.ch \
--cc=gdb@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