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


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

Is this safe?

Started byMuttley@dastardlyhq.com
First post2023-02-20 16:45 +0000
Last post2023-02-21 08:15 -0800
Articles 20 on this page of 203 — 22 participants

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


Contents

  Is this safe? Muttley@dastardlyhq.com - 2023-02-20 16:45 +0000
    Re: Is this safe? Bonita Montero <Bonita.Montero@gmail.com> - 2023-02-20 18:34 +0100
      Re: Is this safe? Chris Vine <vine24683579@gmail.com> - 2023-02-20 11:16 -0800
        Re: Is this safe? Bonita Montero <Bonita.Montero@gmail.com> - 2023-02-20 21:39 +0100
          Re: Is this safe? Chris Vine <vine24683579@gmail.com> - 2023-02-20 12:56 -0800
            Re: Is this safe? Tony Oliver <guinness.tony@gmail.com> - 2023-02-20 16:17 -0800
              Re: Is this safe? Manu Raju <MR@invalid.invalid> - 2023-02-21 01:57 +0000
                Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-21 09:15 +0000
                  Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-21 12:31 +0200
            Re: Is this safe? Bonita Montero <Bonita.Montero@gmail.com> - 2023-02-21 05:36 +0100
              Re: Is this safe? Chris Vine <vine24683579@gmail.com> - 2023-02-21 02:19 -0800
                Re: Is this safe? Bonita Montero <Bonita.Montero@gmail.com> - 2023-02-21 14:16 +0100
                  Re: Is this safe? Ralf Goertz <me@myprovider.invalid> - 2023-02-21 14:40 +0100
                  Re: Is this safe? Chris Vine <vine24683579@gmail.com> - 2023-02-21 05:51 -0800
                  Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-21 15:58 +0200
                    Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-21 14:55 +0000
                      Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-21 19:02 +0200
                        Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-21 17:13 +0000
                          Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-21 19:58 +0200
                            Re: Is this safe? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-02-21 12:15 -0800
                              Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-21 23:41 +0200
                                Re: Is this safe? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-03-03 12:57 -0800
        Re: Is this safe? Tony Oliver <guinness.tony@gmail.com> - 2023-02-20 16:14 -0800
          Re: Is this safe? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-02-20 23:48 -0500
        Re: Is this safe? Öö Tiib <ootiib@hot.ee> - 2023-02-21 00:05 -0800
      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-21 09:14 +0000
    Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-20 21:18 -0500
    Re: Is this safe? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-20 20:38 -0800
      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-21 09:18 +0000
        Re: Is this safe? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-02-21 15:12 +0100
          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-21 14:53 +0000
            Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-21 10:35 -0800
              Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-22 09:25 +0000
                Re: Is this safe? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-02-22 22:33 +0100
                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 09:25 +0000
                    Re: Is this safe? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-23 07:05 -0800
                Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-22 21:21 -0800
                Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-23 09:39 +0200
                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 09:35 +0000
                    Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-23 12:30 +0200
                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 10:34 +0000
                        Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-23 13:20 +0200
                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 16:00 +0000
                            Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-23 18:24 +0200
                              Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 16:28 +0000
                                Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-23 19:01 +0200
                              Re: Is this safe? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-02-23 11:57 -0500
                                Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-23 19:12 +0200
                          Re: Is this safe? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-02-23 11:57 -0500
                            Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-23 12:20 -0500
                              Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-02-24 02:15 +0000
                                Re: Is this safe? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-02-24 15:24 -0800
                              Re: Is this safe? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-02-24 02:14 -0500
                        Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-23 07:18 -0500
                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 16:01 +0000
                            Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-23 11:50 -0500
                              Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-23 14:41 -0800
                            Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-23 19:44 +0100
                        Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-23 15:02 +0100
                          Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-02-23 14:49 +0000
                            Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-23 16:25 +0100
                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 16:10 +0000
                            Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-23 20:46 +0100
                              Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-23 20:05 +0000
                                Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-23 14:48 -0800
                                  Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-23 22:12 -0500
                                  Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-24 10:49 +0200
                                Re: Is this safe? Ralf Fassel <ralfixx@gmx.de> - 2023-02-24 11:36 +0100
                                  Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-24 15:39 +0000
                              Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-24 10:29 +0000
                                Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-24 17:20 +0100
                                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-24 17:09 +0000
                                    Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-24 17:32 +0000
                                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-25 11:56 +0000
                                        Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-25 16:04 +0100
                                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-25 15:47 +0000
                                            Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-25 19:13 +0100
                                              Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-25 19:00 +0000
                                              Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-27 08:43 +0000
                                                Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-27 10:31 +0100
                                          Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-25 16:40 +0000
                                    Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-24 18:42 +0100
                                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-25 11:58 +0000
                                        Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-25 16:25 +0100
                                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-25 15:45 +0000
                                            Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-25 19:15 +0100
                                              Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-27 08:44 +0000
                                                Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-27 10:40 +0100
                                                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-27 10:24 +0000
                                                    Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-27 18:31 +0100
                                                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-28 08:38 +0000
                                                        Re: Is this safe? Öö Tiib <ootiib@hot.ee> - 2023-02-28 01:33 -0800
                                                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-28 10:17 +0000
                                                            Re: Is this safe? Öö Tiib <ootiib@hot.ee> - 2023-02-28 02:43 -0800
                                                              Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-28 16:50 +0100
                                                        Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-02-28 03:19 -0800
                                                          Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-28 08:10 -0500
                                                            Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-02-28 05:42 -0800
                                                              Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-28 09:39 -0500
                                                                Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-02-28 07:12 -0800
                                                                  Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-28 11:29 -0500
                                                              Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-28 16:45 +0100
                                                                Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-02-28 11:31 -0800
                                                                  Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-28 20:59 +0100
                                                              Re: Is this safe? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-03-01 14:29 -0800
                                                        Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-28 16:37 +0100
                                                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-28 15:56 +0000
                                                            Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-28 18:34 +0100
                                                              Re: Is this safe? Muttley@dastardlyhq.com - 2023-03-01 09:37 +0000
                                                                Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-01 02:29 -0800
                                                                  Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-01 19:56 +0000
                                                                    Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-01 12:53 -0800
                                                                      Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-01 21:13 +0000
                                                                        Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-02 01:48 -0800
                                                                          Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-03 21:44 +0000
                                                                            Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-03 20:16 -0800
                                                                              Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-04 22:55 +0000
                                                                                Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-05 07:11 -0800
                                                                                  Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-05 20:44 +0000
                                                                                    Re: Is this safe? Mr Flibble <flibble2@reddwarf.jmc.corp> - 2023-03-05 21:00 +0000
                                                                                      Re: Is this safe? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-03-05 13:59 -0800
                                                                                        Re: Is this safe? Mr Flibble <flibble2@reddwarf.jmc.corp> - 2023-03-05 23:07 +0000
                                                                                      Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-06 00:22 +0000
                                                                                    Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-05 14:26 -0800
                                                                                      Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-06 00:51 +0000
                                                                                        Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-06 02:17 -0800
                                                                              Re: Is this safe? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-03-05 08:13 -0800
                                                                                Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-05 09:05 -0800
                                                                        Re: Is this safe? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-03-14 09:47 -0700
                                                                      Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-03-01 14:40 -0800
                                                                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-03-02 09:07 +0000
                                                                  Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-03-01 21:37 -0500
                                                                    Re: Is this safe? Öö Tiib <ootiib@hot.ee> - 2023-03-01 22:30 -0800
                                                                Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-03-01 14:27 +0100
                                                                  Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-03-01 10:48 -0800
                                                                    Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-03-02 10:29 +0100
                                                                Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-01 19:53 +0000
                                                                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-03-02 09:08 +0000
                                                                    Re: Is this safe? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-03-02 01:32 -0800
                                                                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-03-02 09:56 +0000
                                                                        Re: Is this safe? Öö Tiib <ootiib@hot.ee> - 2023-03-02 04:02 -0800
                                                                          Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-03-02 15:00 +0100
                                                                            Re: Is this safe? Öö Tiib <ootiib@hot.ee> - 2023-03-02 07:59 -0800
                                                                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-03-02 15:38 +0000
                                                                            Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-03-02 11:16 -0800
                                                                    Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-03-02 11:08 -0800
                                                                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-03-03 09:53 +0000
                                                                        Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-03-04 06:47 -0800
                                                                    Re: Is this safe? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-03-02 19:35 +0000
                                                        Re: Is this safe? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-02-28 17:40 +0100
                                  Re: Is this safe? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-02-24 12:16 -0500
                                    Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-24 18:39 +0100
                                      Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-24 10:03 -0800
                                        Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-24 19:59 +0100
                                      Re: Is this safe? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-02-25 06:47 +0100
                                        Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-25 10:23 +0200
                        Re: Is this safe? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-23 07:16 -0800
                          Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-23 14:31 -0800
                        Re: Is this safe? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-02-23 16:34 +0100
                          Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 16:15 +0000
                            Re: Is this safe? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-02-24 12:17 +0100
                              Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-24 12:24 +0000
                                Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-24 15:18 +0200
                                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-24 15:55 +0000
                                    Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-24 18:20 +0200
                                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-24 17:05 +0000
                                        Re: Is this safe? Paavo Helde <eesnimi@osa.pri.ee> - 2023-02-24 19:24 +0200
                                        Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-24 09:46 -0800
                                Re: Is this safe? David Brown <david.brown@hesbynett.no> - 2023-02-24 17:30 +0100
                        Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-23 17:12 +0000
                    Re: Is this safe? Öö Tiib <ootiib@hot.ee> - 2023-02-23 02:47 -0800
                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 15:59 +0000
                        Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-23 11:55 -0500
                    Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-23 08:37 -0800
                      Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-23 14:19 -0800
                  Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-23 17:09 +0000
                    Re: Is this safe? Richard Damon <Richard@Damon-Family.org> - 2023-02-23 12:21 -0500
                      Re: Is this safe? scott@slp53.sl.home (Scott Lurndal) - 2023-02-23 17:55 +0000
                        Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-23 13:57 -0800
                          Re: Is this safe? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-23 17:28 -0800
                            Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-23 21:44 -0800
                              Re: Is this safe? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-02-24 08:48 -0800
            Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-21 10:58 -0800
              Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-22 09:26 +0000
                Re: Is this safe? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-02-22 22:34 +0100
                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 09:29 +0000
                    Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-23 08:28 -0800
                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 17:16 +0000
                        Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-23 22:24 -0800
                Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-22 21:30 -0800
                  Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-23 09:31 +0000
                    Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-23 22:00 -0800
                      Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-23 22:20 -0800
                        Re: Is this safe? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-02-24 01:34 -0500
                      Re: Is this safe? Muttley@dastardlyhq.com - 2023-02-24 10:32 +0000
                        Re: Is this safe? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-02-25 00:19 -0800
              Re: Is this safe? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-22 08:09 -0800
          Re: Is this safe? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-21 22:32 -0800
            Re: Is this safe? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-02-22 08:32 -0800
              Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-02-22 09:17 -0800
                Re: Is this safe? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-04-04 23:28 -0700
                  Re: Is this safe? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-04-05 11:08 -0700
        Re: Is this safe? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-02-21 08:15 -0800

