Re: Driver optimization.
Rakesh Dubey (rakesh@arp.com)
Tue, 2 Jul 1996 14:04:36 -0700
> On Mon, 1 Jul 1996, Ralph Lewis wrote:
> On Mon, 1 Jul 1996, Darren J Moffat wrote:
>
> > On Sun, 30 Jun 1996, Rakesh Dubey wrote:
> >
> > > A somewhat more sophisticates approach is used in NextStep where you
> > > have a fat binary for several architectures. The program loader knows
> >
> >
> > The same happens in MacOS for m68k and PPC binaries. I've even seen
> > programs running with m68k and PPC code at the same time, since MacOS for
> > PPC does actually have an m68k emulator in it. eg. Photoshop m86k
> > running on PPC with PPC native plugins for Kai's power tools.
> >
> >
> > The other answer to multiarch binaries is of course the Java way....
>
> I think the answer lies with Openstep for multiarch binaries. Check
> out http://www.gnustep.org. With Openstep applications no longer become
> dependant upon the OS. Right now I think they have Openstep for Solaris, HPUX,
> Next, and NT. This means that an Openstep app will run on all these OSs in the
> same binary form. Has some kind of Object layer independence. Anyway, I'm not
> an expert by far, so I I'm wrong, don't flame, just say 'you're wrong'.
>
> PS I would like to see this in linux....
I would like to point out that "fat binaries" is not in OpenStep
specification so a OpenStep app will not run on different platforms
as you mention. It is a NeXT only scheme.
-rakesh