Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c++ > #90713 > unrolled thread

Parsing multi-byte keystrokes

Started by"R.Wieser" <address@is.invalid>
First post2023-06-25 19:45 +0200
Last post2023-06-26 19:24 +0200
Articles 20 on this page of 143 — 19 participants

Back to article view | Back to comp.lang.c++


Contents

  Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-25 19:45 +0200
    Re: Parsing multi-byte keystrokes "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-06-25 20:34 +0200
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-25 21:39 +0200
      Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-25 15:06 -0700
        Re: Parsing multi-byte keystrokes Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-06-25 20:18 -0400
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-25 19:10 -0700
        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 08:46 +0200
    Re: Parsing multi-byte keystrokes Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-06-25 18:39 -0400
      Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 00:53 +0100
        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 09:11 +0200
          Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-06-26 09:32 +0200
          Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 13:50 +0100
            Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 15:03 +0200
              Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-06-26 22:27 +0200
                Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 22:48 +0200
                  Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 14:35 -0700
                  Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-06-26 23:58 +0200
                    Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 16:26 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 08:50 +0200
        Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 01:39 -0700
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:43 +0200
            Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-06-26 15:26 +0000
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 18:04 +0200
            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:01 -0700
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 21:59 +0200
                Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 14:15 -0700
                Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 22:35 +0000
                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 13:15 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:03 +0000
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 17:49 +0200
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:23 -0700
        Re: Parsing multi-byte keystrokes red floyd <no.spam.here@its.invalid> - 2023-06-28 14:35 -0700
          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-06-29 00:17 +0000
            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-29 00:43 +0000
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 14:04 +0200
                Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-06-29 15:44 +0000
                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 18:37 +0200
                    Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-30 14:14 +0100
                      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-30 18:12 +0200
                        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-30 20:32 +0200
                        Re: Parsing multi-byte keystrokes Paavo Helde <eesnimi@osa.pri.ee> - 2023-06-30 22:57 +0300
                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-01 09:49 +0200
                        Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-30 21:36 +0100
                        Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-30 13:45 -0700
                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-01 10:33 +0200
                            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-01 11:58 -0700
                              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 11:03 +0200
                                Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-07-02 23:15 +0200
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 09:12 +0200
                                Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-02 15:39 -0700
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 10:12 +0200
                                    Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-03 13:28 +0000
                                    Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-03 12:43 -0400
                                Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-03 15:41 +0000
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 21:32 +0200
                                    Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-03 21:06 +0000
                                    Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-04 05:20 -0400
                                      Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-04 13:56 +0000
                                        Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-04 16:03 -0400
                                          Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 21:03 +0000
                                            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-04 14:33 -0700
                                              Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 21:55 +0000
                                                Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 13:58 +0000
                                            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 13:56 +0000
                                    Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-04 15:54 +0000
                                      Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-04 18:03 +0200
                                        Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 16:33 +0000
                                          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-04 16:41 +0000
                                            Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 16:52 +0000
                                          Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-05 09:50 +0200
                                            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 14:00 +0000
                                            Re: Parsing multi-byte keystrokes "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-05 11:21 -0700
                                              Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 20:24 +0000
                                            Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-05 19:31 +0000
                                        Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-04 19:05 +0000
                                      Re: Parsing multi-byte keystrokes red floyd <no.spam.here@its.invalid> - 2023-07-05 18:31 -0700
                                        Cars (Was: Parsing what is Linux?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-06 08:40 +0000
                                        Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-06 08:55 +0000
                                          Cars (Was: Parsing multi-byte keystrokes) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-06 09:27 +0000
                                            Re: Cars (Was: Parsing multi-byte keystrokes) Muttley@dastardlyhq.com - 2023-07-06 15:43 +0000
                                              Totally insane (Was: Cars (Was: Parsing multi-byte keystrokes)) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-06 16:53 +0000
                                                Re: Totally insane (Was: Cars (Was: Parsing multi-byte keystrokes)) Muttley@dastardlyhq.com - 2023-07-07 07:15 +0000
                        Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-06-30 17:00 -0400
                          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-01 07:53 +0000
                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-01 10:30 +0200
                            Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-02 04:04 -0400
                              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 11:27 +0200
                                Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-02 14:51 -0400
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 22:49 +0200
                                    Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-02 18:56 -0400
                                      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 10:59 +0200
                                        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-03 13:34 +0000
                                        Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-03 12:20 -0400
                                          Re: Parsing multi-byte keystrokes Richard Harnden <richard.nospam@gmail.com> - 2023-07-03 18:02 +0100
                                            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-03 14:40 -0700
                                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 22:50 +0200
                                            Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-04 05:47 -0400
                                          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-03 14:36 -0700
                            Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-03 11:38 +0200
                              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 13:04 +0200
                                Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-03 15:11 +0200
                                Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-07-03 20:35 +0200
                                  Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-03 19:16 +0000
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 22:55 +0200
                          Re: Parsing multi-byte keystrokes Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-01 03:03 -0700
                            Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-01 10:30 +0000
                    Re: Parsing multi-byte keystrokes "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-07-01 22:37 +0200
                      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 09:42 +0200
        Re: Parsing multi-byte keystrokes Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-06-29 22:21 -0400
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-30 17:50 +0200
    Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-25 23:20 +0000
      Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-25 17:10 -0700
        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 09:21 +0200
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 01:29 -0700
            Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:30 +0200
              Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:18 -0700
                Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 22:37 +0200
                  Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 14:32 -0700
                  Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 22:41 +0000
                    Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 13:58 +0200
                      Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-29 13:59 -0700
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 01:30 -0700
            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:00 +0000
          Re: Parsing multi-byte keystrokes "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2023-06-26 12:31 +0200
            Re: Parsing multi-byte keystrokes "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2023-06-26 12:47 +0200
            Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:56 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 13:58 +0000
        Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:08 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 08:56 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:02 +0000
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 17:46 +0200
            Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 18:19 +0100
              Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 18:36 +0000
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 21:24 +0200
                Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 22:12 +0100
    Re: Parsing multi-byte keystrokes wij <wyniijj5@gmail.com> - 2023-06-26 02:06 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:49 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:05 +0000
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 17:58 +0200
        Re: Parsing multi-byte keystrokes wij <wyniijj5@gmail.com> - 2023-06-27 13:32 -0700
          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-06-28 02:17 +0000
            Re: Parsing multi-byte keystrokes wij <wyniijj5@gmail.com> - 2023-06-27 20:26 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 19:24 +0200

Page 4 of 8 — ← Prev page 1 2 3 [4] 5 6 7 8  Next page →


#90873

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-07-04 14:33 -0700
Message-ID<87edlnweeb.fsf@nosuchdomain.example.com>
In reply to#90872
kalevi@kolttonen.fi (Kalevi Kolttonen) writes:
> James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
>> UNIX is a standard, and most distros of Linux come close to fully
>> conforming to it. According to one of the other posters on this thread,
>> there are even distros that fully conform to it.
>
> Right. It is clear that my information was outdated. 
> The last I checked, no Linux distro had gone through 
> the UNIX certification process. But according to:
>
>   https://en.wikipedia.org/wiki/Unix
>
> "Notably, EulerOS and Inspur K-UX are Linux 
> distributions certified as UNIX 03 compliant."
>
> I have no idea what "03" means but I am pretty
> damn sure it does not stand for "2003".

It's version 3 of the Single UNIX specification, released in 2002.
(Previous versions are referred to as UNIX 95 and UNIX 98, so it's
very likely that the "03" refers to the year 2003.)

https://unix.org/unix03.html

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]


