bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Port getprogname module to SCO OpenServer


From: Tim Rice
Subject: Re: Port getprogname module to SCO OpenServer
Date: Sat, 3 Oct 2020 17:28:47 -0700 (PDT)
User-agent: Alpine 2.11 (UW2 23 2013-08-11)

Hi Bruno,

On Sat, 3 Oct 2020, Bruno Haible wrote:

> Tim Rice wrote:
> > > +# elif defined __SCO_VERSION__ /* SCO OpenServer/UnixWare */
> > 
> > While __SCO_VERSION__ covers Openserver 6 and UnixWare 7,
> > what is normally used for 6 and 7 is __USLC__  for the native compiler
> > and __sysv5__ for gcc
> > 
> > Ie.
> > # elif defined __USLC__ || defined __sysv5__
> 
> If the code depends only on the operating system, let's use a #if for
> the operating system, not for the compilers (__USLC__). Because the day
> clang gets ported to that operating systems, the condition would not
> work any more.
> 
> https://sourceforge.net/p/predef/wiki/OperatingSystems/ says that
> _SCO_DS can be used to test for SCO OpenServer. It seems that you say that
> __SCO_VERSION__  works as well. So let's use one of these.

_SCO_DS is only for Openserver 5 (which the proposed patch will not work for)
and __SCO_VERSION__ only works for the native compiler on OpenServer 6 and
UnixWare 7. Sorry I did not make that clear before.
__sysv5__ works for the GCC 7.3.0 on 6 and 7. If clang is ported, chances
are extremely high it will also include the __sysv5__ manifest define.

As to __SCO_VERSION__ vs __USLC__ for native compiler, I am fine
with __SCO_VERSION__ in this case. In the general case, I strongly
advocate __USLC__ as that is what most of us have been using for many years.

> 
> Bruno
> 

-- 
Tim Rice                                Multitalents
tim@multitalents.net





reply via email to

[Prev in Thread] Current Thread [Next in Thread]