Editor 64 in Assembly - - Syntax?????

[AAGDOS]

All,

I now have the "C64 Macro Assembler Development System" in the original Commodore Package with Manual and Disk.

I am embarrassed to ask this,...., but what is the Syntax for lines entered into Editor64???? I am getting just
"?Syntax Error". Nothing is shown in the Manual.

I load it as shown in the Manual and then SYS to start it running...e.g.

Load "Editor64",8,1
SYS49152

and get
Commodore 64 Editor V072982
(c) Commodore 1982 By Commodore Business Machine

Then if I type in....
Loop INC $D020 and <return>
?SYNTAX ERROR

or typing in....
LDX #$41
?SYNTAX ERROR

It works fine with the Monitor$8000 from the same disk....
.A 1400 LDA #$01

This is ok for tiny check out programs, but not good for my (pending) larger codes!

Any guidance would be MUCH appreciated!

Thank you.

 

[AAGDOS]

Editor64 Syntax ? Any Clues?

I am watching my earlier post and see a number of "views", but no "replies" w/ thoughts yet. If you know anything about this please post. Thank you very much.

I have 2 older books on C64 Assembly pending from eBay, and hope there is some further explanation!

I have also written a number of smaller codes with Monitor$8000. These have worked fine!

Thank you.

 

[KC9UDX]

It's been a while, but if memory serves, you are just missing line numbers. Lines are numbered just like a Commodore BASIC program. But don't worry, you won't end up with spaghetti code: the line numbers are just for the sake of the editor; they're not part of your code.

 

[rittwage]

I had that package when I was a teenager and I think it set me back years in learning Assembly. It was horrible and the documentation was unclear or non-existent.

 

[AAGDOS]

Editor64 - Syntax - Resolved

Thank you all for the comments. I just received the book "Commodore 64/128 Assembly Language Programming" (by Mark Andrews). There is a description on PP 60-62 on loading and running the Editor64 program with notes on "spacing". Apparently the Commodore is "very fussy about spacing", with 1 space between the line number and the label, and 2 spaces between the line number and the op code. Who would have thought!

So now my program is written and saved to disk!

 

[KC9UDX]

Rigid spacing requirements weren't uncommon in assemblers at that time. Other programming languages, too.