Page 9 of 11 — ← Prev page 1 … 7 8 [9] 10 11  Next page →


#89279

From"Alf P. Steinbach" <alf.p.steinbach@gmail.com>
Date2023-02-24 12:17 +0100
Message-ID<tta6bj$26nuf$1@dont-email.me>
In reply to#89237
On 2023-02-23 5:15 PM, Muttley@dastardlyhq.com wrote:
> On Thu, 23 Feb 2023 16:34:57 +0100
> "Alf P. Steinbach" <alf.p.steinbach@gmail.com> wrote:
>> On 2023-02-23 11:34 AM, Muttley@dastardlyhq.com wrote:
>> Implementations do access arrays with the character code as index
>> because functions like `toupper` are locale dependent and in practice
>> support a number of encodings such as Latin-1, in addition to ASCII.
> 
> The digit characters are the same valid regardless of which 8 bit code page is
> being used. Ditto UTF16 and UTF8, so I have no idea in which locale the
> numeric digits would have different values.

There's only an associative connection between your question concerning 
digits, and the preceding discussion about `toupper`. Thread warping is 
a tradition but still, consider starting a new thread for a new topic.

As answer to the (off topical) question about digits other than the 
ASCII ones, see the table of digit symbols in Wikipedia, <url: 
https://en.wikipedia.org/wiki/Numerical_digit#Numerals_in_most_popular_systems>.

