Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com
From: Ed Federmeyer <fedeedw@charlie.cns.iit.edu>
Newsgroups: scea.yaroze.beginners
Subject: Yaroze philosophy
Date: Wed, 23 Apr 1997 20:07:58 -0500
Organization: (no organization)
Lines: 15
Message-ID: <335EB26E.19A3@charlie.cns.iit.edu>
Reply-To: fedeedw@charlie.cns.iit.edu
NNTP-Posting-Host: charlie.cns.iit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0C-GZone  (Win95; I)

I've been looking at the demos, and one thing that seems very common
to me is that people use siocons to load data chunks (TIM, VAB, etc)
into "hard coded" locations, and then use #define VAB_ADDR 0x8011000
type definitions to let the run-time code know where they are.

Wouldn't it be easier to include a big array in the code, (ie,
convert the binary datafile into a big, "C" array, like using
tga2img.exe) with the appropriate size, and then just refer to
&array[0] (or just "array" of course) in the code, and let the linker
figure out where it should go?

I'm not sure if I'm missing the benefit of the multiple load
method.

Ed Federmeyer