#90874

Fromkalevi@kolttonen.fi (Kalevi Kolttonen)
Date2023-07-04 21:55 +0000
Message-ID<u824gk$7b2m$1@dont-email.me>
In reply to#90873
Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
> kalevi@kolttonen.fi (Kalevi Kolttonen) writes:
>> James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
>>> UNIX is a standard, and most distros of Linux come close to fully
>>> conforming to it. According to one of the other posters on this thread,
>>> there are even distros that fully conform to it.
>>
>> Right. It is clear that my information was outdated. 
>> The last I checked, no Linux distro had gone through 
>> the UNIX certification process. But according to:
>>
>>   https://en.wikipedia.org/wiki/Unix
>>
>> "Notably, EulerOS and Inspur K-UX are Linux 
>> distributions certified as UNIX 03 compliant."
>>
>> I have no idea what "03" means but I am pretty
>> damn sure it does not stand for "2003".
> 
> It's version 3 of the Single UNIX specification, released in 2002.
> (Previous versions are referred to as UNIX 95 and UNIX 98, so it's
> very likely that the "03" refers to the year 2003.)
> 
> https://unix.org/unix03.html

That's very surprising, at least for me. I never 
thought it would refer to such an old specification. 
I mean, come on, 2003, that was *20 years ago*!

While we are at it:

  https://en.wikipedia.org/wiki/Inspur_K-UX

