nesdev.org

Bregalad wrote:I guess the same with MTE could be as well compressed than huffmann (but the decoding table would be larger) and is much, much easyer to use.

Bregalad wrote:The problem of your DOS program isn't the usage, it doesn't run at all (when I type huffpuff, the DOS command answer "Not executable programm" or something like that).

Bregalad wrote:So a structure/union is a kind of buffer in the C language, but your assempler seems to do a mix between C and ASM and it's not easy to got it.

Bregalad wrote:Also, annonymous macros doesn't work at all, and I've done them exactly as in the exmple (the like i=0 render an error)

SnowBro wrote:How exactly is MTE easier to use? As long as you have automated tools to encode and decode data, there really isn't any difference as far as actual usage.

Structures/unions have the same semantics in my assembler as in C, to the best of my knowledge. But nobody's forcing you to use structures, and if you've gotten by without them before perhaps it's best to carry on like before. If you're on IRC or MSN, we could try having a more interactive session though, I bet that would clear up things a lot faster than using this messageboard.

Strange. I just assembled both examples without problem. Are you using the latest version of the assembler (1.4.5)? Could you give the precise error message?

Concerning the debugging-related problems of data/code relocation. If you give the --verbose option to the linker, it will print out the final physical address of each public symbol in your code, which should be of some help. But again, you can just use .EQU directives to map your RAM to avoid the automapping altogether.

tepples wrote:

Anonymous wrote:No, at the moment there's really no difference between "proc" and a normal label. However, I have fun ideas for it, such as being able to inline a function defined in another unit, or the linker being able to extract a single procedure from one unit, as opposed to having to link in the whole unit.

Sounds like .ifref in .CA65. In addition, CA65's .proc allows for procedure-local labels. Do you plan on adding that?

For example,

Code: Select all

.pad $FFFA - $

simulates absolute padding to $FFFA.
Perhaps I should just change ".pad XXXX" to mean ".dsb XXXX - $"

Such a change would at least help maintain consistency with x816. CA65, on the other hand, prefers that the linker script put a 6-byte "vectors" section into the ROM_C000 bank.

But I think records are a life-saver for user-defined bitfields, and especially the ability to initialize the fields like a normal structure and have the assembler do the tiresome shifting, ANDing and ORing for you. Check out "warp2d.h"; back in the old days I had to generate the packed bytes of (area, section, location) manually

If your assembler can handle the | operator, you don't need it. Define the masks in a header file, and OR them together in your constant data. Even better is to make a custom graphical editor for each data type, separate from your assembler.

I'm using Huffman coding for my text

I've read in Managing Gigabytes that a technique called "huffword", where each Huffman code maps to a word, provides good compression.

You can define a label to point to WRAM:

Code: Select all

.label wram = $6000

But you can't map an entire data segment to a specific location.

CA65 can.

However, you can use a structure, since a structure's field are guaranteed to be mapped sequentially in memory.

In fact, I use a technique like this in my GBA headers.

Thank you, I'm the only one who's used the assembler up until now I'm pretty sure, so I'm glad for all feedback on how others see it.

What do you plan on making your assembler do that CA65 doesn't already do?

Dwedit wrote:Am I the only person to notice that the example game's logic allows jumping in midair as long as your vertical velocity is zero?

tokumaru wrote: I guess you gotta have a flag to tell if the player is in the air or not...

Bregalad wrote:You probably already have to have one, scince your player most probably don't have that same animation frame in air than on the ground. So a such flag is needed when checking witch animation frame should be used to draw the player.

I can't find these files in the internet either!