How can i change the compiler from Brass to TASM and if someone can send me a TASM command line example that would be great!
Thanx,
POS
Thanx,
POS
Sucks to be you then. Brass is better than TASM, so maybe you should rethink why you don't like brass, or you shouldn't use Latenite.
No, and I'm not entirely sure you can. It would be a royal pain to change the batch scripts it creates automatically every time...
Only way you really could would be to code a program, call it brass.exe, and have it translate the brass command line options to TASM-style ones.
Or you could realize your mistake and grasp that Brass pwns TASM
Only way you really could would be to code a program, call it brass.exe, and have it translate the brass command line options to TASM-style ones.
Or you could realize your mistake and grasp that Brass pwns TASM
Then how would i change this to run on brass?
.nolist
#include "ti83plus.inc"
#define ProgStart $9D95
.list
.org ProgStart - 2
.db t2ByteTok, tAsmCmp
b_call(_ClrLCDFull)
ld hl, 0
ld (PenCol), hl
ld hl, msg
b_call(_PutS) ; Display the text
b_call(_NewLine)
ret
msg:
.db "Hello world!", 0
.end
.nolist
#include "ti83plus.inc"
#define ProgStart $9D95
.list
.org ProgStart - 2
.db t2ByteTok, tAsmCmp
b_call(_ClrLCDFull)
ld hl, 0
ld (PenCol), hl
ld hl, msg
b_call(_PutS) ; Display the text
b_call(_NewLine)
ret
msg:
.db "Hello world!", 0
.end
When you start a new project in Latenite, it adds all the 'required' stuff automatically, so all you need is this part, which would be the actual code: (in the file where it has "program begins here: ")
Code:
Code:
b_call(_ClrLCDFull)
ld hl, 0
ld (PenCol), hl
ld hl, msg
b_call(_PutS) ; Display the text
b_call(_NewLine)
ret
msg:
.db "Hello world!", 0
ohhhhhhh, i didn't know that. okay. thanx. i think i might just use brass because TASM is also too hard
However, in TASM it sometimes glitches so you need to add 2 ".end"'s
ps
Nice to talk to you for the first
time Mr.KermMartian
ps
Nice to talk to you for the first
time Mr.KermMartian
POS wrote:
But when i am compiling from latenite using brass will it do what u r saying?
What I said is for Latenite, which is what you are talking about. As Kerm said, a file that assembles with TASM will assemble the same in Brass. It is Latenite that does things differently, and that is what I was talking about above.
POS wrote:
so latenite and brass are 2 whole different things?
FINALLY, HE GETS IT. Of course, we could have saved all this if you would have just read my post where I said that Latenite and Brass are different
Or he could have asked me at school
But yeah, Brass is simply the COMPILER for Latenite, which is the editor. It all wraps up into a nice little IDE
But yeah, Brass is simply the COMPILER for Latenite, which is the editor. It all wraps up into a nice little IDE
Any fool can use a computer. Many do.
Kllrnohj wrote:
When you start a new project in Latenite, it adds all the 'required' stuff automatically, so all you need is this part, which would be the actual code: (in the file where it has "program begins here: ")
Code:
Code:
b_call(_ClrLCDFull)
ld hl, 0
ld (PenCol), hl
ld hl, msg
b_call(_PutS) ; Display the text
b_call(_NewLine)
ret
msg:
.db "Hello world!", 0 Actually, all of the header stuff is put in headers.asm, and that is the file that Latenite tells Brass to start compiling at. Conveniently, you don't have to change anything to that file to compile for different shells/calculator models, as it's all in there and just compiles the parts accordingly. Brass is much more powerful than tasm, however there are a few differences:
1. b_call( in tasm, bcall( in brass
2. b_jump( in tasm, bjump( in brass
As for the rest, Brass1 is completely compatible with tasm. Again, Brass has added support for more things:
1. labels are just at the start of the line and don't need the colon (":")
2. Either .db or db, as well as other instructions with similar stuff (#define, define, .define, x=y,x .equ y)
3. More directives, and designed to be more similar to higher level languages
Rush Hour
Version 1.3. Works completely, check it out here
Version 1.3 has support for two special cars to be removed, an on-calc level editor, and flash-memory support that actually works correctly.
Please "encourage" me to work more on
Anyway you feel like (personal messages, spam, poke me with a stick, even better if it's Weregoose's stick of optimization, etc.)
Version 1.3. Works completely, check it out here
Version 1.3 has support for two special cars to be removed, an on-calc level editor, and flash-memory support that actually works correctly.
Please "encourage" me to work more on
Anyway you feel like (personal messages, spam, poke me with a stick, even better if it's Weregoose's stick of optimization, etc.)
The full list of directives that Brass adds to TASM can be found here:
http://www.benryves.com/bin/brass
http://www.benryves.com/bin/brass
Calc Buffoon wrote:
Actually, all of the header stuff is put in headers.asm, and that is the file that Latenite tells Brass to start compiling at. Conveniently, you don't have to change anything to that file to compile for different shells/calculator models, as it's all in there and just compiles the parts accordingly.
Which doesn't contradict anything I said, although you wrote it with that tone. Why?
Quote:
Brass is much more powerful than tasm, however there are a few differences:
1. b_call( in tasm, bcall( in brass
2. b_jump( in tasm, bjump( in brass
1. b_call( in tasm, bcall( in brass
2. b_jump( in tasm, bjump( in brass
Thats determined by whatever header it is using, not the assembler.
@harq: remember these are assemblers, not compilers
Register to Join the Conversation
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Advertisement