"Inspur K-UX 3.0 was also certified as a UNIX OS, although, 
according to the same website, its certification expired 
on 3 February 2019 and has not yet been renewed."

And:

  https://en.wikipedia.org/wiki/EulerOS

"EulerOS 2.0, running on the Huawei KunLun Mission 
Critical Server, was certified to conform to The 
Open Group's UNIX 03 standard, however the certification 
expired in September 2022."

I did not bother to check whether those distros
have renewed their UNIX certification. Wikipedia
can certainly contain outdated information.

Anyway, according to the same article EulerOS was 
first released on September 24, 2021. It is 
unbelievable that the UNIX 03 certification was 
still worth acquiring just a few years ago.

How can a 20 year old specification still be
valid in a field that develops very rapidly?


br,
KK

[toc] | [prev] | [next] | [standalone]


#90886

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-07-05 13:58 +0000
Message-ID<hGepM.33225$t9v6.22776@fx15.iad>
In reply to#90874
kalevi@kolttonen.fi (Kalevi Kolttonen) writes:
>Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> kalevi@kolttonen.fi (Kalevi Kolttonen) writes:

>How can a 20 year old specification still be
>valid in a field that develops very rapidly?

It's still being developed, and there are newer versions.

https://www.opengroup.org/austin/

[toc] | [prev] | [next] | [standalone]


#90885

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-07-05 13:56 +0000
Message-ID<EEepM.33224$t9v6.26906@fx15.iad>
In reply to#90872
kalevi@kolttonen.fi (Kalevi Kolttonen) writes:
>James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
>> UNIX is a standard, and most distros of Linux come close to fully
>> conforming to it. According to one of the other posters on this thread,
>> there are even distros that fully conform to it.
>
>Right. It is clear that my information was outdated. 
>The last I checked, no Linux distro had gone through 
>the UNIX certification process. But according to:
>
>  https://en.wikipedia.org/wiki/Unix
>
>"Notably, EulerOS and Inspur K-UX are Linux 
>distributions certified as UNIX 03 compliant."
>
>I have no idea what "03" means but I am pretty
>damn sure it does not stand for "2003".

That's exactly what it stands for.

[toc] | [prev] | [next] | [standalone]


#90860

FromMuttley@dastardlyhq.com
Date2023-07-04 15:54 +0000
Message-ID<u81fcd$4vie$1@dont-email.me>
In reply to#90846
On Mon, 3 Jul 2023 21:32:27 +0200
"R.Wieser" <address@is.invalid> wrote:
>Muttly,
>
>> I've posted linux specific questions on that group and no
>> one complained.
>
>Thanks for that.
>
>Though mine is not a programing question, but /an availability/ of something 
>in Linux.   There, AFAICT, the the distinction matters.
>
>To me it feels like asking a Fort dealer about something thats going to be 
>used in an Audi.

Its more like asking a VW or Skoda dealer about your Audi.

[toc] | [prev] | [next] | [standalone]


#90861

FromDavid Brown <david.brown@hesbynett.no>
Date2023-07-04 18:03 +0200
Message-ID<u81frk$4voj$1@dont-email.me>
In reply to#90860
On 04/07/2023 17:54, Muttley@dastardlyhq.com wrote:
> On Mon, 3 Jul 2023 21:32:27 +0200
> "R.Wieser" <address@is.invalid> wrote:
>> Muttly,
>>
>>> I've posted linux specific questions on that group and no
>>> one complained.
>>
>> Thanks for that.
>>
>> Though mine is not a programing question, but /an availability/ of something
>> in Linux.   There, AFAICT, the the distinction matters.
>>
>> To me it feels like asking a Fort dealer about something thats going to be
>> used in an Audi.
> 
> Its more like asking a VW or Skoda dealer about your Audi.
> 

It is more like asking a "Motorised vehicle dealer" about your vehicle 
with wheels.  The dealer might also sell tanks and other belted 
vehicles, but most of the trade is in things with wheels.

Technically, Linux is not UNIX because it does not share a common 
ancestor in early UNIX code.  But the functional commonality between 
Linux and "true" UNIX versions is huge - you'll find very little code 
that works on multiple UNIX systems that does not work equally well on 
Linux.

