Allan wrote:
>> This claim is complete nonsense: Mac OS X has not been available on x86
>> processors until last year (in beta versions on a single system
>> configuration). I suppose you are confusing Mac OS X with the Mach kernel,
>> which indeed has been running on x86 processors for decades now.
> 
> Fact: Apple has been running OS X on intel processors since the inception of
> OS X.  Just look at the frigin 10.0, 10.1, 10.2, 10.3, etc, source code!  Do
> you think they were coding #ifdef i386 for practice?

Apple has only released the source code of the kernel, and thus your
statement is definitive proof that you do not understand what you are
talking about!!! The GUI and anything above kernel level (except standard
Unix OSS tools of course) were never released as source code, and have not
been to this day, all for very obvious reasons (they are confidential Apple
intellectual property).

Binary-only releases of those x86 system layers above the kernel level were
made available last year as part of the x86 versions of Mac OS X. And that
Mac OS X is more than its kernel and Unix environment should be clear to
even the most ignorant and clueless around. Of course, assuming you actually
know what a kernel is, which I suppose you don't know either :-(

> Considering the GUI interface on POV-ray for the Mac, what you need to
> understand is this: forget Code Warrior, Code Warrior is dead, dead, dead.
> Long live XCode.  Code Warrior can RIP for all we Mac programmers care.
> Take a few hours to learn Objective-C and Interface Builder and put a
> decent front-end on the POV-ray C code and build a universal app for PPC
> and intel.

Which again shows you absolutely do not understand what you are talking
about. XCode, which is just an unreliable IDE for gcc, supports Apple Carbon
API (aka standard C and C++) development just fine, much better than Cocoa
API (aka Objective-C) in fact.  Objective-C is a proprietary Apple-only
extension to gcc, and hence does not enjoy the widespread support as the
standard C and C++ compilers within gcc. That CodeWarrior has been
discontinued for Macs has absolutely nothing to do with porting.

In fact, you conveniently overlooked or did not understand that part in my
Sept 25 reply to you, where I explicitly point out the porting problems. If
you had understood what I was talking about, you would instantly have
noticed that neither of the issues listed there have anything to do with the
GUI frontend for POV-Ray. Porting that is almost trivial.

> I have said enough on this thread and will not be posting to it any more.

Thank you! You really have wasted my time long enough :-(

	Thorsten

Post a reply to this message