Args list too long

Thu Jan 11 20:32:00 GMT 2001

Jeff Sturm <jsturm@detroit.appnet.com> writes:
> You didn't mention `native' methods in your plan. The .cc sources must
> still compile to distinct .o files, right?

Yes. (Well, they don't *have* to, if we have an integrated C++/Java
compiler ...)
> Except for the native methods, symbols with package-private scope could be
> non-public in the object file. This would benefit platforms
> (e.g. win32) which incur an extra cost for exported symbols.

On Unix you might smaller relocation specifiers, which (slightly) reduce
the size of .o files. You also get faster link times, which mainly
matters for shared libraries.
-- 
	--Per Bothner
per@bothner.com http://www.bothner.com/~per/