It's possible that Linux has additional features that make the OP's task 
easier on Linux than on one or more of the real UNIX's, but there is 
still a much better chance of learning about that on c.u.p. than here in 
c.l.c++.

[toc] | [prev] | [next] | [standalone]


#90862

Fromkalevi@kolttonen.fi (Kalevi Kolttonen)
Date2023-07-04 16:33 +0000
Message-ID<u81hk0$57oe$1@dont-email.me>
In reply to#90861
David Brown <david.brown@hesbynett.no> wrote:
> Technically, Linux is not UNIX because it does 
> not share a common ancestor in early UNIX code.

I have to disagree with that claim. There is no
requirement to "share a common ancestor" at all
in order to be a UNIX system.

Linux could indeed become "a certified UNIX"
by fulfilling certain technical requirements:

  https://www.opengroup.org/certifications/unix

The Linux community never bothered to do that.

It probably would not help in any real sense
and maybe they are not willing to put money
into it. Linux works fine just the way it is,
regardless of the "certified UNIX" status.

As far as I remember, when Dennis Ritchie was 
asked whether Linux is a "real UNIX", he replied 
that for all sensible definitions, yes, it is.
Or something like that.

The following is from Wikipedia and from
Dennis Ritchie's mouth:

"I think the Linux phenomenon is quite delightful, 
because it draws so strongly on the basis that 
Unix provided. Linux seems to be among the healthiest 
of the direct Unix derivatives, though there are also 
the various BSD systems as well as the more official 
offerings from the workstation and mainframe 
manufacturers."

"In the same interview, he states that he views both 
Unix and Linux as "the continuation of ideas that were 
started by Ken and me and many others, many years ago"

In any case, all that is pretty much off-topic.
The OP is making a fool of himself. He should just 
shut up and go to comp.unix.programmer.

br,
KK

[toc] | [prev] | [next] | [standalone]


#90863

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2023-07-04 16:41 +0000
Message-ID<u81i4d$1r17v$1@news.xmission.com>
In reply to#90862
In article <u81hk0$57oe$1@dont-email.me>,
Kalevi Kolttonen <kalevi@kolttonen.fi> wrote:
...
>In any case, all that is pretty much off-topic.
>The OP is making a fool of himself. He should just 
>shut up and go to comp.unix.programmer.

But you guys keep feeding him.  You keep egging him on.  So, you're at
least partly to blame.

I remember well the moment where this all turned personal - where it turned
"meta" and became all about OP trying to explain himself and the rest of
you making sure to persecute him for his efforts.  You all could have (and
should have) just ignored it.  From the first moment where he turned
"meta", you could have just ignored it.  But no...

Keith is actually directly responsible for it all (and I'm sure he's very
proud of himself) by insisting on bringing up irrelevant nonsense about
attribution-quoting and mentioning other newsgroups.  He should have just
resisted the urge to be himself - but he never does.

-- 
There are a lot of Wisconsin farmers right now who, despite having
themselves voted for Trump, are now wishing that their state's electors
had had the good sense to vote for the other candidate - thereby saving
them from their current predicament.

[toc] | [prev] | [next] | [standalone]


#90864

Fromkalevi@kolttonen.fi (Kalevi Kolttonen)
Date2023-07-04 16:52 +0000
Message-ID<u81ink$59r3$1@dont-email.me>
In reply to#90863
Kenny McCormack <gazelle@shell.xmission.com> wrote:
> But you guys keep feeding him.  You keep egging him on.
> So, you're at least partly to blame.

To be quite honest, I totally agree with you. This 
thread should have died a long time ago.

I will only defend myself here by saying that I 
posted *just one message* with the main intention 
to correct what I thought was David Brown's false 
statement about UNIX. 

Yes, I also commented on the OP, but having read 
over a hundred posts in this thread, I just 
could not be quiet any longer...

This is my second post and I hope it will
be my last. :-)

br,
KK

[toc] | [prev] | [next] | [standalone]


#90878

FromDavid Brown <david.brown@hesbynett.no>
Date2023-07-05 09:50 +0200
Message-ID<u837cr$f4if$1@dont-email.me>
In reply to#90862
On 04/07/2023 18:33, Kalevi Kolttonen wrote:
> David Brown <david.brown@hesbynett.no> wrote:
>> Technically, Linux is not UNIX because it does
>> not share a common ancestor in early UNIX code.
> 
> I have to disagree with that claim. There is no
> requirement to "share a common ancestor" at all
> in order to be a UNIX system.
> 
> Linux could indeed become "a certified UNIX"
> by fulfilling certain technical requirements:
> 
>    https://www.opengroup.org/certifications/unix
> 

