Re: SAOL tokenisation

From: John Lazzaro (lazzaro@cs.berkeley.edu)
Date: Tue Jan 30 2001 - 13:42:10 EST


> In the Bitstream token table of the 'Structured Audio' specification there
> are
> two values for the 'buzz' keyword (0x7C and 0xB5). Is this a documentation
> error?
> Which one should I use.

0x7C is the buzz wavetable generator, 0xB5 is the buzz opcode

> Am I free to encode a
> source constant value
> with (for example) a value of 1 with either of these methods?

I've assumed that you don't want to encode a float where an int is
syntactically required (i.e. array size declarations and such) but
that the reverse is OK and good practice for file-size reduction.
When sfront encodes files, it first builds a complete parse tree
as if it were translating to C, and part of this parse-tree build
is the lexical analysis, which parses numeric constants into S_INTGR
or S_NUMBER types depending on the format of constants ... see
mp4write.c, line 178, in the sfront sources to see the actual SAOL
encoding for the numeric types (actually, it starts at line 268).

                                                                --jl

-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------



This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 11:46:42 EST