Frank is not right. The import lines are there ONLY for compile purpose. If you look into compiled class file, you will see on begin the constant pool part. There are among others names of all necessary classes with package.
So the result: There isn't and can't be any difference between import java.util.Vector and java.util.*. Radim > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Frank D. Greco > Sent: Wednesday, June 26, 2002 4:37 PM > To: [EMAIL PROTECTED] > Subject: Re: How import affect the performance? > > > At 05:14 PM 6/25/2002 +0530, Panyam Krishna Murthy wrote: > >import java.util.* > > > >compared with: > > > >import java.util.Vector > >cause any added overhead? > > Nope. > > It used to be overhead back in the old days before > jar files (circa 95-97). imports used to cause directory > lookups, which were slow. > > With jar files (that have a manifest of course), there > shouldn't be a difference. > > Frank G. > +======================================================================+ > | Crossroads Technologies Inc, 55 Broad Street, 28th Fl, NYC, NY 10004 | > | Enterprise Java Engineering | > | Email: [EMAIL PROTECTED] Web: www.CrossroadsTech.com | > | Voice: 212-482-5280 x229 Fax: 212-482-5281 | > +======================================================================+ > > > _______________________________________________ > Advanced-swing mailing list > [EMAIL PROTECTED] > http://eos.dk/mailman/listinfo/advanced-swing > _______________________________________________ Advanced-swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/advanced-swing
