Path: csiph.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: D Finnigan Newsgroups: comp.sys.apple2.programmer,comp.emulators.apple2 Subject: Integrated development on emulators: The next step Date: Tue, 7 Oct 2025 14:47:12 -0000 (UTC) Organization: Mac GUI Lines: 19 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 07 Oct 2025 14:47:16 +0000 (UTC) Injection-Info: dont-email.me; posting-host="b25abdbddfdb6a1d843471a83e4a07c5"; logging-data="1075966"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/q8/wyWix2OQK6DeOMF4Ya" Summary: Apple II emulators with integrated assembler User-Agent: Mac GUI Usenet Cancel-Lock: sha1:uRZJWqMoDyhIoXtvlKn0EyjPxGk= Xref: csiph.com comp.sys.apple2.programmer:6329 comp.emulators.apple2:3908 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/