Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Johann Klasek - swap last two domainparts" Newsgroups: comp.lang.forth Subject: Ragsdale Forth assembler history Date: 29 Jul 2026 21:50:45 GMT Lines: 27 Sender: Johann Klasek Message-ID: X-Trace: individual.net bHWUhCqSwvMZdBPDBPFsZQyOn/dWcdrmanRyyjS1zST3S2g3PO Summary: forth assembler history Keywords: forth, history, assembler, 8bit X-Orig-Path: not-for-mail Cancel-Lock: sha1:BuwQYYS+gCiAIalKpCqtaF01hpA= sha256:FGIlBGBzC3LiHLcqwjyQWIHVjS0qC9AvWdCkeknl0XE= User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (Linux/2.6.22.14-72.fc6 (i686)) User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (Linux/2.6.22.14-72.fc6 (i686)) Xref: csiph.com comp.lang.forth:135280 Hi folks, sometimes ago (2012) I did some re-work on a 65C02 assembler derived from the well known Ragsdale Assembler published in c't magazin, 1984/01, p. 72, "65C02 Assembler in FORTH". The aim was to support WDC commands (not just those from Rockwell). In addition to a number of performance improvements (which were due to shortcomings in the Ragsdale code), several new features were introduced: certain structure commands, as well as loop or conditional blocks, can now (using the word `FAR') span code sections of more than 127 bytes. Recently, in 2026, a number of further changes were made to improve runtime performance. https://klasek.at/forth/ also covers a number of other Forth topics, though the main focus there is on assemblers and disassemblers. My test environment is a C64 Forth/79 from Performance Micro Products, but I don't think porting it would be a problem (at least on little- endian platforms). Happy Forth-coding JEEK