[2266] in java-interest
Re: Setting Boundaries (was Re: JDK Question)
daemon@ATHENA.MIT.EDU (Sami Shaio)
Wed Sep 27 15:24:59 1995
Date: Wed, 27 Sep 1995 09:41:16 -0700
From: Sami.Shaio@Eng.Sun.COM (Sami Shaio)
To: cmcmanis@scndprsn.Eng.Sun.COM, jcdst10+@pitt.edu
Cc: java-interest@java.Eng.Sun.COM
There are no native methods in java.awt.*. All the native methods
are done in another package that is platform-specific (or you can
even have multiple awt implementations on the same platform or
runtime).
--sami
|From daemon@java Tue Sep 26 23:13 PDT 1995
|Date: Tue, 26 Sep 1995 20:44:24 -0400 (EDT)
|From: James C Deikun <jcdst10+@pitt.edu>
|Subject: Re: Setting Boundaries (was Re: JDK Question)
|To: Chuck McManis <cmcmanis@scndprsn.Eng.Sun.COM>
|Cc: java-interest@java.Eng.Sun.COM
|Mime-Version: 1.0
|X-Info: To unsubscribe, send 'unsubscribe' to java-interest-request@java.sun.com
|
|
|
|On Fri, 22 Sep 1995, Chuck McManis wrote:
|
|>
|> Actually, adding more java files doesn't impact portability since they
|> just work. There are currently 28 classes in the java.* hierarchy that
|> have native methods (and thus require porting). Pure java code works the
|> same where ever it runs.
|
|I wonder how many of those native method classes are in java.awt.*.
|
|In any case, a third-party implementation still has to duplicate the
|library code unless it wants to work only in conjunction with the Sun
|distribution, so the libraries still add work that could have an especial
|impact on producers with low budgets.
|
|--
|James "impacted?!" Deikun
|-
|Note to Sun employees: this is an EXTERNAL mailing list!
|Info: send 'help' to java-interest-request@java.sun.com
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
