Re: A86: ti-85 emulation
[Prev][Next][Index][Thread]
Re: A86: ti-85 emulation
>
>>TASM? I've only used that once. Assembly Studio 86 is the way to go,
>>imho.
>
>Yes, but you can't predefine anything, so the #ifdef and #ifndef command
>macros are useless.
What do you mean you can't predefine anything? Use #define...
The current version did have some bugs, I believe, but in the version I have
(3.0 beta 2), those bugs are fixed. It WILL compile Vertigo, so I'm sure it
will compile anything you can throw at it :)
>>It will also support the 85, or even 82 or 83 if you write an output
>>plugin
>>for it (and since he included the source to the .86p plugin, it would
>>take
>>30 secs to compile one).
>
>Really? I didn't realize that. That would be VERY nice. Would make all
>calculator programming much easier.
>
Hmm, those might not be in the current released version, but they will be, I
assure you.
> Though I've never tried, Assembly Studio 86
>>should
>>support ANY processor that TASM does, because it uses the TASM .tab
>>files.
>>So theoretically you could compile 6502 code with Assembly Studio
>>86...
>
>Okay, but why? The only other useful instruction set for it to support
>would be the M68k. Whose gonna compile NES roms with a calculator
>assembler, anyway (I think that is what it is)
>
Hehe. TONS of stuff used the 6502. I believe it was the most used
processor back in the day for arcade machines and consoles. The Atari 2600
used it as well. The 68k was a nice chip, but much too expensive for
machines, when a cheap z80 for 6502 could be had for less than a quarter of
the price. 68k won't compile with TASM or Assembly Studio because it's for
8 bit processors. The 68k is a 16 bit processor. It'd take a lot of
modification for it to work with them (at least I think so).
>>
>>If you are making different versions, I would suggest using different
>>files,
>>unless you want your code to look like the Vertigo source... :)
>>
>
>Hey, it looks cool!
But can you understand it? =)