Originally posted by Alcaro
Yes, I know those are files. It doesn't matter which file you use for this, Asar will just ignore it.
Some generic existing file is probably easier since you won't need to care about Windows vs Linux.
Some generic existing file is probably easier since you won't need to care about Windows vs Linux.
It's probably an irrelevant subject, but do you mean that the program won't need to care, or the user won't. It's probably best as a command line option if you just want to use a consistent name.
I was under the impression you could give it a device and the program would just happily read from and write to the device as if it was a file without special internal handling, but I am not sure. If that were true, it would work already.
Originally posted by Alcaro
Inserting binary files is indeed stupid. I think all spritetool tells the assembler where to place the file, but I'm not entirely sure. (BTSD seems to insert binary files.)
Romi's reinserts everything, which takes a minute for larger ROMs. I never checked Tessera, but something tells me that feature is missing there too.
(I'm not sure if I like the idea of an all-in-one sprite inserter either, but that's irrelevant.)
Random note: Just like it is indeed easier to offload everything to Asar, it is also easier to reinsert all files than checking timestamps. People will often use the easiest solution, even if it isn't the best.
Romi's reinserts everything, which takes a minute for larger ROMs. I never checked Tessera, but something tells me that feature is missing there too.
(I'm not sure if I like the idea of an all-in-one sprite inserter either, but that's irrelevant.)
Random note: Just like it is indeed easier to offload everything to Asar, it is also easier to reinsert all files than checking timestamps. People will often use the easiest solution, even if it isn't the best.
I am pretty sure romi's at least and I think Tessera as well assemble to a temp file to find the size first at least. And really, if your doing that, why not just insert the temp file instead of running the emulator again? Though I am honestly not sure if they do.
Originally posted by Alcaro
I think you've misunderstood something. Both dynamic and static libraries can offer various functions for each other to call. External programs offers only more convulted communication methods (you can hijack stdin and stdout, but that could get annoying).
Either way, making external programs are easier for me (I don't know how to declare that a function should be visible to a DLL, nor do I know how to load one). Sending instructions through stdlib.asm and parsing stdout is good enough for me.
Either way, making external programs are easier for me (I don't know how to declare that a function should be visible to a DLL, nor do I know how to load one). Sending instructions through stdlib.asm and parsing stdout is good enough for me.
To be honest, my experiences with this type of thing tends to involve monolithic parser classes/functions that end up doing most of the work, and lots of little utility functions that don't do much that is useful on there own. I just assumed a dynamic library would end up being a fancy wrapper to some "assemblethis()" function. It would still be useful for file IO stuff but it doesn't really seem to offer much more flexibility. I havn't looked into it much.
Originally posted by Alcaro
...do we have any reason to follow the official documents?
Besides, I wouldn't trust a document that uses bits everywhere instead of bytes for use as toilet paper.
Besides, I wouldn't trust a document that uses bits everywhere instead of bytes for use as toilet paper.
It's most likely not following the official documents is the reason why there are so many opcode lists in the first place. Though I would expect byuu's to be pretty close.
Originally posted by Alcaro
Yes, you have an LDA.l <label>,x there, which the HTML filter doesn't seem to like. I fixed it for you.
I run into the same problem sometimes when I post a code containing for (int i=0;str[i];i++) str[i]=tolower(str[i]); or something like that.
...though I can't claim to have run into <label> before.
I run into the same problem sometimes when I post a code containing for (int i=0;str[i];i++) str[i]=tolower(str[i]); or something like that.
...though I can't claim to have run into <label> before.
Ugh, I forgot all about that.
Your layout has been removed.