I was under the impression that the classification "UNIX" was for OS's 
that were derived from at least part of the original "UNIX" code - as 
was the case for SunOS, AIX, and so on.  I could be wrong - or it could 
also have been changed.  Ultimately, "UNIX" means what the owners of 
that trademark decide it means, and the owners have changed over time.

> The Linux community never bothered to do that.

The history of the term "UNIX" has been filled with politics, legal 
battles, economic fights - things that most of the Linux community would 
prefer to stay clear of.  In particular, there was that ugly business 
with Microsoft paying SCO to fight with Novell about UNIX and source 
code in Linux, as an underhand way to try to stop the success of Linux 
challenging the monopoly of Windows.  (Happily, MS has moved on a fair 
bit since those days.)  It's no wonder that the great majority of the 
Linux community, and Linux distributors, have wanted nothing to do with 
"official" UNIX.

> 
> It probably would not help in any real sense
> and maybe they are not willing to put money
> into it. Linux works fine just the way it is,
> regardless of the "certified UNIX" status.
> 

Exactly.

> As far as I remember, when Dennis Ritchie was
> asked whether Linux is a "real UNIX", he replied
> that for all sensible definitions, yes, it is.
> Or something like that.
> 

Yes.

The reality, of course, is that such definitions are made by lawyers for 
corporations with an aim for economic gain or power and control (for 
future economic gain).  They are not "sensible", from technical 
viewpoints or from the viewpoint of being helpful to end-users.

There's nothing wrong with trying to have standards and improving 
compatibility across systems.  The challenge is who defines the 
standards - volunteer or independent groups can easily run out of money 
or energy, while company-controlled groups can be misused and biased.

> The following is from Wikipedia and from
> Dennis Ritchie's mouth:
> 
> "I think the Linux phenomenon is quite delightful,
> because it draws so strongly on the basis that
> Unix provided. Linux seems to be among the healthiest
> of the direct Unix derivatives, though there are also
> the various BSD systems as well as the more official
> offerings from the workstation and mainframe
> manufacturers."
> 
> "In the same interview, he states that he views both
> Unix and Linux as "the continuation of ideas that were
> started by Ken and me and many others, many years ago"
> 
> In any case, all that is pretty much off-topic.

But interesting - at least for some of us.

> The OP is making a fool of himself. He should just
> shut up and go to comp.unix.programmer.
> 

Yes.  Regardless of any official meaning of "UNIX", Ritchie's definition 
is the realistic and practical one.  c.u.p. covers "unix-like" systems 
as much as "true UNIX" systems.


[toc] | [prev] | [next] | [standalone]


#90887

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-07-05 14:00 +0000
Message-ID<OHepM.33226$t9v6.24167@fx15.iad>
In reply to#90878
David Brown <david.brown@hesbynett.no> writes:
>On 04/07/2023 18:33, Kalevi Kolttonen wrote:
>> David Brown <david.brown@hesbynett.no> wrote:
>>> Technically, Linux is not UNIX because it does
>>> not share a common ancestor in early UNIX code.
>> 
>> I have to disagree with that claim. There is no
>> requirement to "share a common ancestor" at all
>> in order to be a UNIX system.
>> 
>> Linux could indeed become "a certified UNIX"
>> by fulfilling certain technical requirements:
>> 
>>    https://www.opengroup.org/certifications/unix
>> 
>
>I was under the impression that the classification "UNIX" was for OS's 
>that were derived from at least part of the original "UNIX" code - as 
>was the case for SunOS, AIX, and so on.  I could be wrong - or it could 
>also have been changed.  Ultimately, "UNIX" means what the owners of 
>that trademark decide it means, and the owners have changed over time.

The trademark was transferred to X/Open (now the Open Group) two decades
ago to be applied after certification against the X/Open specifications
(subsequently merged with POSIX).

[toc] | [prev] | [next] | [standalone]


#90889

