Groups | Search | Server Info | Login | Register


Groups > comp.sys.apple2.programmer > #6329

Integrated development on emulators: The next step

Path csiph.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From D Finnigan <dog_cow@macgui.com>
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 <dog_cow-1759848430@macgui.com> (permalink)
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

Cross-posted to 2 groups.

Show key headers only | View raw


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/

Back to comp.sys.apple2.programmer | Previous | NextNext in thread | Find similar


Thread

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