Hi Aaron,
you present a very simple picture. Is the picture that simple? Are you
saying there is never been a case where code that is correct, crashes
on Win32 but not on the Mac? Are you saying there has never been a case
that correct code needs to have work arounds written for Win32 only
bugs?
I'd like to know where I can learn about the Win32 bugs I'll have to
work around.
So long as you're not using Mac toolbox calls, it should work just
fine on
x86. Watch out for endian issues as well. Chances are, you're just
making
some assumptions in your code and not coding defensively. Those
assumptions
may be correct on Mac, but probably aren't on Windows.
I make no OS calls on Win32. On Mac the only call I make is to
BlockMoveData, but that's irrelevant, because BlockMoveData will not
compile on Win32!
Also, I want to make a linux version.
What do I need to do, buy a PC?
Yes.
What's the general technique for making a plugin *That works* with
100%
of it's functionality 100% of the time, on Mac, PC, and Linux?
Get a box that has the OSes you'd like to support and make sure to test
every step of the way on those boxes.
How do you transfer files? I find file transfer time and energy
consuming. When I have to perform 12 steps to transfer a file to VPC,
that consumes more energy than if I have to perform 1 simple "press
this button", even if it takes the same amount of time.
Ideally, when I press "build" on my Mac CodeWarrior, the Win32 plugin
would automatically appear, already in .rbx format on my Win32 computer
over the network. Is that possible?
--
Theodore H. Smith - Macintosh Consultant / Contractor.
My website: <www.elfdata.com/>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|