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: Re: Integrated development on emulators: The next step Date: Tue, 14 Oct 2025 19:18:02 -0000 (UTC) Organization: Mac GUI Lines: 20 Message-ID: References: <10c6ejt$1qvka$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 14 Oct 2025 19:18:04 +0000 (UTC) Injection-Info: dont-email.me; posting-host="afcd13583c0682a10d6bba7dd27eb390"; logging-data="3336442"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/UqEQNOS1RxH1pSfCs0hN5" User-Agent: Mac GUI Usenet Cancel-Lock: sha1:OPsco/1VOGHQ2vTYd7NR1DEgGPM= In-Reply-To: <10c6ejt$1qvka$1@dont-email.me> Xref: csiph.com comp.sys.apple2.programmer:6338 comp.emulators.apple2:3911 Kent Dickey wrote: > > Most emulators allow easy loading of external files into memory, and > this can be scripted. So you build on your host machine, then load > the binary into the emulator. > That's true, and that would be a good starting point for some extensions to aid development. But imagine a closely-coupled assembler where you could set a breakpoint in the source file, and then start the emulated machine running. As soon as execution reaches that breakpoint, there is a marker in the source, and you can single step through the object code and see all register values, etc. No more tracing through the Monitor, instead you trace through your assembly source. -- ]DF$ The New Apple II User's Guide: https://macgui.com/newa2guide/