Groups | Search | Server Info | Login | Register
Groups > comp.sys.apple2.programmer > #6331
| Subject | Re: Integrated development on emulators: The next step |
|---|---|
| From | mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) |
| Date | 2025-10-08 13:31 -0400 |
| Newsgroups | comp.sys.apple2.programmer |
| References | <alpine.DEB.2.21.2510080804400.25129@sd-119843.dedibox.fr> |
| Message-ID | <E7GdnaDwY5w9IXv1nZ2dnZfqn_GdnZ2d@giganews.com> (permalink) |
> D Finnigan wrote: > Here's an idea for the Apple II emulator authors: why don't we have > emulators with an integrated assembler? The assembler would produce object > code copied directly in the RAM of the emulated machine. Or the object code > would be copied to a ProDOS or DOS 3.3 disk image. > > Furthermore, why not integrate a C compiler or some other high-level > language? Output options would be the same: the object could would be > written directly to the emulated RAM, ready for execution. Or it could be > copied to a disk image. > > I think that these features would speed up cross-development considerably. > It would be a lot easier to interchange source files with the host > environment, across the Internet, and in version control systems. > > -- > ]DF$ > The New Apple II User's Guide: > https://macgui.com/newa2guide/ You've basically described the dream workflow for a lot of retro developers. Having the edit-assemble-test loop all happen in one environment without swapping files around is a huge time saver. It's awesome that "uso" actually built that functionality in the past with the integrated assembler and dynamic ROM generation. That proves the concept is not just possible, but genuinely useful. The fact they're thinking about extending it now with other content like Gameware and FPBASIC is really promising. It sounds like the groundwork is already there for someone to pick up and run with. The real power, like you said, is in bridging the old and new. Being able to use modern tools like Git for version control on your source files, then seamlessly compiling and injecting the code directly into the emulator's memory or a disk image, is the best of both worlds. It keeps the classic feel of the machine but removes all the friction of the original development process. I hope "uso" or someone else inspired by this picks up the torch. This is exactly the kind of feature that could become a standard for the next generation of emulators. This is a response to the post seen at: http://www.jlaforums.com/viewtopic.php?p=697217128#697217128
Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
Integrated development on emulators: The next step D Finnigan <dog_cow@macgui.com> - 2025-10-07 14:47 +0000
Re: Integrated development on emulators: The next step Steve Nickolas <usotsuki@buric.co> - 2025-10-08 08:09 -0400
Re: Integrated development on emulators: The next step mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) - 2025-10-08 13:31 -0400
Re: Integrated development on emulators: The next step Steve Nickolas <usotsuki@buric.co> - 2025-10-08 20:36 -0400
Re: Integrated development on emulators: The next step Speccie <someone@somewhere.com> - 2025-10-09 08:07 +0100
Re: Integrated development on emulators: The next step Hugh Hood <hughhood@earthlink.net> - 2025-10-09 10:44 -0500
Re: Integrated development on emulators: The next step Speccie <someone@somewhere.com> - 2025-10-10 08:01 +0100
Re: Integrated development on emulators: The next step D Finnigan <dog_cow@macgui.com> - 2025-10-14 19:14 +0000
Re: Integrated development on emulators: The next step kegs@provalid.com (Kent Dickey) - 2025-10-08 19:38 +0000
Re: Integrated development on emulators: The next step D Finnigan <dog_cow@macgui.com> - 2025-10-14 19:18 +0000
Re: Integrated development on emulators: The next step Hugh Hood <hughhood@earthlink.net> - 2025-10-15 23:28 -0500
Re: Integrated development on emulators: The next step kegs@provalid.com (Kent Dickey) - 2025-10-20 19:05 +0000
Re: Integrated development on emulators: The next step Noncho Savov <user10020@newsgrouper.org.invalid> - 2025-10-26 20:49 +0000
csiph-web