> Mike Stump <[EMAIL PROTECTED]>:
> On Thursday, May 5, 2005, at 02:53 PM, Andi Vajda wrote:
>> I wish the same were possible on Linux and Mac OS X but I have not
>> been able to create a shared library that is statically linked
>> against libgcj.a
> Should just work, though, you don't want
> Brian Dessent :
[snip! Access from plugins to every aspect of the compiler]
> ... This means you'd have to move essentially everything into this
> mega-DLL, leaving cc1 and friends as merely stubs that set a flag and
> then call into the DLL never to return, since anything left in cc1
> woul
> Mark Mitchell :
> I think virtual functions are on the edge; quite useful, but do result
> in the compiler adding a pointer to data objects and in uninlinable
> indirect calls at run-time. Therefore, I would avoid them in the
> initial subset of C++ used in GCC.
Umm...? Virtual functions
> Larry Evans :
> claims that switch statements are faster than virtual function calls.
That's not really interesting, is it? The overhead and downsides of
virtual functions are well known.
The upside is the possibility to use polymorphism to make frameworks.
All kinds of pluggable framewor
> Martin Jambor :
> Well, IIRC mostly worries about history. SVN claims to be able to
> track history of renamed files but I use the git mirror now and I
> wonder what the history would show there. I would consider it very
> unfortunate if 'git blame' did not show the .c era history of the
>
