Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: D Finnigan Newsgroups: comp.sys.apple2.programmer Subject: Re: need help identifying tokenized assembler file format Date: Mon, 19 Feb 2018 02:37:26 -0000 (UTC) Organization: Mac GUI Lines: 20 Message-ID: References: <38888b53-6c12-43c7-bba0-294a23fc7e0d@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 19 Feb 2018 02:37:26 -0000 (UTC) Injection-Info: reader02.eternal-september.org; posting-host="48c576059e09d5f252311a0310421b01"; logging-data="30950"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+4dGAFbxtGeslAF4e8eJWd" User-Agent: Mac GUI Usenet In-Reply-To: <38888b53-6c12-43c7-bba0-294a23fc7e0d@googlegroups.com> Cancel-Lock: sha1:ohFMu4f2UbRbwuhwOZ4+5cKOdrY= Xref: csiph.com comp.sys.apple2.programmer:4241 aycock wrote: > I'm trying to identify the assembler that used a specific file format for > source code. The assembler would've been in use in early 1980. > > In this format, lines are separated by $d (CR) characters. The byte > following the $d is the line length. Opcodes are tokenized - not > completely > sure how yet - but their high bit's always set. [...] > Does this ring any bells for anyone? Might be LISA. Documentation here: http://macgui.com/spyglass/r/2dc6023fc6ac0b2b -- ]DF$ The New Apple II User's Guide: http://macgui.com/newa2guide/