A89: Re: arrays...

To: <assembly-89@lists.ticalc.org>
Subject: A89: Re: arrays...
From: "Miles Raymond" <m_rayman@bigfoot.com>
Date: Mon, 26 Jul 1999 15:33:38 -0500
Delivered-To: assembly-89-outgoing@towerguard.unix.edu.sollentuna.se
Delivered-To: assembly-89@lists.ticalc.org
Organization: Expert Internet Services
References: <d2dbc031.24cde730@aol.com>
Reply-To: assembly-89@lists.ticalc.org


You allocate the space with the dc.x op code.  The number after it is just
what is stored in that space.

So in effect, both are lists of one byte, but they are different in that:
(displayed in TI-BASIC for simplicity)

array1 = {1}
array2 = {0}

-Miles Raymond      EML: m_rayman@bigfoot.com
ICQ: 13217756       IRC: Killer2        AIM: KilIer2 (kilier2)
http://www.bigfoot.com/~m_rayman/

----- Original Message -----
From: <S43R80@aol.com>
To: <assembly-89@lists.ticalc.org>
Sent: Monday, July 26, 1999 11:30 AM
Subject: A89: arrays...


> This is probably a dumb question, however, I am curious about defining
> arrays...I mean if you do something like:
> array1 ds.b 1
> then it will allocate (is this the right word?) 1 byte of space at
location
> (array1)...
>
> but how come if you do:
> array2 ds.b 0
> it will still allocate 1 bytes...doesn't it literally mean "define 0 bytes
of
> space"?...how come this works then...or am i just interpreting it
wrongly???
>
> -Steve

Follow-Ups:

Re: A89: Re: arrays...

From: Olle Hedman <oh@hem.passagen.se>

References:

A89: arrays...

From: S43R80@aol.com