| Author |
Message |
z5_
Member |
Are there some neat tips and tricks we should know about asm-one?
I have a couple of questions allready:
- are the commodore includes distributed with asm-one?
- is there a possibility to run a project from within asm-one (everytime i have to test something, i assemble it and write it to an object, then drag down my asm-one screen, search for the icon on my workbench and run it from there, which is pretty annoying)?
|
noname
Member |
1.) includes come seperately iirc since later version of asmone where kind of free whereas the includes are copyrighted. commercial assemblers (devpac, oma, original asmon) would probably come with includes. you just can't buy them anymore. so get the includes from a copy of devpac.
2.)
a<Enter>
j<Enter>
|
z5_
Member |
great :)
Another question: why can't i use the numbers on the "numpad"?
|
kufa
Member |
Go to preferences/assembler, and change the numlock settings :)
|
z5_
Member |
ok, i guess i should shut up and examine asm-one a bit before asking such questions :)
|
z5_
Member |
Let's assume i have two sources open: source A and source B.
Source B is included in source A and source A is my main loop. It calls a subroutine in source B (bsr).
If i make a change to source B, how can i reassemble source A and B in one go. If i make a change to source B and write it to disk, close source B, go to source A and assemble A, it doesn't reassemble source B, or so it seems. Which is very annoying. What is the best way to handle two sources in Asm-One.
|
bonkers
Member |
zi - zapp includes and then re-assemble, it will reload all the includes.
|
dalton
Member |
you could also use the INCSRC directive. At least that's comfortable when you have lots of includes. If you include with incsrc # you don't have to reload the include with ZI, but it must be open while you use it.
|
bonkers
Member |
@dalton: I think one should avoid using INCSRC as it's quite tricky to remeber what screen each source belonged to after a crash.
|
dalton
Member |
@bonkers: good point
another tip: the as# directive is very practical when you use multiple sources. My typical compiling sequence looks like this: u / as0 / zi / a / j
|
StingRay
Member |
Why avoid INCSRC? Use all the features your assembler has. :) I use it quite a lot for quick tests and stuff and it can save you quite some time.
Dalton: real coders don't even know what 'u' does, they start their stuff w/o updating. :) Well, at least I do it this way. =)
a/j is all you need. :)
|
