That was for my processor by the way. I had it set up with >64K of ram... in the simulator. But, it worked

I think the point that BDD was making is that # has a special meaning to the assembler. It means "treat the next expression as a literal". You wouldn't write "2 = 10" in C code. It doesn't make any sense. By omitting the #, you are telling the assembler that it is an address rather than a literal "memory[2] = 10".

That being said, assemblers aren't known for having the greatest error checking around, so it's entirely possible that one would accept that input and turn it into God knows what

If you haven't done so already, you should download the Kowalski simulator and play around with some 6502 code to learn the finer points. Heck, you could even try out having your parser/lexer generate some object code for it (if you're in for a real adventure )

The final version of the Kowalski simulator, V1.2.12, was never made available for download, as Mike Kowalski is no longer maintaining the software. Attached is V1.2.12, which I have been using for more than a year.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

Hope wine can run this...

Yes, the last one I tried did run in WINE.

I doubt it. He sent me V1.2.12 after I discovered a bug in 1.2.11.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!