In article
<Pine.LNX.4.44.0805071236490.13992-100000@[EMAIL PROTECTED]
>,
Beta Zero <beta_zero@[EMAIL PROTECTED]
> wrote:
> On Thu, 6 Mar 2008, rodmc wrote:
> >Subject: Re: Newbie
> >
> >Hi,
> >
> >I am in the same situation so if you are prepared to join the
> >Association of Computing Machinery ($99) per year you can get
> >access to quite a few books on Objective-C, Mac programming
> >via their electronic books services (namely Safari). The book
> >you mention is on it as well as is "Programming in Objective-C"
> >which although I bought in its real form some time ago I can
> >say is a good read for getting to grips with the basics of the
> >language before diving into Mac OS X specifics.
>
> Hi! I'm relatively new to the Mac 'mini' and would like to ****t some
> vintage 68000 assembly language source over to 'C' on the Mac. It's
> pure 68000 code, and I regret to say I have zero experience with 'C.'
>
> Do you know of any good books to get, or scope out? Even if they are
> hard to come by? I want to ****t some Atari ST code over to the Mac.
> I have about a meg of 68000 source code - that's not much but it
> represents several years of handtinkering, and fine-tuning. It's
> independent of GEM binding (I always had trouble with GEM, so I
> manhandled the thing into existence, occasionally delving into
> supervisor mode when necessary.).
>
> I was wondering if it would be easier hand-tinkering this into shape
> for execution on a Mac. What is your favorite assembler for the Mac?
>
> Are there any good books you can suggest?
Aaron Hillegas' "Cocoa Programming for OS X"
http://www.amazon.com/Cocoa-Programming-Mac-OS-2nd/dp/0321213149
is the
book to get. (Actually, the third edition, which isn't quite out yet, is
the one to get.)
You'd have to be pretty crazy to program Macs in assembly language: a
substantial fraction are Intel Macs. a substantial fraction are Power PC
Macs. iPhones, and iPod Touches run OS X, but use the Arm processor.
Macs have one to eight "cores" (Think independent CPUs). Some Macs have
vector processing units. They have varying degrees of processing power
in the video card. Future machines may be yet again different.
Do you want to spend your life coding for all the possible combinations
of machines that will run your code?
If you call Apple's libraries, then you'll get optimized performance by
experts of the whole range of current (and future!) hardware.
That said, you can intermix Objective-C, C, and C++, if you know what
you are doing, and many people treat C as a universal assembler. You can
pretty much do a one-to-one translation from a line of assembly language
to a line of C. You'll produce hideous C, though.
Consider this web page:
http://www.vetta.org/2008/05/scipy-the-embarrassing-way-to-code/
The author describes how doing a blind translation from one language
resulted in something much longer to write, and much slower to run, than
taking advantage of the sup****t that was built-in.
|
