tepples wrote:My current project makes use of ca65 features such as .proc (labels scoped to a procedure, for local variables in low zero page), .repeat (loop unrolling without copy and paste), and .enum (namespaced constants). How do you plan to handle things like these in NESICIDE's assembler?
I'm planning on implementing a macro system very similar to how NASM works. After that, I'll take suggestions on what can be added to make life easier for NES deving. Procedure-level label scopes will definitely be in. Loop unrolls of course will be in. .enum sounds sorta like a struct system. I plan on supporting enums and structs in the macro system. The assembler is finished, all of the higher level 'niceties' will be the responsibility of the preprocessor -- but I know what you are saying.
tepples wrote:And is NESICIDE intended to be lightweight enough to run on my laptop? (It has 1024x600px screen, 512 MB of RAM, 900 MHz Celeron CPU, and Ubuntu 9.10.)
Right now, most likely not (in its current state) -- although it seems to run the fastest in linux (compared to Windows and OSX currently). Though right now chris is in the process of importing all of the inspectors, and all of the debuggers are running full steam. Once the debuggers are all ported over (he's done 4 so far), we will toggle the callbacks so that if a debugger is not visible, it will not eat CPU. Aside from that, we run profillers to try to trim down on execution time. If, after we get those debugger toggles in it still runs too slow for you, by all means let us know and we'll work to get things sped up. A celeron processor is pretty weak (regardless of how new it is) due to it's itty bitty cache, but it should be at least usably fast (again, after the debugger toggle logic gets added). If not, we'll have more work to do
