From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_02A9_01C5607C.C9454B20
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Can't you even remember the noise that you post.  If you statement =
"if compiled for windows then it requires windows" then wine
could not = work, right?

   As for your claims "once spat out by the compiler it has verious =
expectations which only a given OS (& usually only on a given cpu =
arch)can provide.", well this is false too.  I can't speak for other =
vendors but the Microsoft Visual Studio compiler and linker and used to =
target multiple environment from Windows to Windows CE to the .NET =
Framework and other ECMA/ISO standard compilant environments to EFI, a =
boot environment supported by Intel and others.

   I thought you were working for sun.  Did I misunderstand something or =
are you just no longer with them?

Rich

  "Adam Flinton"  wrote in message =
news:42937358{at}w3.nls.net...
  Rich wrote:
  >    It sounds like you are fixated on the packaging of applications =
(e.g.=20
  > .EXE vs. .class).  I have plenty of examples of components that do =
not=20
  > bind directly to any Win32 APIs.  Your own example is easily =
expressed=20
  > in portable ANSI C
  > =20
  >         system(CommandString)
  > =20

  Given people (outside of opensource projects) only ever get to see the =

  compiled code then if compiled for windows then it requires windows. =
I'm=20
  sure you can write portable C, C++ etc but then once spat out by the=20
  compiler it has verious expectations which only a given OS (& usually=20
  only on a given cpu arch)can provide.

  Whereas I can give you a jar & not really know or care what OS or cpu=20
  arch you have.

  >    I'm sure this isn't just because you are employed by sun.  I'm =
still=20
  > a bit surprised that you are now claiming that portable code is=20
  > otherwise not possible.
  > =20
  I'm not employed by Sun. Portable code is possible but then also=20
  dependant upon the portability of the libs should you choose to use =
libs.

  Adam
------=_NextPart_000_02A9_01C5607C.C9454B20
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Can't you
even remember =
the noise that=20
you post.  If you statement "if=20
compiled for windows then it requires windows" then wine
could = not work,=20
right?
 
   As for
your claims "once spat out by the
compiler it has = verious=20
expectations which only a given OS (& usually only on a given cpu =
arch)can=20
provide.", well this is false too.  I can't
speak for other = vendors=20
but the Microsoft Visual Studio compiler and linker and used to target = multiple=20
environment from Windows to Windows CE to the .NET Framework and other = ECMA/ISO=20
standard compilant environments to EFI, a boot environment supported by = Intel=20
and others.
 
   I thought
you were working =
for=20
sun.  Did I misunderstand something or are you just no longer
with=20 them?
 
Rich
 

  "Adam Flinton" <adam{at}NOSPAM_softfab.com>">mailto:adam{at}NOSPAM_softfab.com">adam{at}NOSPAM_softfab.com>
= wrote in=20
  message news:42937358{at}w3.nls.net...Ri=
ch=20
  wrote:>    It sounds like you
are fixated on the =

  packaging of applications (e.g. > .EXE vs. .class).  I =
have plenty=20
  of examples of components that do not > bind directly to any =
Win32=20
  APIs.  Your own example is easily expressed >
in portable =
ANSI=20
  C>  =
>        =20
  system(CommandString)> 
Given people (outside of=20
  opensource projects) only ever get to see the compiled code then =
if=20
  compiled for windows then it requires windows. I'm sure you can =
write=20
  portable C, C++ etc but then once spat out by the compiler it has =
verious=20
  expectations which only a given OS (& usually only on a given =
cpu=20
  arch)can provide.Whereas I can give you a jar
& not really =
know or=20
  care what OS or cpu arch you
have.>    =
I'm sure=20
  this isn't just because you are employed by sun.  I'm still =
> a=20
  bit surprised that you are now claiming that portable code is > =

  otherwise not possible.>  I'm not
employed by Sun. =
Portable=20
  code is possible but then also dependant upon the portability of =
the libs=20
  should you choose to use
libs.Adam

------=_NextPart_000_02A9_01C5607C.C9454B20--

--- BBBS/NT v4.01 Flag-5