[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: METAL is now FREE!!!!!!
In article <1993Mar31.175108.10039@cs.UAlberta.CA> glyn@cs.UAlberta.CA (Reade Glyn Devin) writes:
[Stuff Deleted]
>> I wonder how Andy programmed this? Huh? Any suggestions? Go ahead and explain
>> to me how code generated using 65C02 assembly is EASILY portable "with very
>> little change" to the Macintosh or IBM platforms...This I want to hear...Sorry
>> bud, but the Motorola 68000 series is just a little differnet than the 6502
>> series processors and porting code from the 6502 to the 68000 was, last time
>> -I- checked, a royal pain in the ass and not worth the time considering the
>> decent C compilers available on the Mac.
>
>#define FLAME
#define FLAME-RESPONSE
>Yo buddy! Take a break!
I do not need one. Work is easy enough.
>First off, I have not used METAL, LLUCE, etc. so I will not comment about
>things with which I am not familiar (hint, hint).
Then before you open your mouth again, realize that LLUCE, ACOS and METAL are
ALL written in 65C02 Assembly and NOT 65816 Aseembly. This will have bearing
later on when you go into your little speal about what you know.
>However, I _am_ familiar with the Apple IIGS, as well as the 680x0, i80x86
>and most other platforms that you care to mention. For those not following
>this on a *apple* newsgroup:
>
> 1. The GS uses a 65c816, not a 65c02
Correct. LLUCE, METAL and ACOS are all written in 65C02 and are NOT GS
specific. An extended IIE can run any of them.
>
> 2. The GS has firmware/system software that, at the programming
> level, is almost identical to the Mac's firmware/software.
> Remember those toolbox calls? From a high-level language
> (ie: C) you can often get by with no changes. If you're using
> an assembler that has a decent macro set, the changes are
> also minor, assuming you produced good code the first time
> around.
Great. Understandable, and agreed upon -IF- you are writing in 65816 assembly
-AND- using Tool Box calls etc..
In this case, the program in question, LLUCE, is generated using 65C02
Assembly and DOES NOT use the toolbox -AT ALL- that I am aware of. Therefore,
my original point is STILL valid. Porting 65C02 code to a 6800 series when NO
tools are being used is a pain in the ass.
>I concede that the 65c816 is no powerhorse, and the 6502 is even less so.
>However, as Steven Lichter mentioned, there is no need for computer bashing.
>I may use a Sun or IBM at work, but for enjoyment I program my GS and like
>the GS community. Relax a bit, OK?
I am -NOT- bashing computers. I am simply pointing out a misrepresentation of
a product and a -REALLY- idiotic statment. I personally feel that your above
statment has more to do with computer bashing than my original post, as I made
NO mention of which computer was better or worse. Again, the ONLY point I made
in the above post was that porting 65-C-02 assembly to 68000 series is a PAIN.
>#undef FLAME
#undef FLAME-RESPONSE
>
>> Point is, your way misinformed. Are you the same idiot that claimed LLUCE was
>> a MultiLine BBS system under ProDos 8? And that you could have two people
>> sharing the same BBS system as long as you had...
>>
>> 1. A Macintosh Filserving
>> 2. 1 II with A modem
>> 3. A second II with a modem
>>
>> > That has its advantage if a SysOp want
>> >to move to a different computer. I'll stick with my II and GBBS/LLUCE.
>> >Apple II Forever!!!!!!!
>>
>> Good...Stay there and be "awed". Just don't ever look at METAL or you'll
>> realize just how badly you have been ripped off by L&L.
>
>Oh, and by the way: Please quit cross-posting this to comp.sys.apple2.gno.
>That is a newsgroup for the GS' Unix clone, not for BBS info. Anyone
>reading csa2g is also likely reading comp.sys.apple2 which is more
>appropriate, and will therefore receive it there. (Time to edit my
>KILL file.)
'
That was an oversite on my part. It has been corrected. The initial post in
this thread was cross-posted to other newsgroups to reach the maximum user
audience.
#define FLAME-RESPONSE
And yes, I -DO- know what GNO is considering the fact that I use it every day
and am a customer of Procyon.
#undef FLAME-RESPONSE