MaxCoderz

One logical step up for Latenite is to not have to be bundled with a 3rd party assembler.
Mainly because one (high profile!) user is having real problems getting the buggy TASM to work with it, and other people have expressed annoyance with TASM, (limited string length, limited label length, limited numbers of DBs, lack of features, buffer overflow crashes... the usual) I have decided that I need to write an assembler (BRASS).
WLA-DX is very nice but is geared towards console development and burning programs on ROMs, and defining a ROM bank map for a TI-83 Plus program is a bit silly. I will try and keep it as compatible with TASM as possible, so old TASM-geared code still compiles, but will add some new features.
Just to show that this isn't just an idea and that I am actually doing something about it, have an evening's work;

(BRASS at the top, TASM at the bottom - not that it actually matters!)
A lot of work still needs to be done - supporting ZIDX/ZIX/ZBIT instructions (anything like BIT *,A or LD A,(IX*)) is a pretty important one, for starters. The expression parser (for things like "_label+21" needs to actually parse expressions (all it does at the moment is check for and substitute in labels or numbers). Directives for conditionals and macros (and macros themselves!) need to be worked in.

Currently supported directives: .org, .include (#include maps to .include), .locallabelchar and .module.

.include could do with some work, this will compile (or rather, it won't ever get into pass 2):

File: test.asm


I also need ideas for directives. Some are already in my mind (.dbsin, .include_once (like PHP's require_once()), .incbin)... What would you implement if you were writing a Z80 assembler?

This is a great idea ben! More than 30 array elements per line would be a great feature, especially when strings are concerned.

Here is a nice TASM reference with a list of directives and stuff: http://home.comcast.net/~tasm/tasmman.htm

_________________
"My world is Black & White. But if I blink fast enough, I see it in Grayscale."

Ben, you rock! Why do you call it BRASS?


Smiles in silence

_________________
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS

B/c BRASS KICKS A**.
Ben this is looking sweet!

My initials combined with assembler. Maybe the lack of differentiation between arse (backside) and ass (donkey) in US English means this is a bad choice...

Did 'BRASM' ever cross your mind?

_________________
"My world is Black & White. But if I blink fast enough, I see it in Grayscale."

Well, it's really Brass. I tend to stick to words that make sense (so a DOOM-like engine I was toying with was called "Broom").
Though, to be honest, the actual name is of little real importance!

How about a poll with possible names?

anyone have suggestions for names that could be put on the poll?

_________________
In Memory of the Maxcoderz Trophy

BRASS sounds good to me.

_________________

I like brass, i think it's cool. A name suited for the project who's goal is to replace tasm.
Anyway, a project like this is LONG overdue. Ben if you achieve this you are my hero.

As for requests more support for Multipage apps and OSes.

_________________

I agree with Jim on all accounts

_________________
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS

I'd really rather see Z80 added to NESHLA.

_________________
You know your hexadecimal output routine is broken when it displays the character 'G'.

Main updates:
Expression parsing now works, but in a non-TASM way. The easiest approach I could think of was a simple recursion splitting up the expression by parentheses and operators. It doesn't add up in left->right order, thanks to this, and as a result unless you wrap everything in parentheses the order of operation is very odd.
Fixed bug where 16-bit operations declared in the table file weren't being flipped.
Z80 index (ZIX/ZIDX) instructions added.
Binary is no longer written in the order of instructions in the file: eg;

...should produce BA, not AB.

Supported directives (anything in [brackets] is an alias):
.org
.include [#include]
.locallabelchar
.module
.db [.byte] [.text]
.dw [.word]
.block
.chk
.echo
.equ [=]
.export
.fill

What needs doing:
Not all ZBIT directives work at the moment I need a document on them (building an assembler without a machine-code reference is a stupid idea, after all!).
Macros! TASM is thankfully quite simple, just basic find-and-replace style macros.
TASM-like expression parsing (including substituting $ for current IP), as well as adding % ~ = != < > <= >= operators.

The main priority for me is to get a really basic assembler that works like TASM, so I can get rid of TASM's oddities. In the same way that I can use WLA-DX to assemble TI projects, but it's not TASM compatible.
I'm not sure what this would really require me to do, not ever having assembled a multipage app/OS.

Don't forget

.define [#define]
.ifdef [#ifdef]
.ifndef [#ifndef]
.else [#else]
.endif [#endif]

_________________
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS

Oh yes (see "What needs doing:") - macros.