Re: A86: VAT

To: assembly-86@lists.ticalc.org
Subject: Re: A86: VAT
From: Tim Farrell <tercero@busprod.com>
Date: Fri, 10 Apr 1998 16:14:41 -0700
Delivered-To: assembly-86-outgoing@towerguard.unix.edu.sollentuna.se
Organization: BPS Internet
References: <000601bd6431$a8389ee0$284103cf@joemama.minot> <352E40A8.1ADC054C@eden.rutgers.edu>
Reply-To: assembly-86@lists.ticalc.org


The VAT (Variable Allocation Table) is like an index of the existing variables.  It 
tells only the name, size of name (in characters), type of variable, and where the data 
is in the memory (in 24-bit addressing).  The name is backwards but everything else is 
in it's own TI-defined order.

I took this example from a txt I got off of Cybop's site (tnx to Cybop).

	HEX ASCII
	74 t (The name backwards)
	61 a
	74 t
	53 S
	78 x
	05 (symbol) (Length of name)
	00 (null) (Linking value)
	01 (first byte of absolute addr)
	40 (second byte)
	00 (third byte)
	04 (type of var. -list-)

Hope this helps.

Tercero

Dux Gregis wrote:
> 
> I still don't understand what you mean.  There aren't any programs in the
> VAT, just pointers to all the variables (programs) and the spelling of each
> variable.
> 
> Trey Jazz wrote:
> 
> > >> 3. is everything in the VAT backwards, like all the code in a program?
> > >
> > >What?  Everything in the VAT is backwards (except the addresses, because
> > >they were backwards before that), but there isn't any program code :-)
> >
> > i meant like if the program was just :
> >
> > nop
> > ret
> >
> > if it would store the code backwards as    [218][0]
> >
> > btw does anyone have the compacted opcodes reference? not the hex opcodes
> > but the codes that the ti86 compacts it to to save space?

References:

Re: A86: VAT

From: "Trey Jazz" <joemama@minot.com>

Re: A86: VAT

From: Dux Gregis <assets@eden.rutgers.edu>

Prev: A86: questions
Next: Re: A86: _cpOP1OP2
Index(es):
- Main
- Thread