I once bought Zortech C for the price of a new PC just because it promised 
easy access to large memory chunks, so I could address the whole 16MB of 
memory the PC had. A broken promise, btw...

Well, thoses were the times of Turbo C, Turbo Pascal, 20 MB harddisks and 1 
MHz processors...

BTW: my first computer was a VIC with a whole 5 kB main memory. To draw 
complex graphics (like a monochrome sine curve ;-) you had to fill the video 
memory with a sequence of ASCII chars, map the dot-matrix for those chars 
(8x16 dots) to memory, and then redefine the respective rectangular 
dot-matrices so that a graphical output would happen. If you have done this, 
everything windows throws at you is just a minor nuisance ;-)

"Darren New" <dne### [at] sanrrcom> schrieb im Newsbeitrag 
news:4a7227fe$1@news.povray.org...
> Warp wrote:
>> clipka <nomail@nomail> wrote:
>>> Just as you cannot rely on the char type to be an 8-bit integer. Or 
>>> pointers to
>>> be of the same size as long int, for that matter.
>>
>>   Or all pointers having the same size.
>
> Well, that's been the case for different memory areas for a long time. 
> Near vs far pointers, at least.  I guess folks don't remember way back in 
> the bad old days of x86 any more. :-)
>
> -- 
>   Darren New, San Diego CA, USA (PST)
>   "We'd like you to back-port all the changes in 2.0
>    back to version 1.0."
>   "We've done that already. We call it 2.0."

Post a reply to this message