INTL 3:770/1 3:770/3
REPLYADDR none@invalid.com
REPLYTO 3:770/3.0 UUCP
MSGID: 2eb8a4fc
REPLY: 72e96c36
PID: SoupGate-Win32 v1.05
On 23/08/2024 10:17, The Natural Philosopher wrote:
> On 22/08/2024 11:57, Ahem A Rivet's Shot wrote:
>> On Thu, 22 Aug 2024 11:00:26 +0100
>> Single Stage to Orbit wrote:
>>
>>> FAR and NEAR specifiers used with JMP
>>
>> The obscenity was these qualifiers making their way into C source
>> code - try writing (or even reading) the declaration for a near
>> pointer to a
>> function returning a far pointer to an array of functions returning near
>> pointers to integers.
>>
>> Then realise that you *also* wanted this source code to be portable.
>>
> I don't recall them ever appearing in C source. They are not part of the
> C language.
> AIR you could compile for 'small model' or 'large model'
>
> And with the early compilers I used, no attempt was made to think about
> whether a jump was near or far.
>
> I think you got an assembler or linker error if a target was 'out of
> range'
>
>
No I remember the joy of using NEAR and FAR in C for 8086 code. I can
remember being forced to use them in zORLAND C/Zortech C++ and Borland C
on 8086 code for PCs running DOS and in embedded 80186EB code.
https://www.geeksforgeeks.org/what-are-near-far-and-huge-pointers/
https://en.wikipedia.org/wiki/Digital_Mars
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757
SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