That table shows a multitude of characters that, in other languages than 
English, are considered digits. All these are present in Unicode. UTF-8 
encodes all of Unicode. Whether this means that "numeric digits would 
have different values" depends on what you mean by that, unless you're 
talking about archaic EBCDIC. It doesn't make much sense to me.

The /C++ standard/ guarantees that the Arabic digits 0 through 9 have 
consecutive code points.

Possibly because that's so in both ASCII and EBCDIC.

- Alf

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


#89280

FromMuttley@dastardlyhq.com
Date2023-02-24 12:24 +0000
Message-ID<ttaa9d$27813$1@dont-email.me>
In reply to#89279
On Fri, 24 Feb 2023 12:17:06 +0100
"Alf P. Steinbach" <alf.p.steinbach@gmail.com> wrote:
>On 2023-02-23 5:15 PM, Muttley@dastardlyhq.com wrote:
>> On Thu, 23 Feb 2023 16:34:57 +0100
>> "Alf P. Steinbach" <alf.p.steinbach@gmail.com> wrote:
>>> On 2023-02-23 11:34 AM, Muttley@dastardlyhq.com wrote:
>>> Implementations do access arrays with the character code as index
>>> because functions like `toupper` are locale dependent and in practice
>>> support a number of encodings such as Latin-1, in addition to ASCII.
>> 
>> The digit characters are the same valid regardless of which 8 bit code page
>is
>> being used. Ditto UTF16 and UTF8, so I have no idea in which locale the
>> numeric digits would have different values.
>
>There's only an associative connection between your question concerning 
>digits, and the preceding discussion about `toupper`. Thread warping is 
>a tradition but still, consider starting a new thread for a new topic.
>
>As answer to the (off topical) question about digits other than the 
>ASCII ones, see the table of digit symbols in Wikipedia, <url: 
>https://en.wikipedia.org/wiki/Numerical_digit#Numerals_in_most_popular_systems>
>.
>
>That table shows a multitude of characters that, in other languages than 
>English, are considered digits. All these are present in Unicode. UTF-8 
>encodes all of Unicode. Whether this means that "numeric digits would 
>have different values" depends on what you mean by that, unless you're 
>talking about archaic EBCDIC. It doesn't make much sense to me.
>
>The /C++ standard/ guarantees that the Arabic digits 0 through 9 have 
>consecutive code points.

From a programming POV the only ones that matter are the ones that can be
used in mathematical operations by the compiler. I doubt the arab digits or
any UTF comedy digits fall into that category.

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


#89281

FromPaavo Helde <eesnimi@osa.pri.ee>
Date2023-02-24 15:18 +0200
Message-ID<ttadg0$27i1m$1@dont-email.me>
In reply to#89280
24.02.2023 14:24 Muttley@dastardlyhq.com kirjutas:
> On Fri, 24 Feb 2023 12:17:06 +0100
> "Alf P. Steinbach" <alf.p.steinbach@gmail.com> wrote:

>>
>> The /C++ standard/ guarantees that the Arabic digits 0 through 9 have
>> consecutive code points.
> 
>  From a programming POV the only ones that matter are the ones that can be
> used in mathematical operations by the compiler. I doubt the arab digits or
> any UTF comedy digits fall into that category.

Unless the compiler is for a programming language in Arabic. This is an 
extract from 
https://github.com/nasser/---/blob/master/public/lib/mtfaail/mtfaail.qlb

If I'm not mistaken, there are digits there in the first two lines.

