Re: 16:32 far pointers in OpenWatcom C/C++

From	Peter Flass <Peter@Iron-Spring.com>
Newsgroups	alt.folklore.computers, openwatcom.users.c_cpp, comp.lang.c
Subject	Re: 16:32 far pointers in OpenWatcom C/C++
Date	2025-11-03 16:25 -0700
Organization	A noiseless patient Spider
Message-ID	<10ebdki$387ml$1@dont-email.me> (permalink)
References	(6 earlier) <hoa6f8$s1r$1@news.eternal-september.org> <20100323120956.0cd015a1@maxa> <hobc7v$omt$1@news.eternal-september.org> <10e8edu$2bc04$6@dont-email.me> <10eb31q$34thk$7@dont-email.me>

Cross-posted to 3 groups.

Show all headers | View raw

On 11/3/25 13:24, Lynn McGuire wrote:
> On 11/2/2025 2:20 PM, Peter Flass wrote:
>> What happened here?? I just noticed that a lot of these posts are from 
>> 2010. Did some news server just barf?
>>
>> On 3/23/10 14:42, Peter Flass wrote:
>>> Branimir Maksimovic wrote:
>>>> On Tue, 23 Mar 2010 06:51:18 -0400
>>>> Peter Flass <Peter_Flass@Yahoo.com> wrote:
>>>>
>>>>> Jonathan de Boyne Pollard wrote:
>>>>>> Returning to what we were talking about before the silly diversion,
>>>>>> I should point out that 32-bit applications programming where the
>>>>>> target is extended DOS or 32-bit Win16 (with OpenWatcom's extender)
>>>>>> will also occasionally employ 16:32 far pointers of course.  But as
>>>>>> I said before, regular 32-bit OS/2 or Win32 applications
>>>>>> programming generally does not, since those both use the Tiny
>>>>>> memory model, 
>>>>> Flat memory model.
>>>>
>>>> Problem with standard C and C++ is that they assume flat memory
>>>> model.
>>>
>>> I'm not a C expert, perhaps you're a denizen of comp.lang.c, but as 
>>> far as I know there's nothing in the C standard that assumes anything 
>>> about pointers, except that they have to be the same size as int, so 
>>> for 16:32 pointers I guess you'd need 64-bit ints.
>>>
>>> As far as implementations are concerned, both Watcom and IBM VA C++ 
>>> support segmented memory models.  These are the ones I'm aware of, 
>>> there are probably more.
> 
> I asked Ray Banana of E-S about the openwatcom.* groups and he 
> resurrected them with all of their very old postings.
> 
> Lynn
> 

Oh, OK. Also everything that was X-posted. No worries.

Back to openwatcom.users.c_cpp | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: 16:32 far pointers in OpenWatcom C/C++ Peter Flass <Peter@Iron-Spring.com> - 2025-11-02 13:20 -0700
  OT: 2010 posts (was: Re: 16:32 far pointers in OpenWatcom C/C++) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-03 14:58 +0000
  Re: 16:32 far pointers in OpenWatcom C/C++ Lynn McGuire <lynnmcguire5@gmail.com> - 2025-11-03 14:24 -0600
    Re: 16:32 far pointers in OpenWatcom C/C++ Peter Flass <Peter@Iron-Spring.com> - 2025-11-03 16:25 -0700
      Re: 16:32 far pointers in OpenWatcom C/C++ Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 00:26 +0000
        Re: 16:32 far pointers in OpenWatcom C/C++ scott@slp53.sl.home (Scott Lurndal) - 2025-11-04 15:20 +0000
          Re: 16:32 far pointers in OpenWatcom C/C++ Peter Flass <Peter@Iron-Spring.com> - 2025-11-04 09:39 -0700
            Re: 16:32 far pointers in OpenWatcom C/C++ scott@slp53.sl.home (Scott Lurndal) - 2025-11-04 17:14 +0000
              Re: 16:32 far pointers in OpenWatcom C/C++ scott@slp53.sl.home (Scott Lurndal) - 2025-11-04 17:32 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 17:38 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ David Brown <david.brown@hesbynett.no> - 2025-11-04 21:23 +0100
                Re: 16:32 far pointers in OpenWatcom C/C++ scott@slp53.sl.home (Scott Lurndal) - 2025-11-04 22:04 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ David Brown <david.brown@hesbynett.no> - 2025-11-05 08:50 +0100
                Re: 16:32 far pointers in OpenWatcom C/C++ scott@slp53.sl.home (Scott Lurndal) - 2025-11-05 15:15 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ David Brown <david.brown@hesbynett.no> - 2025-11-06 08:51 +0100
            Re: 16:32 far pointers in OpenWatcom C/C++ Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-04 22:17 +0000
            Re: 16:32 far pointers in OpenWatcom C/C++ cross@spitfire.i.gajendra.net (Dan Cross) - 2025-11-07 15:50 +0000
              Re: 16:32 far pointers in OpenWatcom C/C++ scott@slp53.sl.home (Scott Lurndal) - 2025-11-07 16:08 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ cross@spitfire.i.gajendra.net (Dan Cross) - 2025-11-07 16:54 +0000
              Re: 16:32 far pointers in OpenWatcom C/C++ Paul S Person <psperson@old.netcom.invalid> - 2025-11-07 08:22 -0800
                Re: 16:32 far pointers in OpenWatcom C/C++ cross@spitfire.i.gajendra.net (Dan Cross) - 2025-11-07 17:22 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ Michael S <already5chosen@yahoo.com> - 2025-11-09 11:15 +0200
                Re: 16:32 far pointers in OpenWatcom C/C++ cross@spitfire.i.gajendra.net (Dan Cross) - 2025-11-10 09:08 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ scott@slp53.sl.home (Scott Lurndal) - 2025-11-07 17:43 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-07 19:40 +0000
              Re: 16:32 far pointers in OpenWatcom C/C++ Peter Flass <Peter@Iron-Spring.com> - 2025-11-08 08:45 -0700
          Re: 16:32 far pointers in OpenWatcom C/C++ Richard Heathfield <rjh@cpax.org.uk> - 2025-11-04 17:12 +0000
            Re: 16:32 far pointers in OpenWatcom C/C++ geodandw <geodandw@gmail.com> - 2025-11-04 12:15 -0500
              Re: 16:32 far pointers in OpenWatcom C/C++ Kaz Kylheku <643-408-1753@kylheku.com> - 2025-11-04 17:21 +0000
              Re: 16:32 far pointers in OpenWatcom C/C++ Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-04 22:19 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ rbowman <bowman@montana.com> - 2025-11-05 00:13 +0000
              Re: 16:32 far pointers in OpenWatcom C/C++ cross@spitfire.i.gajendra.net (Dan Cross) - 2025-11-07 16:46 +0000
                Re: 16:32 far pointers in OpenWatcom C/C++ Peter Flass <Peter@Iron-Spring.com> - 2025-11-08 08:47 -0700
                Re: 16:32 far pointers in OpenWatcom C/C++ John Levine <johnl@taugh.com> - 2025-11-08 21:17 +0000
        Re: 16:32 far pointers in OpenWatcom C/C++ Paul S Person <psperson@old.netcom.invalid> - 2025-11-04 08:29 -0800
    Re: 16:32 far pointers in OpenWatcom C/C++ Paul S Person <psperson@old.netcom.invalid> - 2025-11-04 08:32 -0800

csiph-web