🚀 go-pugleaf

In article <1992Nov5.031544.5264@sequent.com> furballs@sequent.com (Paul Penrod) writes:
[stuff deleted]

>Almost right, but you forgot something.
>
>In your data declarations, if you do not specifically specify the
>keyword far, then the declaration is left in the default data
>segment, which can be a problem if you have more than 64k of global
>data. Granted, DS is referenced by a far pointer, but you are still
>limited to 64k per data segment, eventhough you can reference upto
>1 megabyte of data and 1 meg of code. This is because the far
>pointers in the LARGE model are not normalized 32 bit, but
>segment:offset 20 bit pointers. 
>
>...Paul
>
I am writing my first app, and I am using large model (BC++ 3.1). I haven't
used either 'far' or 'FAR' so far.  I have just let pointers default to far as
provided by the large model.  Ok, presumably I will eventually hit the
64k limit for data in my app sooner or later.  What do I do then?
Are you saying I can get more than 64k data storage by explicitly using the
'far' declaration?  Does that give me 'another' 64k data segment?

John A. Grant
Geological Survey of Canada