(قول "قـلـب: لغة برمجة - مترجم ٠،١،٣")
(قول "رمــــــزي نـــــاصـــــر ٢٠١٢")
(قول "")
(قول "<a class='execute' href='#أمثلة'>أمثلة</a> - <a class='execute' 
href='#النجدة'>الــنجــدة</a> - <a class='execute' href='#ما-هذا؟'>مـا 
هـذا؟</a>")
(قول "")

(حدد أمثلة (لامدا () (
   (قول "سـهـل: <a class='load' href='#amthila/mrhba'>مرحبا يا عالم</a>")
   (قول "متوسط: <a class='load' href='#amthila/fybunatshi'>عدد 
فيبوناتشي</a>")
   (قول "متقدم: <a class='load' href='#amthila/konway'>لعبة الحياة 
لكونواي</a>")
   (عدم)
)))

(حدد النجدة (لامدا () (قول "هذا قلب!")))
(حدد ما-هذا؟ (لامدا ()
   (قول "قلب هـي لغة برمجة هدفها إستكشاف")
   (قول "العلاقة بـيـن الـثقـافة البشـرية")
   (قول "والعلوم الحاســوبية، خصوصاً علاقة")
   (قول "الأبجدية الـلاتينية بلغات البرمجة")
   (قول "المختلفة. للمزيد مــن المعلومات")

   (قول "زوروا الموقـع <a target='_blank' 
href='http://قلب-لغة-برمجة.com'>قلب-لغة-برمجة.com</a>")
   (قول "")
   (قول "تم تصميم وتنفيذ قلب بدعم <a target='_blank' 
href='http://eyebeam.org'>المركز</a>")
   (قول "<a target='_blank' href='http://eyebeam.org'>الـفـنـي 
التكنولوجي 'ايـبــيـم'</a>")
   (قول "في نيو يورك، حين كـان رمزي ناصر")
   (قول "فــنــان مــقــيــم سـنـة ٢٠١٢.")
   (عدم)
))

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


#89284

FromMuttley@dastardlyhq.com
Date2023-02-24 15:55 +0000
Message-ID<ttamlg$28h7l$1@dont-email.me>
In reply to#89281
On Fri, 24 Feb 2023 15:18:55 +0200
Paavo Helde <eesnimi@osa.pri.ee> wrote:
>24.02.2023 14:24 Muttley@dastardlyhq.com kirjutas:
>> On Fri, 24 Feb 2023 12:17:06 +0100
>> "Alf P. Steinbach" <alf.p.steinbach@gmail.com> wrote:
>
>>>
>>> The /C++ standard/ guarantees that the Arabic digits 0 through 9 have
>>> consecutive code points.
>> 
>>  From a programming POV the only ones that matter are the ones that can be
>> used in mathematical operations by the compiler. I doubt the arab digits or
>> any UTF comedy digits fall into that category.
>
>Unless the compiler is for a programming language in Arabic. This is an 
>extract from 
>https://github.com/nasser/---/blob/master/public/lib/mtfaail/mtfaail.qlb
>
>If I'm not mistaken, there are digits there in the first two lines.

They can do what they like with their own programming language, but in C++
the digits are 0 to 9.

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


#89286

FromPaavo Helde <eesnimi@osa.pri.ee>
Date2023-02-24 18:20 +0200
Message-ID<ttao4f$28m3f$1@dont-email.me>
In reply to#89284
24.02.2023 17:55 Muttley@dastardlyhq.com kirjutas:
> On Fri, 24 Feb 2023 15:18:55 +0200
> Paavo Helde <eesnimi@osa.pri.ee> wrote:
>> 24.02.2023 14:24 Muttley@dastardlyhq.com kirjutas:
>>> On Fri, 24 Feb 2023 12:17:06 +0100
>>> "Alf P. Steinbach" <alf.p.steinbach@gmail.com> wrote:
>>
>>>>
>>>> The /C++ standard/ guarantees that the Arabic digits 0 through 9 have
>>>> consecutive code points.
>>>
>>>   From a programming POV the only ones that matter are the ones that can be
>>> used in mathematical operations by the compiler. I doubt the arab digits or
>>> any UTF comedy digits fall into that category.
>>
>> Unless the compiler is for a programming language in Arabic. This is an
>> extract from
>> https://github.com/nasser/---/blob/master/public/lib/mtfaail/mtfaail.qlb
>>
>> If I'm not mistaken, there are digits there in the first two lines.
> 
> They can do what they like with their own programming language, but in C++
> the digits are 0 to 9.

If a compiler is meant to compile programs written in Arabic and using 
Eastern Arabic numerals, it would need to be able to recognize these 
numbers. These numbers would be used in "mathematical operations by the 
compiler" and would thus matter "from a programming POV".

Incidentally, if this compiler is written in C++, it would be C++ code 
which would need to be able to recognize these Eastern Arabic numerals.

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


#89293

FromMuttley@dastardlyhq.com
Date2023-02-24 17:05 +0000
Message-ID<ttaqph$28utp$1@dont-email.me>
In reply to#89286
On Fri, 24 Feb 2023 18:20:30 +0200
Paavo Helde <eesnimi@osa.pri.ee> wrote:
>24.02.2023 17:55 Muttley@dastardlyhq.com kirjutas:
>> They can do what they like with their own programming language, but in C++
>> the digits are 0 to 9.
>
>If a compiler is meant to compile programs written in Arabic and using 
>Eastern Arabic numerals, it would need to be able to recognize these 
>numbers. These numbers would be used in "mathematical operations by the 
>compiler" and would thus matter "from a programming POV".

man isdigit:

DESCRIPTION
     The isdigit() function tests for a decimal digit character.  Regardless
     of locale, this includes the following characters only:

     ``0''``1''``2''``3''``4''
     ``5''``6''``7''``8''``9''

     The isnumber() function behaves similarly to isdigit(), but may recognize
     additional characters, depending on the current locale setting.


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


#89296

FromPaavo Helde <eesnimi@osa.pri.ee>
Date2023-02-24 19:24 +0200
Message-ID<ttarsg$2911m$1@dont-email.me>
In reply to#89293
24.02.2023 19:05 Muttley@dastardlyhq.com kirjutas:
> On Fri, 24 Feb 2023 18:20:30 +0200
> Paavo Helde <eesnimi@osa.pri.ee> wrote:
>> 24.02.2023 17:55 Muttley@dastardlyhq.com kirjutas:
>>> They can do what they like with their own programming language, but in C++
>>> the digits are 0 to 9.
>>
>> If a compiler is meant to compile programs written in Arabic and using
>> Eastern Arabic numerals, it would need to be able to recognize these
>> numbers. These numbers would be used in "mathematical operations by the
>> compiler" and would thus matter "from a programming POV".
> 
> man isdigit:
> 
> DESCRIPTION
>       The isdigit() function tests for a decimal digit character.  Regardless
>       of locale, this includes the following characters only:
> 
>       ``0''``1''``2''``3''``4''
>       ``5''``6''``7''``8''``9''
> 
>       The isnumber() function behaves similarly to isdigit(), but may recognize
>       additional characters, depending on the current locale setting.
> 

Where did you see "isdigit" in my last response? If not, why bring it up 
again? Compilers written in other languages might even not have 
isdigit(), but would still need to parse numbers in whatever target 
language they are compiling.

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


#89301

From"james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu>
Date2023-02-24 09:46 -0800
Message-ID<e8f72b28-bdab-420b-9e65-453059b31e66n@googlegroups.com>
In reply to#89293
On Friday, February 24, 2023 at 12:06:13 PM UTC-5, Mut...@dastardlyhq.com wrote:
...
> man isdigit: 
> 
> DESCRIPTION 
> The isdigit() function tests for a decimal digit character. Regardless 
> of locale, this includes the following characters only: 
> 
> ``0''``1''``2''``3''``4'' 
> ``5''``6''``7''``8''``9'' 

That is perfectly correct, but it less authoritative than the citations
from the C standard which have already been posted to this thread,
and say the same thing (though less directly).

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


#89288

FromDavid Brown <david.brown@hesbynett.no>
Date2023-02-24 17:30 +0100
Message-ID<ttaoml$28m2r$3@dont-email.me>
In reply to#89280
On 24/02/2023 13:24, Muttley@dastardlyhq.com wrote:
> On Fri, 24 Feb 2023 12:17:06 +0100
> "Alf P. Steinbach" <alf.p.steinbach@gmail.com> wrote:

>> The /C++ standard/ guarantees that the Arabic digits 0 through 9 have
>> consecutive code points.
> 
>  From a programming POV the only ones that matter are the ones that can be
> used in mathematical operations by the compiler. I doubt the arab digits or
> any UTF comedy digits fall into that category.
> 

"Arabic numerals" or "Arabic digits" is the term used for the digits 0 
to 9, not the Arabic script numerals.

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


#89250

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-02-23 17:12 +0000
Message-ID<W7NJL.30343$Kqu2.1845@fx01.iad>
In reply to#89222
Muttley@dastardlyhq.com writes:
>On Thu, 23 Feb 2023 12:30:39 +0200
>Paavo Helde <eesnimi@osa.pri.ee> wrote:
>>23.02.2023 11:35 Muttley@dastardlyhq.com kirjutas:
>>> On Thu, 23 Feb 2023 09:39:04 +0200
>>> Paavo Helde <eesnimi@osa.pri.ee> wrote:
>>>> 22.02.2023 11:25 Muttley@dastardlyhq.com kirjutas:
>>>>
>>>>> Absolute rubbish. Why would UTF8 have anything to do with "safety"? Safety
>>>>> means will the program crash or have hidden bugs, not whether a string gets
>>
>>>>> translated into uppercase properly or not which would be immediately
>>obvious.
>>>>
>>>>
>>>>
>>>> Because you asked: I have seen isdigit() crashing hard on negative
>>> 
>>> Thats clearly a library bug. All bets are off when they exist.
>>
>>What makes you think so? The C standard clearly says in 7.4 (Character 
>>handling <ctype.h>):
>>
>>"In all cases the argument is an int, the value of which shall be
>>representable as an unsigned char or shall equal the value of the macro 
>>EOF. If the argument has any other value, the behavior is undefined."
>>
>>Undefined behavior may or may not involve a program crash.
>
>I would still consider a crash to be a bug. Undefined would just be returning
>rubbish. I can't even figure out HOW it would crash since all its doing is
>
>return (c >= '0' && c <= '9')
>
>unless there's some obscure way of doing that test even faster.

Early implementations used an array of bytes indexed by the
char value.   Each byte had a set of flags indicating character
class.  isdigit() was a macro (DEFINE) which simply tested the byte for the
DIGIT flag.  Likewise isalpha, etc.

#ifndef _U
#   define      _U      01      /* Upper case */
#   define      _L      02      /* Lower case */
#   define      _N      04      /* Numeral (digit) */
#   define      _S      010     /* Spacing character */
#   define      _P      020     /* Punctuation */
#   define      _C      040     /* Control character */
#   define      _B      0100    /* Blank */
#   define      _X      0200    /* heXadecimal digit */
#endif

#ifdef __STDC__

extern int      isalnum(int);
extern int      isalpha(int);
extern int      iscntrl(int);
extern int      isdigit(int);
extern int      isgraph(int);
extern int      islower(int);
extern int      isprint(int);
extern int      ispunct(int);
extern int      isspace(int);
extern int      isupper(int);
extern int      isxdigit(int);
extern int      tolower(int);
extern int      toupper(int);

extern int      isascii(int);
extern int      toascii(int);
extern int      _tolower(int);
extern int      _toupper(int);

extern unsigned char    __ctype[];

#if !#lint(on)

#define isalpha(c)      ((__ctype + 1)[c] & (_U | _L))
#define isupper(c)      ((__ctype + 1)[c] & _U)
#define islower(c)      ((__ctype + 1)[c] & _L)
#define isdigit(c)      ((__ctype + 1)[c] & _N)
#define isxdigit(c)     ((__ctype + 1)[c] & _X)
#define isalnum(c)      ((__ctype + 1)[c] & (_U | _L | _N))
#define isspace(c)      ((__ctype + 1)[c] & _S)
#define ispunct(c)      ((__ctype + 1)[c] & _P)
#define isprint(c)      ((__ctype + 1)[c] & (_P | _U | _L | _N | _B))
#define isgraph(c)      ((__ctype + 1)[c] & (_P | _U | _L | _N))
#define iscntrl(c)      ((__ctype + 1)[c] & _C)

#define isascii(c)      (!((c) & ~0177))

>

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


#89223

FromÖö Tiib <ootiib@hot.ee>
Date2023-02-23 02:47 -0800
Message-ID<ed03ffbd-9b3d-4d8b-8268-a8daaeeec544n@googlegroups.com>
In reply to#89220
On Thursday, 23 February 2023 at 11:35:59 UTC+2, Mut...@dastardlyhq.com wrote:
> On Thu, 23 Feb 2023 09:39:04 +0200 
> Paavo Helde <ees...@osa.pri.ee> wrote: 
> >22.02.2023 11:25 Mut...@dastardlyhq.com kirjutas: 
> > 
> >> Absolute rubbish. Why would UTF8 have anything to do with "safety"? Safety 
> >> means will the program crash or have hidden bugs, not whether a string gets 
> >> translated into uppercase properly or not which would be immediately obvious. 
> > 
> > 
> > 
> >Because you asked: I have seen isdigit() crashing hard on negative
> 
> Thats clearly a library bug. All bets are off when they exist.
> 
Nope, standard does matter only as specification. Read the licence
agreements of compilers you use or something. There are all the
warranties that you actually get and there the interesting part of our
work only starts. No bets are off ... in practice we may need to use
clearly and provably defective implementations for developing
financial applications that people use daily and trust blindly without
thinking.  We get paid well for that. 

About 15 years ago one of my teams helped programming particular 
point-of-sale credit card terminal using gcc that produced a  binary
that rebooted that terminal on case of situation that Paavo described. 
POS could talk native language of card owner (that might contain none
of Latin characters) got certified by EMV (eurocard-mastercard-visa)
and I saw it in use only few years ago.

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


#89232

FromMuttley@dastardlyhq.com
Date2023-02-23 15:59 +0000
Message-ID<tt82gj$1ti5l$1@dont-email.me>
In reply to#89223
On Thu, 23 Feb 2023 02:47:33 -0800 (PST)
=?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote:
>On Thursday, 23 February 2023 at 11:35:59 UTC+2, Mut...@dastardlyhq.com wrote:
>> On Thu, 23 Feb 2023 09:39:04 +0200 
>> Paavo Helde <ees...@osa.pri.ee> wrote: 
>> >22.02.2023 11:25 Mut...@dastardlyhq.com kirjutas: 
>> > 
>> >> Absolute rubbish. Why would UTF8 have anything to do with "safety"?
>Safety 
>> >> means will the program crash or have hidden bugs, not whether a string
>gets 
>> >> translated into uppercase properly or not which would be immediately
>obvious. 
>> > 
>> > 
>> > 
>> >Because you asked: I have seen isdigit() crashing hard on negative
>> 
>> Thats clearly a library bug. All bets are off when they exist.
>> 
>Nope, standard does matter only as specification. Read the licence

Yes.

A standard use of toupper and tolower is to iterate through a string and
apply them to whatever is there without testing each character first. If
either crashes IT IS a bug.

>agreements of compilers you use or something. There are all the
>warranties that you actually get and there the interesting part of our

Warranties are legal protection against bugs. It doesn't mean they don't exist.

>About 15 years ago one of my teams helped programming particular 
>point-of-sale credit card terminal using gcc that produced a  binary
>that rebooted that terminal on case of situation that Paavo described. 
>POS could talk native language of card owner (that might contain none
>of Latin characters) got certified by EMV (eurocard-mastercard-visa)
>and I saw it in use only few years ago.

Its still a library bug.

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


#89244

FromRichard Damon <Richard@Damon-Family.org>
Date2023-02-23 11:55 -0500
Message-ID<tUMJL.102033$eRZ7.95128@fx06.iad>
In reply to#89232
On 2/23/23 10:59 AM, Muttley@dastardlyhq.com wrote:
> On Thu, 23 Feb 2023 02:47:33 -0800 (PST)
> =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote:
>> On Thursday, 23 February 2023 at 11:35:59 UTC+2, Mut...@dastardlyhq.com wrote:
>>> On Thu, 23 Feb 2023 09:39:04 +0200
>>> Paavo Helde <ees...@osa.pri.ee> wrote:
>>>> 22.02.2023 11:25 Mut...@dastardlyhq.com kirjutas:
>>>>
>>>>> Absolute rubbish. Why would UTF8 have anything to do with "safety"?
>> Safety
>>>>> means will the program crash or have hidden bugs, not whether a string
>> gets
>>>>> translated into uppercase properly or not which would be immediately
>> obvious.
>>>>
>>>>
>>>>
>>>> Because you asked: I have seen isdigit() crashing hard on negative
>>>
>>> Thats clearly a library bug. All bets are off when they exist.
>>>
>> Nope, standard does matter only as specification. Read the licence
> 
> Yes.
> 
> A standard use of toupper and tolower is to iterate through a string and
> apply them to whatever is there without testing each character first. If
> either crashes IT IS a bug.

and the loop, if reading from a "char" string needs to cast the 
character to "unsigned char" before giving it to toupper/tolower.

The original definitions of the functions were based on input loops that 
read using a function that returned an int (not a char) that returned -1 
for EOF or a non-negative value that represented the character.

> 
>> agreements of compilers you use or something. There are all the
>> warranties that you actually get and there the interesting part of our
> 
> Warranties are legal protection against bugs. It doesn't mean they don't exist.

And the C standard explicitly provides no "warranties" for code that 
performs "Undefined Behavior"

> 
>> About 15 years ago one of my teams helped programming particular
>> point-of-sale credit card terminal using gcc that produced a  binary
>> that rebooted that terminal on case of situation that Paavo described.
>> POS could talk native language of card owner (that might contain none
>> of Latin characters) got certified by EMV (eurocard-mastercard-visa)
>> and I saw it in use only few years ago.
> 
> Its still a library bug.
> 

Nope, calling toupper with a value outside its define input range (which 
has only 1 possibly negative value, that of EOF) is explicitly defined 
to be "Undefined Behavior", so the PROGRAM that does that has the bug, 
not the library, which met its requirements.

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


#89242

From"james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu>
Date2023-02-23 08:37 -0800
Message-ID<d6f30292-d735-4792-ae20-500f7360eeacn@googlegroups.com>
In reply to#89220
On Thursday, February 23, 2023 at 4:35:59 AM UTC-5, Mut...@dastardlyhq.com wrote:
> On Thu, 23 Feb 2023 09:39:04 +0200 
> Paavo Helde <ees...@osa.pri.ee> wrote: 
...
> >Because you asked: I have seen isdigit() crashing hard on negative
> Thats clearly a library bug. All bets are off when they exist.

The standard requires that the value be either EOF or representable as an unsigned
char. That permits the very common implementation of isdigit()  as

static unsigned _ctype_table[UCHAR_MAX-EOF];
int isdigit(int c) { return _ctype_table[c-EOF] & _DIGIT_BIT_; }
// Each of the other <ctype.h> functions uses the same table,
// masking off a different bit pattern.

Anything you do to modify that code to make it safe to pass numbers less than EOF 
or greater than UCHAR_MAX would make it less efficient, and would only benefit
code that has undefined behavior. Many implementations provide such safety only in
a special debugging mode.

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


#89261

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-02-23 14:19 -0800
Message-ID<87cz60owhg.fsf@nosuchdomain.example.com>
In reply to#89242
"james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> writes:
> On Thursday, February 23, 2023 at 4:35:59 AM UTC-5, Mut...@dastardlyhq.com wrote:
>> On Thu, 23 Feb 2023 09:39:04 +0200 
>> Paavo Helde <ees...@osa.pri.ee> wrote: 
> ...
>> >Because you asked: I have seen isdigit() crashing hard on negative
>> Thats clearly a library bug. All bets are off when they exist.
>
> The standard requires that the value be either EOF or representable as an unsigned
> char. That permits the very common implementation of isdigit()  as
>
> static unsigned _ctype_table[UCHAR_MAX-EOF];
> int isdigit(int c) { return _ctype_table[c-EOF] & _DIGIT_BIT_; }
> // Each of the other <ctype.h> functions uses the same table,
> // masking off a different bit pattern.
>
> Anything you do to modify that code to make it safe to pass numbers less than EOF 
> or greater than UCHAR_MAX would make it less efficient, and would only benefit
> code that has undefined behavior. Many implementations provide such safety only in
> a special debugging mode.

An implementation could make _ctype_table cover values from SCHAR_MIN to
UCHAR_MAX and use an SCHAR_MIN offset when indexing it.  That would make
it well defined for any value within the range of signed char, char, or
unsigned char.  No implementations are *required* to do this, but any
that do will avoid crashing when passing arbitrary char values to the
is*() and to() functions.

GNU's glibc appears to do something like this.

I'd like to see a future standard require well defined behavior for all
values from SCHAR_MIN to UCHAR_MAX.

(There could be a problem treating -1 as EOF and 255 as the letter 'ÿ'.
I'm tempted to argue that the special treatment of EOF has outlived its
usefulness, but I'm not suggesting a breaking change.)

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for XCOM Labs
void Void(void) { Void(); } /* The recursive call of the void */

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


#89248

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-02-23 17:09 +0000
Message-ID<z5NJL.30342$Kqu2.15860@fx01.iad>
In reply to#89215
Paavo Helde <eesnimi@osa.pri.ee> writes:
>22.02.2023 11:25 Muttley@dastardlyhq.com kirjutas:
>
>> Absolute rubbish. Why would UTF8 have anything to do with "safety"? Safety
>> means will the program crash or have hidden bugs, not whether a string gets
>> translated into uppercase properly or not which would be immediately obvious.
>
>
>Because you asked: I have seen isdigit() crashing hard on negative 
>values, would not be surprised if toupper() would behave the same in 
>some implementation.

It was not uncommon in early implementations to for isdigit et al
to simply index into an array of bytes.  Any value not between
zero and 255 would result in UB.

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


#89253

FromRichard Damon <Richard@Damon-Family.org>
Date2023-02-23 12:21 -0500
Message-ID<IgNJL.1596352$GNG9.835554@fx18.iad>
In reply to#89248
On 2/23/23 12:09 PM, Scott Lurndal wrote:
> Paavo Helde <eesnimi@osa.pri.ee> writes:
>> 22.02.2023 11:25 Muttley@dastardlyhq.com kirjutas:
>>
>>> Absolute rubbish. Why would UTF8 have anything to do with "safety"? Safety
>>> means will the program crash or have hidden bugs, not whether a string gets
>>> translated into uppercase properly or not which would be immediately obvious.
>>
>>
>> Because you asked: I have seen isdigit() crashing hard on negative
>> values, would not be surprised if toupper() would behave the same in
>> some implementation.
> 
> It was not uncommon in early implementations to for isdigit et al
> to simply index into an array of bytes.  Any value not between
> zero and 255 would result in UB.
> 

-1 and 255, since EOF was explicitly an allowed value.

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


#89254

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-02-23 17:55 +0000
Message-ID<tMNJL.776317$gGD7.186626@fx11.iad>
In reply to#89253
Richard Damon <Richard@Damon-Family.org> writes:
>On 2/23/23 12:09 PM, Scott Lurndal wrote:
>> Paavo Helde <eesnimi@osa.pri.ee> writes:
>>> 22.02.2023 11:25 Muttley@dastardlyhq.com kirjutas:
>>>
>>>> Absolute rubbish. Why would UTF8 have anything to do with "safety"? Safety
>>>> means will the program crash or have hidden bugs, not whether a string gets
>>>> translated into uppercase properly or not which would be immediately obvious.
>>>
>>>
>>> Because you asked: I have seen isdigit() crashing hard on negative
>>> values, would not be surprised if toupper() would behave the same in
>>> some implementation.
>> 
>> It was not uncommon in early implementations to for isdigit et al
>> to simply index into an array of bytes.  Any value not between
>> zero and 255 would result in UB.
>> 
>
>-1 and 255, since EOF was explicitly an allowed value.

Not in SVR4.2, see msg <W7NJL.30343$Kqu2.1845@fx01.iad>

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


#89260

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-02-23 13:57 -0800
Message-ID<87h6vcoxi0.fsf@nosuchdomain.example.com>
In reply to#89254
scott@slp53.sl.home (Scott Lurndal) writes:
> Richard Damon <Richard@Damon-Family.org> writes:
>>On 2/23/23 12:09 PM, Scott Lurndal wrote:
>>> Paavo Helde <eesnimi@osa.pri.ee> writes:
>>>> 22.02.2023 11:25 Muttley@dastardlyhq.com kirjutas:
>>>>
>>>>> Absolute rubbish. Why would UTF8 have anything to do with "safety"? Safety
>>>>> means will the program crash or have hidden bugs, not whether a string gets
>>>>> translated into uppercase properly or not which would be immediately obvious.
>>>>
>>>>
>>>> Because you asked: I have seen isdigit() crashing hard on negative
>>>> values, would not be surprised if toupper() would behave the same in
>>>> some implementation.
>>> 
>>> It was not uncommon in early implementations to for isdigit et al
>>> to simply index into an array of bytes.  Any value not between
>>> zero and 255 would result in UB.
>>> 
>>
>>-1 and 255, since EOF was explicitly an allowed value.
>
> Not in SVR4.2, see msg <W7NJL.30343$Kqu2.1845@fx01.iad>

Yes in SVR4.2.  The code in the cited article allows for a -1 argument.

    extern unsigned char    __ctype[];
    [...]
    #define isalpha(c)      ((__ctype + 1)[c] & (_U | _L))

Adding 1 to the array address allows for an index of -1.

(The standard requires EOF to have a negative value.  This is a good
reason for it to be exactly -1, and I've never heard of an
implementation where EOF != -1.)

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for XCOM Labs
void Void(void) { Void(); } /* The recursive call of the void */

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


#89265

FromAndrey Tarasevich <andreytarasevich@hotmail.com>
Date2023-02-23 17:28 -0800
Message-ID<tt93sg$20uin$1@dont-email.me>
In reply to#89260
On 02/23/23 1:57 PM, Keith Thompson wrote:
> (The standard requires EOF to have a negative value.  This is a good
> reason for it to be exactly -1, and I've never heard of an
> implementation where EOF != -1.)

https://github.com/xinu-os/xinu/blob/master/include/stddef.h

--
Best regards,
Andrey

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


Page 9 of 11 — ← Prev page 1 … 7 8 [9] 10 11  Next page →

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


csiph-web