Timothy Madden writes:
> On Sat, Jan 30, 2010 at 4:05 AM, Paolo Carlini
> wrote:
> [...]
>> Even for implementors knowing *very* well both the details of the C++
>> standard and the internals of a specific front-end, implementing export
>> is an *highly* non-trivial task. [...]
>
> Yes, everyon
On 02/01/2010 01:26 AM, Timothy Madden wrote:
> Since such a change must happen in small steps, I would be interested
> to know how 'acceptable' would a limited implementation be at first ?
> Like the command line options I have seen declared 'experimental' in
> the gcc manual before ...
>
As I
On Sat, Jan 30, 2010 at 4:05 AM, Paolo Carlini wrote:
[...]
> Even for implementors knowing *very* well both the details of the C++
> standard and the internals of a specific front-end, implementing export
> is an *highly* non-trivial task. [...]
Yes, everyone is telling me that, but could someon
On Sat, Jan 30, 2010 at 4:23 AM, Michael Witten
[...]
> However, I have a gut feeling that at least a restricted version of
> 'export' (or a cousin of 'export') could be both useful and trivial to
> implement: [...]
>
Those were my thoughts too.
Since such a change must happen in small steps, I w
Snapshot gcc-4.3-20100131 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20100131/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.3 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Right now, each fresh clone needs to create a compressed pack, which
takes quite a while. (I think, there might be something else wrong
with the repository.)
