nesdev.org

Hello,

I started creating a visual studio extension for 6502 syntax highlighting, and I was wondering how useful something like this could be. If it's something everyone wants, I could also try adding solution/project/debugger support. Here is an example showing the syntax highlighting in action:



I'm thinking of making files with the ".s" extension be recognized, then use the Linux style shebang at the top of the file to dictate which syntax to highlight.

great job！

Debugger support would be cool, but how were you planning to do it?

chenyu wrote:great job！

Thanks

thefox wrote:Debugger support would be cool, but how were you planning to do it?

That all depends. If any existing compilers generate a line-to-code mapping file, then I can use one of those, if not then I'll have to make an assembler that can. That aside, I would probably do what is done currently for Android/iOS debugging; build the code and run it in an emulator that communicates with Visual Studio.

Awfully ambitious, but hey, I'd use this. Been looking for a change after over a year of using ConTEXT.

beannaich wrote:If any existing compilers generate a line-to-code mapping file, then I can use one of those, if not then I'll have to make an assembler that can.

The cc65 suite can, if asked to (--dbgfile). It seems to be a little cryptic, though.

lidnariq wrote:

beannaich wrote:If any existing compilers generate a line-to-code mapping file, then I can use one of those, if not then I'll have to make an assembler that can.

The cc65 suite can, if asked to (--dbgfile). It seems to be a little cryptic, though.

cc65 provides a C module that can be used to parse the generated debug information: https://github.com/cc65/cc65/tree/master/src/dbginfo

nicklausw wrote:Awfully ambitious, but hey, I'd use this. Been looking for a change after over a year of using ConTEXT.

I was wondering how much use something like this would see if completed, so this is encouraging.

thefox wrote:

lidnariq wrote:

beannaich wrote:If any existing compilers generate a line-to-code mapping file, then I can use one of those, if not then I'll have to make an assembler that can.

The cc65 suite can, if asked to (--dbgfile). It seems to be a little cryptic, though.

cc65 provides a C module that can be used to parse the generated debug information: https://github.com/cc65/cc65/tree/master/src/dbginfo

Thanks guys, I'll take a look when I get more free time. Hopefully this weekend. I'm thinking of throwing this project on Github and letting everyone contribute