From: Eric Gallager <egall@gwmail.gwu.edu>
To: Mike Stump <mikestump@comcast.net>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: C++11? (Re: protected alloca class for malloc fallback)
Date: Tue, 23 Aug 2016 23:17:00 -0000 [thread overview]
Message-ID: <CAMfHzOutHEyQRni-9gfkth5VbTvSZ15Z2HPzfMwTbW0e3X-N=g@mail.gmail.com> (raw)
In-Reply-To: <F3026171-0D8F-43A0-821A-2BCB3C9006C0@comcast.net>
On 8/22/16, Mike Stump <mikestump@comcast.net> wrote:
> On Aug 22, 2016, at 5:02 AM, Eric Gallager <egall@gwmail.gwu.edu> wrote:
>>
>> As a rookie programmer considering possibly contributing to GCC in the
>> future once I'm more confident in my abilities, switching to C++11
>> would increase the barrier for me to contribute. I currently really
>> only know C, and I still have to learn C++ in general, much less all
>> the new features added in C++11.
>
> Don't worry, we don't exploit every feature of the language on every line.
> Most of the lines likely look just like plain C.
Right, I suppose that's true. And even if you did start using every
feature of the language, there'd still be other work available in
areas I'm more comfortable in, such as shell scripts, autoconf macros,
and Makefiles... assuming you also continue using the same build
system, that is...
next prev parent reply other threads:[~2016-08-23 23:17 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 11:30 protected alloca class for malloc fallback Aldy Hernandez
2016-08-04 12:58 ` Richard Biener
2016-08-04 15:19 ` Aldy Hernandez
2016-08-04 19:24 ` Jeff Law
2016-08-05 14:37 ` Aldy Hernandez
2016-08-05 15:15 ` Pedro Alves
2016-08-05 16:23 ` Jeff Law
2016-08-05 17:48 ` Richard Biener
2016-08-05 8:17 ` Richard Biener
2016-08-04 19:06 ` Pedro Alves
2016-08-04 19:16 ` Jeff Law
2016-08-04 19:22 ` Pedro Alves
2016-08-04 19:26 ` Jeff Law
2016-08-04 19:31 ` Pedro Alves
2016-08-05 2:10 ` Martin Sebor
2016-08-05 14:42 ` Aldy Hernandez
2016-08-05 17:56 ` Richard Biener
2016-08-05 18:16 ` Oleg Endo
2016-08-05 20:07 ` Richard Biener
2016-08-06 10:09 ` Aldy Hernandez
2016-08-06 10:15 ` Aldy Hernandez
2016-08-06 15:08 ` Richard Biener
2016-08-08 17:00 ` Jeff Law
2016-08-08 17:32 ` Trevor Saunders
2016-08-08 19:03 ` Richard Biener
2016-08-09 11:34 ` Oleg Endo
2016-08-09 17:34 ` Trevor Saunders
2016-08-10 17:03 ` Oleg Endo
2016-08-11 1:23 ` Trevor Saunders
2016-08-11 12:18 ` Oleg Endo
2016-08-11 17:55 ` Trevor Saunders
2016-08-20 2:29 ` Mike Stump
2016-08-21 20:00 ` C++11? (Re: protected alloca class for malloc fallback) Pedro Alves
2016-08-22 7:10 ` Trevor Saunders
2016-08-22 7:28 ` Richard Biener
2016-08-22 12:02 ` Eric Gallager
2016-08-22 12:58 ` Manuel López-Ibáñez
2016-08-22 22:08 ` Mike Stump
2016-08-23 23:17 ` Eric Gallager [this message]
2016-08-09 13:17 ` protected alloca class for malloc fallback Aldy Hernandez
2016-08-09 13:21 ` Bernd Schmidt
2016-08-10 10:04 ` Richard Biener
2016-08-10 10:12 ` Aldy Hernandez
2016-08-10 10:39 ` Richard Biener
2016-08-10 18:00 ` Jeff Law
2016-08-10 18:33 ` Richard Biener
2016-08-16 16:28 ` Jeff Law
2016-08-16 16:44 ` Jakub Jelinek
2016-08-16 16:47 ` Jeff Law
2016-08-16 17:54 ` Martin Sebor
2016-08-17 8:27 ` Richard Biener
2016-08-17 13:39 ` Martin Sebor
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='CAMfHzOutHEyQRni-9gfkth5VbTvSZ15Z2HPzfMwTbW0e3X-N=g@mail.gmail.com' \
--to=egall@gwmail.gwu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).