From"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>
Date2023-07-05 11:21 -0700
Message-ID<u84cav$jap4$2@dont-email.me>
In reply to#90878
On 7/5/2023 12:50 AM, David Brown wrote:
> On 04/07/2023 18:33, Kalevi Kolttonen wrote:
>> David Brown <david.brown@hesbynett.no> wrote:
>>> Technically, Linux is not UNIX because it does
>>> not share a common ancestor in early UNIX code.
>>
>> I have to disagree with that claim. There is no
>> requirement to "share a common ancestor" at all
>> in order to be a UNIX system.
>>
>> Linux could indeed become "a certified UNIX"
>> by fulfilling certain technical requirements:
>>
>>    https://www.opengroup.org/certifications/unix
>>
> 
> I was under the impression that the classification "UNIX" was for OS's 
> that were derived from at least part of the original "UNIX" code - as 
> was the case for SunOS, AIX, and so on.  I could be wrong - or it could 
> also have been changed.  Ultimately, "UNIX" means what the owners of 
> that trademark decide it means, and the owners have changed over time.
> 
>> The Linux community never bothered to do that.
> 
> The history of the term "UNIX" has been filled with politics, legal 
> battles, economic fights - things that most of the Linux community would 
> prefer to stay clear of.  In particular, there was that ugly business 
> with Microsoft paying SCO to fight with Novell about UNIX and source 
> code in Linux, as an underhand way to try to stop the success of Linux 
> challenging the monopoly of Windows.  (Happily, MS has moved on a fair 
> bit since those days.)  It's no wonder that the great majority of the 
> Linux community, and Linux distributors, have wanted nothing to do with 
> "official" UNIX.
[...]

Fwiw, I think there was a big legal battle over RCU (Read Copy Update) 
with IBM and SCO. I need to look it up again. IIrc, my friend Joe Seigh 
had to testify.

[toc] | [prev] | [next] | [standalone]


#90891

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-07-05 20:24 +0000
Message-ID<tkkpM.40745$fNr5.10096@fx16.iad>
In reply to#90889
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:
>On 7/5/2023 12:50 AM, David Brown wrote:
>> On 04/07/2023 18:33, Kalevi Kolttonen wrote:
>>> David Brown <david.brown@hesbynett.no> wrote:
>>>> Technically, Linux is not UNIX because it does
>>>> not share a common ancestor in early UNIX code.
>>>
>>> I have to disagree with that claim. There is no
>>> requirement to "share a common ancestor" at all
>>> in order to be a UNIX system.
>>>
>>> Linux could indeed become "a certified UNIX"
>>> by fulfilling certain technical requirements:
>>>
>>>    https://www.opengroup.org/certifications/unix
>>>
>> 
>> I was under the impression that the classification "UNIX" was for OS's 
>> that were derived from at least part of the original "UNIX" code - as 
>> was the case for SunOS, AIX, and so on.  I could be wrong - or it could 
>> also have been changed.  Ultimately, "UNIX" means what the owners of 
>> that trademark decide it means, and the owners have changed over time.
>> 
>>> The Linux community never bothered to do that.
>> 
>> The history of the term "UNIX" has been filled with politics, legal 
>> battles, economic fights - things that most of the Linux community would 
>> prefer to stay clear of.  In particular, there was that ugly business 
>> with Microsoft paying SCO to fight with Novell about UNIX and source 
>> code in Linux, as an underhand way to try to stop the success of Linux 
>> challenging the monopoly of Windows.  (Happily, MS has moved on a fair 
>> bit since those days.)  It's no wonder that the great majority of the 
>> Linux community, and Linux distributors, have wanted nothing to do with 
>> "official" UNIX.
>[...]
>
>Fwiw, I think there was a big legal battle over RCU (Read Copy Update) 
>with IBM and SCO. I need to look it up again. IIrc, my friend Joe Seigh 
>had to testify.
>

Everything you ever wanted to know about the SCO (Caldera) suit.

http://www.groklaw.net/

[toc] | [prev] | [next] | [standalone]


#90890

Fromkalevi@kolttonen.fi (Kalevi Kolttonen)
Date2023-07-05 19:31 +0000
Message-ID<u84gf1$jppv$1@dont-email.me>
In reply to#90878
David Brown <david.brown@hesbynett.no> wrote:
> The history of the term "UNIX" has been filled with politics, legal 
> battles, economic fights - things that most of the Linux community would 
> prefer to stay clear of.  In particular, there was that ugly business 
> with Microsoft paying SCO to fight with Novell about UNIX and source 
> code in Linux, as an underhand way to try to stop the success of Linux 
> challenging the monopoly of Windows.  (Happily, MS has moved on a fair 
> bit since those days.)  It's no wonder that the great majority of the 
> Linux community, and Linux distributors, have wanted nothing to do with 
> "official" UNIX.

