🚀 go-pugleaf

In article <767@lakesys.UUCP>, jason@lakesys.UUCP (Jason) writes:
> 
> 	Just for kicks and giggles, why would anyone want elements/structures
> that were >32k? Or, put differently, what's in it? Huge arrays? (Or 16384
> ints? :)

You must be joking, or maybe your are just new to programming.  Yes the
problems I ran into in school could be sloved with very small amounts of
memory.  After all when there are 300+ people using a 1000% overloaded 
mainframe just how complex can you make the problems. :-)

Anyway here is a few that can require more than 32K access in arrays:

           1) Zbuffer for 3D graphics
           2) data logging 
           3) look ahead calcuation done to increase speed
           4) speed sheets
           5) decent word processor
           6) music
           7) ram disk
               on and on

Almost any type program can benefit from the "EASY" access of memory.  When
one has a high level compiler why should he have to worry about array sizes
as long as there is enough real memory.

                                       Wayne Knapp