This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Support for export keyword to use with C++ templates ?
- From: Timothy Madden <terminatorul at gmail dot com>
- To: Paolo Carlini <paolo dot carlini at oracle dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 3 Feb 2010 03:14:18 +0200
- Subject: Re: Support for export keyword to use with C++ templates ?
- References: <5078d8af1001201257i51f5e2bbm8c07cfb2af698a11@mail.gmail.com> <5078d8af1001222235p71475db9lf8efb2d71eb33e17@mail.gmail.com> <mcrfx5uvyt9.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <5078d8af1001291547k7b95fd61t2076827c9e39beb1@mail.gmail.com> <mcrd40sjvno.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <4B6393E7.3070205@oracle.com> <b4087cc51001291823u5bd82f40n21d2ce8c1673909d@mail.gmail.com> <5078d8af1001291846y39305e16u4760ea05ab79b5ad@mail.gmail.com> <5078d8af1001311626v44b9963h59cefcbd3ebae065@mail.gmail.com> <4B662271.8090405@oracle.com>
On Mon, Feb 1, 2010 at 2:38 AM, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> On 02/01/2010 01:26 AM, Timothy Madden wrote:
[...]
> As I see the issue, you should first check over the next months that the
> feature is not deprecated by ISO.
I know, I tried to talk about it on std.c++. I am afraid I can not see
a consensus in the end, still I would not say the committee will just
remove it. They were strongly against deprecation in 2003.
> Then start learning about the
> internals of GCC and eventually propose a detailed plan explaining how
> you want to attack the problem, because before that it's extremely
> unlikely that the C++ front-end maintainers could even consider
> reviewing patches from a novice for such an hard to implement feature.
Yes it is.
I wish there were a nice and easy way about it, but an attempt at
export is something quite big ...
> That said, if you *really* plan contributing to GCC, maybe outside
> export first (which seems a terribly good idea to me) first and
> foremost, read the relevant web page:
>
> ? http://gcc.gnu.org/contribute.html
>
> and start immediately the paperwork for the Copyright assignment,
> because it takes time.
I see that what I need is an assignment for all future changes. If my
employer is not involved with any contributions of mine, the employer
disclaimer is not needed, right ?
It is going to be a while until I will be able to submit any kind of
patch; should I start with the paperwork ?
Thank you,
Timothy Madden