I am too lazy to look up the reference, but I remember clearly what
Linus Torvalds admitted years ago. He said that the Linux kernel
would not have happened if BSD for i386 had been available.

I cannot recall the details, but BSD for PCs was also in some kind
of legal trouble.

br,
KK

[toc] | [prev] | [next] | [standalone]


#90869

FromMuttley@dastardlyhq.com
Date2023-07-04 19:05 +0000
Message-ID<u81qht$671b$1@dont-email.me>
In reply to#90861
On Tue, 4 Jul 2023 18:03:00 +0200
David Brown <david.brown@hesbynett.no> wrote:
>On 04/07/2023 17:54, Muttley@dastardlyhq.com wrote:
>> Its more like asking a VW or Skoda dealer about your Audi.
>> 
>
>It is more like asking a "Motorised vehicle dealer" about your vehicle 
>with wheels.  The dealer might also sell tanks and other belted 
>vehicles, but most of the trade is in things with wheels.
>
>Technically, Linux is not UNIX because it does not share a common 
>ancestor in early UNIX code.  But the functional commonality between 
>Linux and "true" UNIX versions is huge - you'll find very little code 
>that works on multiple UNIX systems that does not work equally well on 
>Linux.

BSD was a rewrite of SysV which was the "real" unix yet BSD is still called
unix so its all semantics really. Plus a few linux distros have passed the
OpenGroup certification process and are technically Unix. I suspect the only
reason they don't all pass is because they don't want to cough up for an
increasingly meaningless moniker.

>It's possible that Linux has additional features that make the OP's task 
>easier on Linux than on one or more of the real UNIX's, but there is 
>still a much better chance of learning about that on c.u.p. than here in 
>c.l.c++.

The closer you get to the kernel the more the various *nixes start to diverge
from each other. MacOS is considered unix but peel off the posix layer and its
a quite strange beast underneath.

[toc] | [prev] | [next] | [standalone]


#90894

Fromred floyd <no.spam.here@its.invalid>
Date2023-07-05 18:31 -0700
Message-ID<u855hm$pm9t$1@redfloyd.dont-email.me>
In reply to#90860
On 7/4/2023 8:54 AM, Muttley@dastardlyhq.com wrote:
> On Mon, 3 Jul 2023 21:32:27 +0200
> "R.Wieser" <address@is.invalid> wrote:
>> Muttly,
>>
>>> I've posted linux specific questions on that group and no
>>> one complained.
>>
>> Thanks for that.
>>
>> Though mine is not a programing question, but /an availability/ of something
>> in Linux.   There, AFAICT, the the distinction matters.
>>
>> To me it feels like asking a Fort dealer about something thats going to be
>> used in an Audi.
> 
> Its more like asking a VW or Skoda dealer about your Audi.
> 

Audi *IS* VW.   Or more precisely, VW owns Audi.   That's why Audi 
diesels were caught up in Dieselgate.

[toc] | [prev] | [next] | [standalone]


#90899 — Cars (Was: Parsing what is Linux?)

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2023-07-06 08:40 +0000
SubjectCars (Was: Parsing what is Linux?)
Message-ID<u85um2$1t929$1@news.xmission.com>
In reply to#90894
In article <u855hm$pm9t$1@redfloyd.dont-email.me>,
red floyd  <no.spam.here@its.invalid> wrote:
>On 7/4/2023 8:54 AM, Muttley@dastardlyhq.com wrote:
>> On Mon, 3 Jul 2023 21:32:27 +0200
>> "R.Wieser" <address@is.invalid> wrote:
>>> Muttly,
>>>
>>>> I've posted linux specific questions on that group and no
>>>> one complained.
>>>
>>> Thanks for that.
>>>
>>> Though mine is not a programing question, but /an availability/ of
>>> something in Linux. There, AFAICT, the the distinction matters.
>>>
>>> To me it feels like asking a Fort dealer about something thats going
>>> to be used in an Audi.
>> 
>> Its more like asking a VW or Skoda dealer about your Audi.
>> 
>
>Audi *IS* VW.   Or more precisely, VW owns Audi.   That's why Audi 
>diesels were caught up in Dieselgate.
>

Now we really have gotten to the meat of this discussion, haven't we?

