🚀 go-pugleaf

Hakan:

There are no "methods in JBuilder" to avoid.  The rules for
portability in Java are simple.  Don't reference Native code.  That's
all that John is talking about.  If you've written JNI code for one
platform, you can't just take it to another.

There are still portions of Java 1.1 that are not implemented on all
platforms (most often because there is no implementation on the local
platform to leverage).  That's stuff you will pick up as you use a
particular platform version of the JDK.

-Rich

Hakan UNLU wrote:
> 
> Can you be more specific. Which methods we should avoid in JBuilder to stay
> portable.
> 
> Steve Schafer (TeamB) wrote:
> 
> > On Thu, 17 Dec 1998 16:13:56 GMT, morbideus@softhome.net (morbideus)
> > wrote:
> >
> > >I will soon purchase JBuilder but I would be sure of one thing:
> > >If I compile toto.java and obtain toto.class in JBuilder, can I use
> > >toto.class on any platform for example on Linux whith jdk installed on
> > >it, by typing "java toto.class" ?
> >
> > As long as your application doesn't make any system-specific calls (to
> > customized native methods, for example).
> >
> > -Steve
> 
> --
> ====================
> Hakan UNLU
> Home: hunlu@geocities.com      Work: hitit@turk.net
> and my bookstore :
> http://www.geocities.com/SiliconValley/Campus/3043/LitHome.htm
> ====================

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=