nesdev.org

As it were, IB CS forces students to use Java. Now I'm not 100% certain, but I've got $20 saying the ca65 is not written in Java. For the curious, the criteria are as follows: 1) Arrays 2) User-Defined Objects 3) Objects As Data Records 4) Simple Selection (if-else) 5) Complex Selection (nested if, ...

Ok, optimizations aside, what are features you would like to see in an assembler?

One of the things I am really set on having is block comments (/* */).

Are there any features you wish a current 6502 assembler had? Anything you really don't like?

As someone pointed out, you're talking about a assembler, not a compiler. There's already great assemblers out there. You might want to focus just on the optimizations - instead of generating code and warnings, just generate warnings. Much like lint. Then people could run their code through your to...

Let me clarify, the compiler will not optimize the code for you, it will output something saying "Check out this line, you might want to do this". Now I'm assuming someone who is writing code to be cycle-accurate would know what they are doing and know this would break the code. The optimi...

I'd be very pissed if my assembler filtered out one of the writes, as that would produce a very hard to find bug. Well to be fair, I could program the optimization to recognize necessary double writes, seemingly useless reads, etc. Also, I'm not necessarily saying the compiler will have carte blanc...

tepples wrote:Are you making an "assembler", which compiles a dialect of assembly language to an object file, or a "compiler", which is generally understood to compile a higher-level language?

I'm writing an assembler. Straight 6502 -> ROM.

I am currently planning a 6502 compiler for a few reasons: 1) I'm kind of annoyed by different features or the lack thereof with different compilers. 2) I'm in an IB CS class and have to write a program for my final so I figured I'd go with something I might actually use and like. On the note of the...

koitsu wrote:I've updated the phrasing of the bit in question. Instead of saying "1: AND all ...", I've changed it to "1: logically AND all...", which should act as extra clarification.

That makes it much clearer.

http://wiki.nesdev.com/w/index.php/PPU_registers#Mask_.28.242001.29_.3E_write The line states that writing #$30 to $2001 will produce a monochrome display. It seems that is incorrect. Writing #$1F will produce the monochrome display. Writing #$30 will only remove the background rendering and intensi...

tokumaru wrote:

67726e wrote:What are the negatives to this approach?

In my games, each module (which is a separate ASM file) has an initialization area followed by a loop.

That is actually what I was talking about doing.

How do you typically place your start menu in your code? My start menu is just your typical 'Press Start' so I figured I would just put a small loop at the beginning that ends when the user presses start and from then on, the real code is done unless of course the game ends in which case it all just...

I'd say that is kind of iffy. I mean I would very well expect my C++ compiler to make basic optimizations and so I expected the same out of NESASM. I'd never seen anything in the documentation about it so I figured it was one of those trivial little things that the compiler takes care of, but I was ...

The OP asked for the source, and I thought he'd just use the source to privately fix it. Indeed I'm not sure what it's going to take for people to actually sit down and read the documentation that's associated with the tools they use. If the tool doesn't come with any documentation, don't use it --...

When would you not want to use zero-page addressing? I mean so far as I know, wouldn't you want to use fastest solution?

I think it requires you to use special syntax with the Low Byte ( < ) operator. Something like #<$40 or something, but this is just what I remember hearing about that tool. I just use ASM6 and not worry about that kind of stuff. That worked like a charm, although in this situation I was using label...