What programming environments are you using?

[pixel]

I use the 'xa' assembler and VICE on Linux. But meditative debugging is starting to do my head in. I guess that's the main problem for people to start assembly, isn't it? What do you use?

[Vic20-Ian]

CBM Basic V2.0

[groepaz]

never felt the need for more than the vice monitor when it comes to debugging... its pretty poweful infact.

[Misfit]

MacBook Pro + Editra (text editor) + cc65 + ca65 + VICE. I don't use any debuggers.

[FD22]

DASM, Notepad++ and VICE.

[Jeff-20]

The real thing. A vic 20 with sd card storage because actual cassette tapes are getting rare.


Sent from my iPhone 6 Beta using Tapatalk

[beamrider]

Windows, Ca65, Notepad++ & Vice mainly. Also used vic20 emu a couple of times as it has a nice (if slow) profiler. I use excel and c# as source code generation tools as well to generate lookup data etc. Also cmrprg studio for graphics.

Sent from my Nexus 5 using Tapatalk

[pixel]

never felt the need for more than the vice monitor when it comes to debugging... its pretty poweful infact.

Just saw the CBM prg Studio 3.0 announcement – missed the feature to import labels and breakpoints into it. Gonna have my wetware debugged, soon. m(

[bills442]

I use the 'xa' assembler and VICE on Linux. But meditative debugging is starting to do my head in. I guess that's the main problem for people to start assembly, isn't it? What do you use?

I know the WinVice monitor is probably super powerful, I never learned/bothered to use the 'symbol table' feature in it which would allow quick inspection of all your zero page stuff ; however, I kinda agree with you. It seems like it would be so straightforward to build a 'source level' debugger -- especially with one of the VIC emulators. Something that would take the assembler listing file and allow single stepping through it. All it would have to do is take the address on the program counter and run a cursor through a text file -- throw in some cool hover and inspect features like a modern IDE.

Now, don't get me wrong, I love moments of nostalgia too. There are times when I love pen and paper and scratching your head and pretending it's 1982 -- it's fun,BUT, there are other times when you are in it for the thrill of programming the VIC as a 'target' platform and not for the nostalgia of it , and that's when you want the best possible tools.

I dunno -- I've got so many silly projects I want to do and not enough time with my day job always getting in the way , but some kind of 'source level' debugger to alleviate the meditative debugging you mention would be of interest to me. I've been looking for an excuse to do a project in Clojure

[pixel]

I dunno -- I've got so many silly projects I want to do and not enough time with my day job always getting in the way , but some kind of 'source level' debugger to alleviate the meditative debugging you mention would be of interest to me. I've been looking for an excuse to do a project in Clojure

Ouhjah! A full-blown IDE in the emulator would be nice. What puts me off is that most software (including VICE) is written like we're still in the 80s there, too. So I banged my own assembler together which generates that VICE symbol files and gives me a WAV file right away. (Need to hunt hardware to check this on real VIC in a minute.) It's a joke to do that in Lisp. But a good one. Still no IDE, though.

The most easy way to do it IMHO would be to grab the JavaScript VIC emulator and hack an IDE in. No cross-platform UI issues there and other comfy things like garbage collection and DOM instead of Un*x terminal foobar or whatever complicated things. Close enough to Lisp, isn't it? And there'd be no heavy weights to lift for beginners. Just open the browser and get going...

[rhurst]

Debugging with the modern emulators is trivial. Your assembler needs to provide symbol tables, like ca65.

[Kweepa]

What pixel is suggesting is a step beyond that mess of symbol files and obscure typed commands.

[Witzo]

Aart Bik's crossassembler on the Mac command line, http://www.aartbik.com/MISC/c64.html, with TextWrangler as editor and VICE as emulator. And Disk Imagery http://lallafa.de/blog/c64-projects/diskimagery64/ for the odd d64 edit.

[TBCVIC]

Check out SublimeText3 for text editor (Windows), it's really good. You can create your own modules for coloring and highlighting keywords and such.

[rhurst]

What pixel is suggesting is a step beyond that mess of symbol files and obscure typed commands.

I got that, really, but the keyword I use here is trivial, which is relatively speaking. After all, I'm old school, so to me it's trivial compared to what we had then.

[youtube]QX9NkF0Tc9E[/youtube]

So if you ask me, you're all soft.