This is the mail archive of the
mailing list for the Java project.
Re: Args list too long
- To: Jeff Sturm <jsturm at detroit dot appnet dot com>
- Subject: Re: Args list too long
- From: Tom Tromey <tromey at redhat dot com>
- Date: 12 Jan 2001 10:41:14 -0700
- Cc: Per Bothner <per at bothner dot com>, "Bradley A. Smith" <yeldar at home dot com>, java-discuss at sources dot redhat dot com
- References: <Pine.LNX.email@example.com>
- Reply-To: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <firstname.lastname@example.org> writes:
Jeff> Except for the native methods, symbols with package-private
Jeff> scope could be non-public in the object file. This would
Jeff> benefit platforms (e.g. win32) which incur an extra cost for
Jeff> exported symbols.
There are cases in libgcj where a package-private method is actually
used by a native method in a different package. This is lame, but it
seemed like the most expedient way to solve the problem at the time.
Can we distinguish between these sorts of objects and the dll? That
is, make the package-private symbols non-public in the dll even though
they are visible outside the object at link time? It seems like this
must be possible.