SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Apple Inc.
AAPL 260.21+0.3%3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Robert Salasidis who wrote (2375)5/21/1997 11:50:00 AM
From: Francisco A. Tomei, Ph.D.   of 213182
 
Robert,

You stated:

"Remember that any Rhapsody app on Intel will need a recompile. Therefore, the situation would be similar to NT,..."

I have not kept up with Rhapsody developments, but I know for a fact that the current NeXTstep/OpenStep developer environment supports FAT binaries. An application written under NeXTstep version 3.3 is supposed to compile (without modification of a single line of code) under four different architectures: Motorola 68040, HP-RISC, Sun Sparc and Intel x86. This fact may not be true, at least in part, for OpenStep 4.x, particularly when running under Windows NT.

My understanding is that NT does not support FAT binaries. Furthermore, the NT source code for Intel x86 will not compile under, for example, DEC Alpha.

If Rhapsody remains OpenStep compliant, applications written for the PowerPC architecture should compile under Intel x86 with little trouble.

I would welcome your comments.

Best regards.

--Francisco.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext