Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.apple2.programmer > #4239 > unrolled thread

need help identifying tokenized assembler file format

Back to article view | Back to comp.sys.apple2.programmer

Contents

  need help identifying tokenized assembler file format aycock@ucalgary.ca - 2018-02-18 13:50 -0800
    Re: need help identifying tokenized assembler file format kelvin@pro-kegs.uucp (Kelvin Sherlock) - 2018-02-19 02:00 -0500
    Re: need help identifying tokenized assembler file format D Finnigan <dog_cow@macgui.com> - 2018-02-19 02:37 +0000
      Re: need help identifying tokenized assembler file format Antoine Vignau <antoine.vignau@laposte.net> - 2018-02-18 18:57 -0800
    Re: need help identifying tokenized assembler file format Fred Smith<fredsmith@thejanitor.corp> - 2018-02-19 03:18 +0000
      Re: need help identifying tokenized assembler file format Andy McFadden <thefadden@gmail.com> - 2018-02-23 08:19 -0800
    Re: need help identifying tokenized assembler file format aycock@ucalgary.ca - 2018-02-19 08:58 -0800

#4239 — need help identifying tokenized assembler file format

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. Following an opcode is a one-byte value that appears to indicate the operand type: 0=implied, 1=label, 2=immediate, 5=(ZP),Y. Operand text and comments are simply ASCII, without the high bit set.

For example, a fragment might be

0d 02 3b
       ;
0d 0a cd 05 28 46 4f 4f 29 2c 59
      op     (  F  O  O  )  ,  Y
0d ...

Does this ring any bells for anyone?

Thanks!
John

[toc] | [next] | [standalone]

#4240

Sounds like LISA.  CiderPress can detokenize it. The source code might
be the only extant documentation:
https://github.com/fadden/ciderpress/blob/master/reformat/Asm.cpp


In <38888b53-6c12-43c7-bba0-294a23fc7e0d@googlegroups.com>
aycock@ucalgary.ca writes:

>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. Following an opcode is a one-byte
>value that appears to indicate the operand type: 0=implied, 1=label, 2=i
>mmediate, 5=(ZP),Y. Operand text and comments are simply ASCII, without the
>high bit set.
>
>For example, a fragment might be
>
>0d 02 3b
>       ;
>0d 0a cd 05 28 46 4f 4f 29 2c 59
>      op     (  F  O  O  )  ,  Y
>0d ...
>
>Does this ring any bells for anyone?
>
>Thanks!
>John

-------
ProLine: kelvin@pro-kegs

[toc] | [prev] | [next] | [standalone]

#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/

[toc] | [prev] | [next] | [standalone]

#4242

Yes, Lisa.

[toc] | [prev] | [next] | [standalone]

#4243

On 2018-02-18, aycock@ucalgary.ca <aycock@ucalgary.ca> 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.

If you really mean early 1980, not "early eighties" then that's
before the Lisa. Could it be the Assembler that came with Apple
Pascal? That also used a CR line break, and I think influenced
Lisa development.

[toc] | [prev] | [next] | [standalone]

#4245

On Sunday, February 18, 2018 at 7:18:23 PM UTC-8, Fred Smith wrote:
> If you really mean early 1980, not "early eighties" then that's
> before the Lisa. Could it be the Assembler that came with Apple
> Pascal? That also used a CR line break, and I think influenced
> Lisa development.

Just to be clear, it's LISA (Lazer Interactive Symbolic Assembler), not the Apple Lisa computer.

From the CiderPress LISA v2.x sources:

/*
 * Format:
 *  2-byte version (?)
 *  2-byte length
 *  <LINE> ...
 *
 * Each line is:
 *  1-byte length
 *  <DATA>
 *  CR
 *
 * Last line has length=255.
 */

which sounds like the same thing.

[toc] | [prev] | [next] | [standalone]

#4244

Thanks, everyone! The original release of this program was 1980, which is why I didn't consider Lisa, but the image I have could be from a later release (and re-assembly). I was able to reverse the token values for the source code fragments I have - off to compare to Lisa...

John

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.apple2.programmer

csiph-web