Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!ucbvax!USU.BITNET!SLMYQ
From: SLMYQ@USU.BITNET
Newsgroups: comp.sys.amiga.tech
Subject: Re: Possible BLINK bug????
Message-ID: <8804100045.AA12398@jade.berkeley.edu>
Date: 10 Apr 88 00:37:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 20

>>When you use SMALLDATA and have a few data chunks that are supposed to go into
>>chip memory and a few that don't need to, it just sticks them both together
>>into one big chunk that must go into chip memory.  I really don't want to
>>have 50K of stuff in chip memory which really doesn't need to be there.  And
>
>This is not a bug.  It's a byproduct of SMALLDATA itself.  When you use the
>SMALLDATA option, you are telling BLINK to make sure all your data is within
>64k of a base pointer.  You can't keep the data within the limit if you split
>it up between CHIP and FAST ram.  Sorry, that's just the way it is.

I see.  However, what I *really* want is just to have all data of the same type
put into big data hunks - that will make the object size smaller, won't it?
I don't need everything to be next to each other.  Maybe you could stick in
another switch which would be somewhere between SMALLDATA and "BIGDATA".  It
would coagulate all data hunks OF THE SAME TYPE, and I think that's what most
programmers like me need.

Glad to hear it's not a bug. :)

                                Bryan Ford (SLMYQ@USU.BITNET)