I need hardly point out the insanity (a nice way of saying "hypocrisy") of
the same people who were bashing OP up and down and every way for being
off-topic (*), degenerating the thread into yet another dumb collection of
old geezers arguing about old Unix systems they once used.

At least now we're talking about cars.  That's an improvement.

(*) I'm well aware of the (BS) counter-argument here.  No need to
regurgitate it.  Thank you.

-- 
"He is exactly as they taught in KGB school: an egoist, a liar, but talented - he
knows the mind of the wrestling-loving, under-educated, authoritarian-admiring
white male populous."
    - Malcolm Nance, p59. -

[toc] | [prev] | [next] | [standalone]


#90900

FromMuttley@dastardlyhq.com
Date2023-07-06 08:55 +0000
Message-ID<u85vhh$sjdv$1@dont-email.me>
In reply to#90894
On Wed, 5 Jul 2023 18:31:34 -0700
red floyd <no.spam.here@its.invalid> wrote:
>On 7/4/2023 8:54 AM, Muttley@dastardlyhq.com wrote:
>> On Mon, 3 Jul 2023 21:32:27 +0200
>> "R.Wieser" <address@is.invalid> wrote:
>>> Muttly,
>>>
>>>> I've posted linux specific questions on that group and no
>>>> one complained.
>>>
>>> Thanks for that.
>>>
>>> Though mine is not a programing question, but /an availability/ of something
>
>>> in Linux.   There, AFAICT, the the distinction matters.
>>>
>>> To me it feels like asking a Fort dealer about something thats going to be
>>> used in an Audi.
>> 
>> Its more like asking a VW or Skoda dealer about your Audi.
>> 
>
>Audi *IS* VW.   Or more precisely, VW owns Audi.   That's why Audi 
>diesels were caught up in Dieselgate.

Duh! That was the point!

[toc] | [prev] | [next] | [standalone]


#90901 — Cars (Was: Parsing multi-byte keystrokes)

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2023-07-06 09:27 +0000
SubjectCars (Was: Parsing multi-byte keystrokes)
Message-ID<u861eh$1taol$1@news.xmission.com>
In reply to#90900
In article <u85vhh$sjdv$1@dont-email.me>,  <Muttley@dastardlyhq.com> wrote:
...
>>> Its more like asking a VW or Skoda dealer about your Audi.
>>> 
>>
>>Audi *IS* VW.   Or more precisely, VW owns Audi.   That's why Audi 
>>diesels were caught up in Dieselgate.
>
>Duh! That was the point!
>

The implication being that Linux is a subset of Unix, in the same sense as
Audi is (now) a subset of VW,

It's be like asking Amazon for help with IMDB.

-- 
Reading any post by Fred Hodgin, you're always faced with the choice of:
    lunatic, moron, or troll.

I always try to be generous and give benefit of the doubt, by assuming troll.

[toc] | [prev] | [next] | [standalone]


#90907 — Re: Cars (Was: Parsing multi-byte keystrokes)

FromMuttley@dastardlyhq.com
Date2023-07-06 15:43 +0000
SubjectRe: Cars (Was: Parsing multi-byte keystrokes)
Message-ID<u86nee$vnt1$1@dont-email.me>
In reply to#90901
On Thu, 6 Jul 2023 09:27:45 -0000 (UTC)
gazelle@shell.xmission.com (Kenny McCormack) wrote:
>In article <u85vhh$sjdv$1@dont-email.me>,  <Muttley@dastardlyhq.com> wrote:
>....
>>>> Its more like asking a VW or Skoda dealer about your Audi.
>>>> 
>>>
>>>Audi *IS* VW.   Or more precisely, VW owns Audi.   That's why Audi 
>>>diesels were caught up in Dieselgate.
>>
>>Duh! That was the point!
>>
>
>The implication being that Linux is a subset of Unix, in the same sense as
>Audi is (now) a subset of VW,

No, in the sense that Audi, VW and Skoda cars are pretty much the same.

>It's be like asking Amazon for help with IMDB.

If you don't understand unix don't comment on it. From a systems devs POV
linux and unix are 99% interchangable. Yes the kernels differ but then the
solaris kernel is a very different to AIX which is different to HP-UX.

[toc] | [prev] | [next] | [standalone]


Page 4 of 8 — ← Prev page 1 2 3 [4] 5 6 7 8  Next page →

Back to top | Article view | comp.lang.c++


csiph-web