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


Groups > comp.lang.c > #83511 > unrolled thread

Testing nodes and lists for hashtable

Started byAlla _ <modelling.data@gmail.com>
First post2016-03-09 00:52 -0800
Last post2016-03-30 07:00 -0700
Articles 20 on this page of 330 — 24 participants

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


Contents

  Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 00:52 -0800
    Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-09 10:13 +0000
      Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 02:19 -0800
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 02:23 -0800
        Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-09 13:00 +0000
    Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-09 02:38 -0800
      Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 02:59 -0800
        Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-09 10:35 -0800
          Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-10 00:20 -0800
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 02:56 -0800
      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-09 13:11 +0000
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 06:37 -0800
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-09 15:50 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 08:19 -0800
              Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-09 17:18 +0000
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-10 00:11 -0800
                  Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-10 08:48 +0000
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-10 04:17 -0800
                  Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-10 11:12 +0000
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-10 04:16 -0800
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-10 04:20 -0800
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 08:41 -0800
              Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-09 17:27 +0000
                Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-09 22:41 -0600
                  Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-10 10:38 +0000
                    Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-10 09:37 -0600
                      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-10 15:51 +0000
                        Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-10 18:42 -0600
                        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 04:17 -0800
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-10 00:18 -0800
                  Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-10 08:51 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 08:50 -0800
    Re: Testing nodes and lists for hashtable jadill33@gmail.com - 2016-03-09 07:16 -0800
    Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-09 09:27 -0600
      Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-09 07:46 -0800
        Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-09 10:56 -0800
          Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-10 00:25 -0800
            Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-10 08:55 -0800
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 01:14 -0800
      Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-11 01:53 -0800
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 02:25 -0800
          Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-11 12:31 -0800
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-12 00:03 -0800
              Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-12 09:04 -0800
        Re: Testing nodes and lists for hashtable mark.bluemel@gmail.com - 2016-03-11 02:30 -0800
          Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 02:39 -0800
            Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-11 02:52 -0800
              Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 04:09 -0800
              Re: Testing nodes and lists for hashtable mark.bluemel@gmail.com - 2016-03-14 08:41 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 02:34 -0800
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 02:41 -0800
          Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-11 12:14 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 04:20 -0800
              Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-11 12:33 +0000
              Re: Testing nodes and lists for hashtable Randy Howard <rhoward.mx@EverybodyUsesIt.com> - 2016-03-11 12:12 -0600
                Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-11 10:24 -0800
                Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-11 19:04 +0000
                  Re: Testing nodes and lists for hashtable Randy Howard <rhoward.mx@EverybodyUsesIt.com> - 2016-03-11 14:20 -0600
                  Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 23:55 -0800
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 04:23 -0800
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 04:25 -0800
              Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-11 12:36 +0000
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 05:56 -0800
                  Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-11 14:55 +0000
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 07:22 -0800
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 07:29 -0800
                      Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-11 16:01 +0000
                        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 23:41 -0800
                          Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-13 13:48 +0000
                    Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-11 20:20 +0000
                      Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-13 13:06 +0000
                  Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-12 17:41 -0600
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-13 05:03 -0700
                      Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-13 13:50 +0000
                        Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-13 10:32 -0500
                          Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-13 09:18 -0700
                          Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-13 16:31 +0000
                            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-13 10:17 -0700
                      Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-13 10:17 -0500
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-13 09:06 -0700
                      Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-13 09:51 -0700
                        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-13 10:31 -0700
                      Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-13 12:41 -0500
      Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-11 08:41 -0800
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-11 23:54 -0800
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-12 08:10 -0800
      Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-12 08:17 -0800
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-12 08:19 -0800
          Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-12 09:16 -0800
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-13 04:17 -0700
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-12 19:37 +0000
            Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-13 11:20 -0500
              Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-13 21:37 +0000
        Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-12 09:48 -0800
          Re: Testing nodes and lists for hashtable raltbos@xs4all.nl (Richard Bos) - 2016-03-12 20:31 +0000
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-12 21:18 +0000
          Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-12 17:54 -0600
          Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-13 04:25 -0700
            Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-13 04:44 -0700
              Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-13 12:31 -0500
                Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-13 11:14 -0700
                  Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-13 16:17 -0500
                    Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-13 14:37 -0700
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-13 11:43 -0700
      Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-13 12:08 -0700
      Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-13 16:31 -0500
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 01:12 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 01:21 -0700
          Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-14 13:48 -0500
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 01:43 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 01:35 -0700
          Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-14 13:44 -0500
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 01:39 -0700
      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-13 23:04 +0000
        Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-13 16:09 -0700
          Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-13 17:54 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 01:58 -0700
          Re: Testing nodes and lists for hashtable fir <profesor.fir@gmail.com> - 2016-03-14 03:08 -0700
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-14 10:59 +0000
            Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-14 04:59 -0700
              Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-14 13:15 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 11:09 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 03:18 -0700
          Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-14 11:03 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 11:17 -0700
              Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-14 15:16 -0700
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 01:59 -0700
                  Re: Testing nodes and lists for hashtable Barry Schwarz <schwarz45@yahoo.com> - 2016-03-15 20:13 -0700
                    Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-15 22:09 -0700
                    Re: Testing nodes and lists for hashtable BartC <bc@freeuk.com> - 2016-03-16 11:53 +0000
                    Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 09:39 -0500
                      Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 07:57 -0700
                        Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-16 08:38 -0700
                          Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 09:04 -0700
                            Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 11:22 -0500
                            Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-16 10:42 -0700
                              Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 10:57 -0700
                                Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-16 11:57 -0700
                        Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 10:43 -0500
                      Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-16 10:59 -0700
                        Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 13:22 -0500
                          Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-16 16:09 -0700
                            Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-16 17:03 -0700
                            Re: Testing nodes and lists for hashtable raltbos@xs4all.nl (Richard Bos) - 2016-03-20 13:04 +0000
                            Re: Testing nodes and lists for hashtable Tim Rentsch <txr@alumni.caltech.edu> - 2016-03-30 09:07 -0700
                              Re: Testing nodes and lists for hashtable luser droog <luser.droog@gmail.com> - 2016-03-31 20:34 -0700
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-14 14:04 +0000
          Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-14 11:07 -0700
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 03:49 -0700
      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-14 13:03 +0000
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 11:24 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-14 11:41 -0700
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-14 19:35 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 01:53 -0700
              Re: Testing nodes and lists for hashtable luser droog <luser.droog@gmail.com> - 2016-03-15 02:03 -0700
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 02:09 -0700
                  Re: Testing nodes and lists for hashtable luser droog <luser.droog@gmail.com> - 2016-03-15 02:13 -0700
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 02:22 -0700
                  Re: Testing nodes and lists for hashtable luser droog <luser.droog@gmail.com> - 2016-03-15 02:15 -0700
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 02:28 -0700
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 02:30 -0700
              Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-15 09:13 +0000
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 02:28 -0700
                Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-15 03:15 -0700
                  Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-15 13:26 +0000
                  Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-15 09:18 -0700
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 03:19 -0700
                  Re: Testing nodes and lists for hashtable David Brown <david.brown@hesbynett.no> - 2016-03-15 15:21 +0100
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 08:39 -0700
                      Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-15 09:26 -0700
                        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 00:10 -0700
                  Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-15 09:19 -0700
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 00:08 -0700
                      Re: Testing nodes and lists for hashtable David Brown <david.brown@hesbynett.no> - 2016-03-16 08:55 +0100
                      Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-16 09:17 -0700
                        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 09:25 -0700
          Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-14 13:06 -0700
            Re: Testing nodes and lists for hashtable Gareth Owen <gwowen@gmail.com> - 2016-03-14 20:29 +0000
            Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-14 21:03 +0000
              Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-14 14:57 -0700
                Re: Testing nodes and lists for hashtable raltbos@xs4all.nl (Richard Bos) - 2016-03-14 22:35 +0000
              Re: Testing nodes and lists for hashtable David Brown <david.brown@hesbynett.no> - 2016-03-16 19:47 +0100
            Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-14 14:26 -0700
      Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-14 11:37 -0700
      Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-14 11:37 -0700
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-15 08:58 -0700
      Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-15 16:12 +0000
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 00:04 -0700
      Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-15 10:48 -0700
        Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-15 18:00 +0000
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-15 19:20 +0000
            Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-15 21:24 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 00:50 -0700
              Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-16 11:19 +0000
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 04:37 -0700
                  Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 11:51 +0000
                    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 05:20 -0700
                      Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 07:13 -0700
                        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 09:05 -0700
                Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 11:45 +0000
                  Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-16 13:46 +0000
                    Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 14:00 +0000
                    Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 07:05 -0700
                      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-16 16:42 +0000
                        Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 10:21 -0700
                          Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 17:33 +0000
                            Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 10:44 -0700
                              Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 18:00 +0000
                                Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 11:08 -0700
                                  Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 18:19 +0000
                                    Re: Testing nodes and lists for hashtable Gareth Owen <gwowen@gmail.com> - 2016-03-16 19:38 +0000
                                      Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 14:00 -0700
                                      Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 21:52 +0000
                                        Re: Testing nodes and lists for hashtable Gareth Owen <gwowen@gmail.com> - 2016-03-16 22:12 +0000
                                Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 13:39 -0500
                          Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-16 15:39 -0700
                            Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-17 02:59 +0000
                              Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-17 04:20 -0700
                                Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-17 23:46 +0000
                                  Re: Testing nodes and lists for hashtable Jerry Stuckle <jstucklex@attglobal.net> - 2016-03-17 20:04 -0400
                                    Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-18 01:05 +0000
                                      Re: Testing nodes and lists for hashtable Jerry Stuckle <jstucklex@attglobal.net> - 2016-03-17 22:35 -0400
                                  Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-17 17:19 -0700
                                    Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-18 01:39 +0000
                                      Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-18 02:54 -0700
                                        Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-18 09:08 -0500
                                          Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-18 11:20 -0700
                                        Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-18 21:29 +0000
                                          Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-18 17:48 -0700
                            Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 22:09 -0500
                              Re: Testing nodes and lists for hashtable raltbos@xs4all.nl (Richard Bos) - 2016-03-17 11:49 +0000
                                Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-17 08:45 -0700
                                Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-17 12:11 -0500
                                  Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-17 10:31 -0700
                                    Re: Testing nodes and lists for hashtable Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-03-17 11:09 -0700
                                      Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-17 16:15 -0500
                                      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-18 00:39 +0000
                      Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 12:04 -0500
                    Re: Testing nodes and lists for hashtable Steve Thompson <stevet810@gmail.com> - 2016-03-17 14:21 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 00:53 -0700
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 01:00 -0700
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 01:24 -0700
              Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-16 11:08 +0000
                Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 11:25 +0000
          Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 00:41 -0700
            Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 08:27 -0500
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 06:43 -0700
      Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 14:07 +0000
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 08:16 -0700
          Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-16 15:25 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 08:30 -0700
      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-16 20:32 +0000
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 03:26 -0700
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-17 16:15 +0000
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 11:07 -0700
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 08:47 -0700
      Re: Testing nodes and lists for hashtable Stephen Sprunk <stephen@sprunk.org> - 2016-03-16 10:54 -0500
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 09:35 -0700
      Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-16 11:31 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 02:53 -0700
          Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-28 18:08 -0700
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 02:07 -0700
              Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-30 09:45 -0700
                Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-30 17:54 +0100
      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-16 20:26 +0000
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 03:00 -0700
          Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-17 16:05 +0000
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-16 09:10 -0700
      Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-16 12:24 -0700
        Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-16 13:16 -0700
          Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-16 16:20 -0700
            Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-16 16:54 -0700
            Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-16 17:27 -0700
        Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-16 13:18 -0700
      Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-16 20:21 +0000
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 04:23 -0700
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 04:47 -0700
      Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 05:40 -0700
        Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-17 12:49 +0000
          Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 06:45 -0700
        Re: Testing nodes and lists for hashtable mark.bluemel@gmail.com - 2016-03-17 10:00 -0700
          Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-17 12:40 -0700
    Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-28 12:00 -0700
      Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-28 12:37 -0700
        Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-28 17:43 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 01:31 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 01:55 -0700
          Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-30 10:23 +0100
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 02:32 -0700
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 02:33 -0700
          Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 07:04 -0700
            Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-30 15:17 +0100
              Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 07:46 -0700
                Re: Testing nodes and lists for hashtable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-03-30 16:41 +0100
                  Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 09:16 -0700
                    Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 09:18 -0700
                    Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 09:37 -0700
          Re: Testing nodes and lists for hashtable Barry Schwarz <schwarzb@dqel.com> - 2016-03-30 10:32 -0700
            Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-30 12:10 -0700
      Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-28 17:42 -0700
        Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-29 08:51 -0700
          Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-29 09:56 -0700
            Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-29 12:09 -0700
              Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-29 16:34 -0700
                Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-29 16:50 -0700
                  Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-29 17:17 -0700
                  Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 02:30 -0700
                Re: Testing nodes and lists for hashtable Richard Heathfield <rjh@cpax.org.uk> - 2016-03-30 00:52 +0100
                  Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-29 17:27 -0700
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 02:26 -0700
                  Re: Testing nodes and lists for hashtable mark.bluemel@gmail.com - 2016-03-30 07:09 -0700
                  Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 07:33 -0700
                    Re: Testing nodes and lists for hashtable Jerry Stuckle <jstucklex@attglobal.net> - 2016-03-30 11:32 -0400
                      Re: Testing nodes and lists for hashtable mrs@kithrup.com (Mike Stump) - 2016-04-29 08:21 +0000
                        Re: Testing nodes and lists for hashtable Jerry Stuckle <jstucklex@attglobal.net> - 2016-04-29 10:35 -0400
                          Re: Testing nodes and lists for hashtable Ken Brody <kenbrody@spamcop.net> - 2016-04-29 11:29 -0400
                            Re: Testing nodes and lists for hashtable Jerry Stuckle <jstucklex@attglobal.net> - 2016-04-29 12:21 -0400
                              Re: Testing nodes and lists for hashtable Ken Brody <kenbrody@spamcop.net> - 2016-05-02 11:55 -0400
                                Re: Testing nodes and lists for hashtable Jerry Stuckle <jstucklex@attglobal.net> - 2016-05-02 13:13 -0400
                  Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-30 08:15 -0700
                    Re: Testing nodes and lists for hashtable Jerry Stuckle <jstucklex@attglobal.net> - 2016-03-30 11:39 -0400
                      Re: Testing nodes and lists for hashtable supercat@casperkitty.com - 2016-03-30 09:47 -0700
                  Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 08:48 -0700
            Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 02:18 -0700
              Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 06:56 -0700
                Re: Testing nodes and lists for hashtable Keith Thompson <kst-u@mib.org> - 2016-03-30 09:04 -0700
                  Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 09:25 -0700
                Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-04-01 00:52 -0700
        Re: Testing nodes and lists for hashtable Alla _ <modelling.data@gmail.com> - 2016-03-30 02:05 -0700
          Re: Testing nodes and lists for hashtable Geoff <geoff@invalid.invalid> - 2016-03-30 07:00 -0700

Page 16 of 17 — ← Prev page 1 … 14 15 [16] 17  Next page →


#85237

FromKeith Thompson <kst-u@mib.org>
Date2016-03-29 08:51 -0700
Message-ID<ln37r92sg2.fsf@kst-u.example.com>
In reply to#85213
Geoff <geoff@invalid.invalid> writes:
> On Mon, 28 Mar 2016 12:00:23 -0700 (PDT), Alla _
> <modelling.data@gmail.com> wrote:
>
>>I have to learn more about this issue, it's interesting )
>
> You probably created your dictionary file in Apple's TextEdit
> application. The default open and save character mode for TextEdit is
> "automatic". When it's in automatic it saves text files in UTF-8.
>
> Furthermore, even the U.S. MacBook Pro keyboard produces the
> right-single quote symbol you encountered in your data file.
>
> To produce the single-quote ASCII symbol on a Mac keyboard, type
> ctrl-' and you will see ' and not ’.

And in another article:

> It's a keyboard issue. She's on a MacBook Pro.

I'm still skeptical.

I have a Mac (not a MacBook Pro) running MacOS 10.5.8.  If TextEdit
behaves as you describe, it's because it's translating an input
apostrophe character (or the scan code it sends) to a right single
quote symbol as you type it.  If typing that key gets you a right
single quote *when you type it at a shell prompt*, then it's probably
a keyboard issue.  If not, it's just how TextEdit behaves.

I don't see that behavior in TextEdit myself.  Either I'm doing
something different from what you're doing, or the older version
I'm using behaves differently from yours, or *maybe* because I'm
using a non-Mac keyboard.  But I don't believe using a Mac keyboard
on a Mac would make it that inconvenient to type ASCII text.

In any case, TextEdit is only one possible source of that non-ASCII
character.  It could as easily have been copy-and-pasted from a
web page or some word processor document.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

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


#85243

FromGeoff <geoff@invalid.invalid>
Date2016-03-29 09:56 -0700
Message-ID<italfb93buflkulhaa4nbopaivimushqv3@4ax.com>
In reply to#85237
On Tue, 29 Mar 2016 08:51:25 -0700, Keith Thompson <kst-u@mib.org>
wrote:

>Geoff <geoff@invalid.invalid> writes:
>> On Mon, 28 Mar 2016 12:00:23 -0700 (PDT), Alla _
>> <modelling.data@gmail.com> wrote:
>>
>>>I have to learn more about this issue, it's interesting )
>>
>> You probably created your dictionary file in Apple's TextEdit
>> application. The default open and save character mode for TextEdit is
>> "automatic". When it's in automatic it saves text files in UTF-8.
>>
>> Furthermore, even the U.S. MacBook Pro keyboard produces the
>> right-single quote symbol you encountered in your data file.
>>
>> To produce the single-quote ASCII symbol on a Mac keyboard, type
>> ctrl-' and you will see ' and not ’.
>
>And in another article:
>
>> It's a keyboard issue. She's on a MacBook Pro.
>
>I'm still skeptical.
>
>I have a Mac (not a MacBook Pro) running MacOS 10.5.8.  If TextEdit
>behaves as you describe, it's because it's translating an input
>apostrophe character (or the scan code it sends) to a right single
>quote symbol as you type it.  If typing that key gets you a right
>single quote *when you type it at a shell prompt*, then it's probably
>a keyboard issue.  If not, it's just how TextEdit behaves.
>

Since all keyboards emit scan codes, then yes, it's a keyboard
translation problem. (see below)

>I don't see that behavior in TextEdit myself.  Either I'm doing
>something different from what you're doing, or the older version
>I'm using behaves differently from yours, or *maybe* because I'm
>using a non-Mac keyboard.  But I don't believe using a Mac keyboard
>on a Mac would make it that inconvenient to type ASCII text.
>

It took a little digging but I compared TextEdit v1.6 on OSX 10.6.8 on
my iMac and Apple keyboard with the behavior of TextEdit v1.10 on OSX
10.10.5 on my MacBook Pro's builtin keyboard. It turns out the culprit
is the keyboard translation can be modified two ways. In System
Preferences, Keyboard, Text tab, there's a setting for "smart quotes
and dashes" where double and single quotes are paired as left-right
pairs and corresponding internationalizations can be specified or
disabled and in TextEdit itself, by turning off the 'Smart quotes'
checkbox. The older OS and TextEdit have no such options.

The smart quotes issue is non-existent in the Xcode IDE and in the
terminal console. This source of confusion and IMO malfunction, is not
surprising - since Jony Ive took over leadership of software
development as well as hardware, the software at Almighty Apple has
replaced functional consistency and correctness with esthetics and
incorrect default behavior.

Witness, 7 months of 'Beta' testing of iOS 9.3, only to be retracted
and micro-patched because of platform inconsistencies that bricked
many iPhones.

>In any case, TextEdit is only one possible source of that non-ASCII
>character.  It could as easily have been copy-and-pasted from a
>web page or some word processor document.

Until Alla_ replies, my money is on TextEdit being the source. She
never stated the source of her data file and it's only alluded to in
the C source she posted. I don't remember the version of OSX she was
using if she stated it when I queried her about her platform.

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


#85257

FromKeith Thompson <kst-u@mib.org>
Date2016-03-29 12:09 -0700
Message-ID<lnlh5114py.fsf@kst-u.example.com>
In reply to#85243
Geoff <geoff@invalid.invalid> writes:
> On Tue, 29 Mar 2016 08:51:25 -0700, Keith Thompson <kst-u@mib.org>
> wrote:
>>Geoff <geoff@invalid.invalid> writes:
>>> On Mon, 28 Mar 2016 12:00:23 -0700 (PDT), Alla _
[...]
>>> It's a keyboard issue. She's on a MacBook Pro.
>>
>>I'm still skeptical.
>>
>>I have a Mac (not a MacBook Pro) running MacOS 10.5.8.  If TextEdit
>>behaves as you describe, it's because it's translating an input
>>apostrophe character (or the scan code it sends) to a right single
>>quote symbol as you type it.  If typing that key gets you a right
>>single quote *when you type it at a shell prompt*, then it's probably
>>a keyboard issue.  If not, it's just how TextEdit behaves.
>>
>
> Since all keyboards emit scan codes, then yes, it's a keyboard
> translation problem. (see below)

I'd say a "keyboard translation problem" is not a "keyboard problem".
When you said it was probably a "keyboard problem", I assumed you meant
it was a hardware (or perhaps firmware) issue with the keyboard itself.
It sounds like the keyboard is working just fine; the software is
choosing to translate keyboard input.  At least for double quotes, I
gather that it generates both opening and closing quotation marks;
surely the keyboard is not involved in the decision of which to use.

[...]

> The smart quotes issue is non-existent in the Xcode IDE and in the
> terminal console.

Which implies that it's a software issue, yes?

[...]

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

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


#85281

FromGeoff <geoff@invalid.invalid>
Date2016-03-29 16:34 -0700
Message-ID<2b3mfb96ri0p40dd60cdpjo2rpq12unsbj@4ax.com>
In reply to#85257
On Tue, 29 Mar 2016 12:09:13 -0700, Keith Thompson <kst-u@mib.org>
wrote:

>Geoff <geoff@invalid.invalid> writes:
>> On Tue, 29 Mar 2016 08:51:25 -0700, Keith Thompson <kst-u@mib.org>
>> wrote:
>>>Geoff <geoff@invalid.invalid> writes:
>>>> On Mon, 28 Mar 2016 12:00:23 -0700 (PDT), Alla _
>[...]
>>>> It's a keyboard issue. She's on a MacBook Pro.
>>>
>>>I'm still skeptical.
>>>
>>>I have a Mac (not a MacBook Pro) running MacOS 10.5.8.  If TextEdit
>>>behaves as you describe, it's because it's translating an input
>>>apostrophe character (or the scan code it sends) to a right single
>>>quote symbol as you type it.  If typing that key gets you a right
>>>single quote *when you type it at a shell prompt*, then it's probably
>>>a keyboard issue.  If not, it's just how TextEdit behaves.
>>>
>>
>> Since all keyboards emit scan codes, then yes, it's a keyboard
>> translation problem. (see below)
>
>I'd say a "keyboard translation problem" is not a "keyboard problem".
>When you said it was probably a "keyboard problem", I assumed you meant
>it was a hardware (or perhaps firmware) issue with the keyboard itself.

No, that's not what I meant, obviously. Are you this pedantic in
person or is this a persona you adopt online?

It must be hard to have a simple conversation with you. If I said "My
car makes noise when it moves, I think I need the brakes checked." I
expect you'd tell me it's the engine or the turbulent airflow and not
the brakes because I've ignored those scenarios and not properly
described the noise for diagnostic purposes.

>It sounds like the keyboard is working just fine; the software is
>choosing to translate keyboard input.  At least for double quotes, I
>gather that it generates both opening and closing quotation marks;
>surely the keyboard is not involved in the decision of which to use.
>
>[...]
>
>> The smart quotes issue is non-existent in the Xcode IDE and in the
>> terminal console.
>
>Which implies that it's a software issue, yes?
>

Since all keyboards on the planet that aren't ASCII keyboards with
RS-232 interfaces are emitting scan codes that are interpreted by the
systems they are interfaced with, I'd say "keyboard problem" and
"keyboard translation problem" are functionally identical for the
purpose of solving Alla_'s mystery of how she didn't get the
apostrophe she was expecting. The fact the keyboard translation is
configurable makes the problem solvable, at least for text that was
input from the keyboard and not copy-pasted from the web. My point was
that she need not have copied the text from the web to obtain the
offending character. I haven't seen a true ASCII keyboard since 1986
and even then it was on a proprietary control and not a PC.

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


#85282

FromKeith Thompson <kst-u@mib.org>
Date2016-03-29 16:50 -0700
Message-ID<lnshz8zvw8.fsf@kst-u.example.com>
In reply to#85281
Geoff <geoff@invalid.invalid> writes:
> On Tue, 29 Mar 2016 12:09:13 -0700, Keith Thompson <kst-u@mib.org>
> wrote:
[...]
>>I'd say a "keyboard translation problem" is not a "keyboard problem".
>>When you said it was probably a "keyboard problem", I assumed you meant
>>it was a hardware (or perhaps firmware) issue with the keyboard itself.
>
> No, that's not what I meant, obviously.

It wasn't obvious to me -- obviously.

>                                         Are you this pedantic in
> person or is this a persona you adopt online?

If you're going to insult me because I didn't understand what
you meant, as opposed to what you said, then I'm done with this
conversation.

[...]

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

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


#85284

FromGeoff <geoff@invalid.invalid>
Date2016-03-29 17:17 -0700
Message-ID<7j6mfblc98jkd9vec4ukte973ufhb82gu9@4ax.com>
In reply to#85282
On Tue, 29 Mar 2016 16:50:31 -0700, Keith Thompson <kst-u@mib.org>
wrote:

>Geoff <geoff@invalid.invalid> writes:
>> On Tue, 29 Mar 2016 12:09:13 -0700, Keith Thompson <kst-u@mib.org>
>> wrote:
>[...]
>>>I'd say a "keyboard translation problem" is not a "keyboard problem".
>>>When you said it was probably a "keyboard problem", I assumed you meant
>>>it was a hardware (or perhaps firmware) issue with the keyboard itself.
>>
>> No, that's not what I meant, obviously.
>
>It wasn't obvious to me -- obviously.
>
>>                                         Are you this pedantic in
>> person or is this a persona you adopt online?
>
>If you're going to insult me because I didn't understand what
>you meant, as opposed to what you said, then I'm done with this
>conversation.
>
>[...]

Hmmm... a question is an insult? I would have asked you the same
question in person had you taken that tone in voice as you did in your
writing. But I grew tired of this kind of mental masturbation about
trivialities a very long time ago.

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


#85297

FromAlla _ <modelling.data@gmail.com>
Date2016-03-30 02:30 -0700
Message-ID<2939fde7-39d3-4a4b-bc24-c85e5e24ecca@googlegroups.com>
In reply to#85282
On Wednesday, March 30, 2016 at 3:50:40 AM UTC+4, Keith Thompson wrote:
> Geoff <geoff@invalid.invalid> writes:
> > On Tue, 29 Mar 2016 12:09:13 -0700, Keith Thompson <kst-u@mib.org>
> > wrote:
> [...]
> >>I'd say a "keyboard translation problem" is not a "keyboard problem".
> >>When you said it was probably a "keyboard problem", I assumed you meant
> >>it was a hardware (or perhaps firmware) issue with the keyboard itself.
> >
> > No, that's not what I meant, obviously.
> 
> It wasn't obvious to me -- obviously.
> 
> >                                         Are you this pedantic in
> > person or is this a persona you adopt online?
> 
> If you're going to insult me because I didn't understand what
> you meant, as opposed to what you said, then I'm done with this
> conversation.
> 
"Boys", please, do not quarrel and do not get personal. It's
a discussion board, and not the most convenient one, and we all are
very different, and it's not easy to decipher neither the
register, nor the goal of different statements, hence be neutral )
Please. You are all great professionals!

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


#85283

FromRichard Heathfield <rjh@cpax.org.uk>
Date2016-03-30 00:52 +0100
Message-ID<ndf4ah$imq$1@dont-email.me>
In reply to#85281
On 30/03/16 00:34, Geoff wrote:
> On Tue, 29 Mar 2016 12:09:13 -0700, Keith Thompson <kst-u@mib.org>
> wrote:
>
<snip>

>> I'd say a "keyboard translation problem" is not a "keyboard problem".
>> When you said it was probably a "keyboard problem", I assumed you meant
>> it was a hardware (or perhaps firmware) issue with the keyboard itself.
>
> No, that's not what I meant, obviously. Are you this pedantic in
> person [...]?

I can't speak for Keith, but /I/ am certainly at least that pedantic in 
person.

> It must be hard to have a simple conversation with you.

It's practically impossible to have a simple conversation with me. It 
is, however, possible to have an /accurate/ conversation with me.

-- 
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within

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


#85285

FromGeoff <geoff@invalid.invalid>
Date2016-03-29 17:27 -0700
Message-ID<3p6mfb1tud36uqd364ov0n9u195uhnmftc@4ax.com>
In reply to#85283
On Wed, 30 Mar 2016 00:52:50 +0100, Richard Heathfield
<rjh@cpax.org.uk> wrote:

>On 30/03/16 00:34, Geoff wrote:
>> On Tue, 29 Mar 2016 12:09:13 -0700, Keith Thompson <kst-u@mib.org>
>> wrote:
>>
><snip>
>
>>> I'd say a "keyboard translation problem" is not a "keyboard problem".
>>> When you said it was probably a "keyboard problem", I assumed you meant
>>> it was a hardware (or perhaps firmware) issue with the keyboard itself.
>>
>> No, that's not what I meant, obviously. Are you this pedantic in
>> person [...]?
>
>I can't speak for Keith, but /I/ am certainly at least that pedantic in 
>person.
>
>> It must be hard to have a simple conversation with you.
>
>It's practically impossible to have a simple conversation with me. It 
>is, however, possible to have an /accurate/ conversation with me.

The conversations I've had with you have often been entertaining as
you take a very much lighter tone than Keith when it comes to semantic
content. You're also a better writer. You and I would probably have a
nice time in a pub somewhere over a pint but I'm not sure I could sit
across the table from Keith without wanting to jump up and strangle
the haughty tone from his vocal cords.

Keith has way to many buttons to push that cause "snappen der
springenwerk mit spitzen sparken" and wide deviations from the topic
at hand.

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


#85296

FromAlla _ <modelling.data@gmail.com>
Date2016-03-30 02:26 -0700
Message-ID<352443b0-d932-498f-a8bf-32b1aa1fd895@googlegroups.com>
In reply to#85281
<snip>
> Since all keyboards on the planet that aren't ASCII keyboards with
> RS-232 interfaces are emitting scan codes that are interpreted by the
> systems they are interfaced with, I'd say "keyboard problem" and
> "keyboard translation problem" are functionally identical for the
> purpose of solving Alla_'s mystery of how she didn't get the
> apostrophe she was expecting. The fact the keyboard translation is
> configurable makes the problem solvable, at least for text that was
> input from the keyboard and not copy-pasted from the web. My point was
> that she need not have copied the text from the web to obtain the
> offending character. I haven't seen a true ASCII keyboard since 1986
> and even then it was on a proprietary control and not a PC.

What is that suppose to mean? ) Of course, I am not capable of 
keeping up with such conversation because I don't yet have any
skills and knowledge required, but shall I deduce from your last 
sentence that all keyboards do not support ASCII characters? Does
it mean that when I type any character using keyboard, the OS has 
to interpret whatever keyboard produces and to turn that into
a genuine ASCII character? It can't be so, can it? Please, note - 
I understand that my assumptions might sound silly, because I do
not have the required knowledge. Sorry. 

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


#85316

Frommark.bluemel@gmail.com
Date2016-03-30 07:09 -0700
Message-ID<4675ee8e-8e4e-41db-80ee-59fc356c18d7@googlegroups.com>
In reply to#85296
On Wednesday, 30 March 2016 10:26:30 UTC+1, Alla _  wrote:

> What is that suppose to mean? ) Of course, I am not capable of 
> keeping up with such conversation because I don't yet have any
> skills and knowledge required, but shall I deduce from your last 
> sentence that all keyboards do not support ASCII characters? Does
> it mean that when I type any character using keyboard, the OS has 
> to interpret whatever keyboard produces and to turn that into
> a genuine ASCII character? It can't be so, can it? Please, note - 
> I understand that my assumptions might sound silly, because I do
> not have the required knowledge. Sorry.

https://en.wikipedia.org/wiki/Computer_keyboard#Technology

Keyboards send a signal to the computer to say which key has been
pressed, software in the computer determines how that key-press is
interpreted.

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


#85320

FromGeoff <geoff@invalid.invalid>
Date2016-03-30 07:33 -0700
Message-ID<15onfbdrb1rrqio4q9bi4pd1mt4f7k729g@4ax.com>
In reply to#85296
On Wed, 30 Mar 2016 02:26:18 -0700 (PDT), Alla _
<modelling.data@gmail.com> wrote:

><snip>
>> Since all keyboards on the planet that aren't ASCII keyboards with
>> RS-232 interfaces are emitting scan codes that are interpreted by the
>> systems they are interfaced with, I'd say "keyboard problem" and
>> "keyboard translation problem" are functionally identical for the
>> purpose of solving Alla_'s mystery of how she didn't get the
>> apostrophe she was expecting. The fact the keyboard translation is
>> configurable makes the problem solvable, at least for text that was
>> input from the keyboard and not copy-pasted from the web. My point was
>> that she need not have copied the text from the web to obtain the
>> offending character. I haven't seen a true ASCII keyboard since 1986
>> and even then it was on a proprietary control and not a PC.
>
>What is that suppose to mean? ) Of course, I am not capable of 
>keeping up with such conversation because I don't yet have any
>skills and knowledge required, but shall I deduce from your last 
>sentence that all keyboards do not support ASCII characters? Does
>it mean that when I type any character using keyboard, the OS has 
>to interpret whatever keyboard produces and to turn that into
>a genuine ASCII character? It can't be so, can it? Please, note - 
>I understand that my assumptions might sound silly, because I do
>not have the required knowledge. Sorry. 

Modern keyboards don't send the actual character codes of the glyphs
they represent on their key faces. They send a hardware dependent "key
code" or "scan code" to the system with every keystroke. The keyboard
drivers within the operating system have knowledge about the scan
codes and interpret the scan codes to choose the system-dependent or
language dependent character codes to be used internally as well as
the glyph they intend to display. This allows much greater flexibility
on a keyboard than would otherwise be possible.

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


#85329

FromJerry Stuckle <jstucklex@attglobal.net>
Date2016-03-30 11:32 -0400
Message-ID<ndgrcg$qvq$1@jstuckle.eternal-september.org>
In reply to#85320
On 3/30/2016 10:33 AM, Geoff wrote:
> On Wed, 30 Mar 2016 02:26:18 -0700 (PDT), Alla _
> <modelling.data@gmail.com> wrote:
> 
>> <snip>
>>> Since all keyboards on the planet that aren't ASCII keyboards with
>>> RS-232 interfaces are emitting scan codes that are interpreted by the
>>> systems they are interfaced with, I'd say "keyboard problem" and
>>> "keyboard translation problem" are functionally identical for the
>>> purpose of solving Alla_'s mystery of how she didn't get the
>>> apostrophe she was expecting. The fact the keyboard translation is
>>> configurable makes the problem solvable, at least for text that was
>>> input from the keyboard and not copy-pasted from the web. My point was
>>> that she need not have copied the text from the web to obtain the
>>> offending character. I haven't seen a true ASCII keyboard since 1986
>>> and even then it was on a proprietary control and not a PC.
>>
>> What is that suppose to mean? ) Of course, I am not capable of 
>> keeping up with such conversation because I don't yet have any
>> skills and knowledge required, but shall I deduce from your last 
>> sentence that all keyboards do not support ASCII characters? Does
>> it mean that when I type any character using keyboard, the OS has 
>> to interpret whatever keyboard produces and to turn that into
>> a genuine ASCII character? It can't be so, can it? Please, note - 
>> I understand that my assumptions might sound silly, because I do
>> not have the required knowledge. Sorry. 
> 
> Modern keyboards don't send the actual character codes of the glyphs
> they represent on their key faces. They send a hardware dependent "key
> code" or "scan code" to the system with every keystroke. The keyboard
> drivers within the operating system have knowledge about the scan
> codes and interpret the scan codes to choose the system-dependent or
> language dependent character codes to be used internally as well as
> the glyph they intend to display. This allows much greater flexibility
> on a keyboard than would otherwise be possible.
> 

This isn't just modern keyboards.  Even back in the 1970's, IBM's 3270
terminals sent key codes to the terminal electronics, as did the
original IBM PC's.

I don't know what the TRS-80 and similar sent, but I highly suspect they
operated similarly.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

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


#86924

Frommrs@kithrup.com (Mike Stump)
Date2016-04-29 08:21 +0000
Message-ID<o6Dz7s.207n@kithrup.com>
In reply to#85329
In article <ndgrcg$qvq$1@jstuckle.eternal-september.org>,
Jerry Stuckle  <jstucklex@attglobal.net> wrote:
>I don't know what the TRS-80 and similar sent, but I highly suspect they
>operated similarly.

Sent?  How quaint.  Imagine you have some address lines, and some data
lines, and you have push buttons switches between them.

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


#86935

FromJerry Stuckle <jstucklex@attglobal.net>
Date2016-04-29 10:35 -0400
Message-ID<nfvr83$fg1$3@jstuckle.eternal-september.org>
In reply to#86924
On 4/29/2016 4:21 AM, Mike Stump wrote:
> In article <ndgrcg$qvq$1@jstuckle.eternal-september.org>,
> Jerry Stuckle  <jstucklex@attglobal.net> wrote:
>> I don't know what the TRS-80 and similar sent, but I highly suspect they
>> operated similarly.
> 
> Sent?  How quaint.  Imagine you have some address lines, and some data
> lines, and you have push buttons switches between them.
> 

Did they send ASCII codes?  Did they send scan codes?

Or did they just send trolling shit like you do?

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

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


#86937

FromKen Brody <kenbrody@spamcop.net>
Date2016-04-29 11:29 -0400
Message-ID<nfvue0$udu$1@dont-email.me>
In reply to#86935
On 4/29/2016 10:35 AM, Jerry Stuckle wrote:
> On 4/29/2016 4:21 AM, Mike Stump wrote:
>> In article <ndgrcg$qvq$1@jstuckle.eternal-september.org>,
>> Jerry Stuckle  <jstucklex@attglobal.net> wrote:
>>> I don't know what the TRS-80 and similar sent, but I highly suspect they
>>> operated similarly.
>>
>> Sent?  How quaint.  Imagine you have some address lines, and some data
>> lines, and you have push buttons switches between them.
>>
>
> Did they send ASCII codes?  Did they send scan codes?
[...]

The TRS-80 model I keyboard didn't "send" anything other than to pull a pin 
to ground.  The BIOS then polled the keyboard's grid to see which key 
position was pushed, and polled the shift key locations, and converted that 
location and shift-status to an ASCII value.

-- 
Kenneth Brody

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


#86940

FromJerry Stuckle <jstucklex@attglobal.net>
Date2016-04-29 12:21 -0400
Message-ID<ng01et$boe$1@jstuckle.eternal-september.org>
In reply to#86937
On 4/29/2016 11:29 AM, Ken Brody wrote:
> On 4/29/2016 10:35 AM, Jerry Stuckle wrote:
>> On 4/29/2016 4:21 AM, Mike Stump wrote:
>>> In article <ndgrcg$qvq$1@jstuckle.eternal-september.org>,
>>> Jerry Stuckle  <jstucklex@attglobal.net> wrote:
>>>> I don't know what the TRS-80 and similar sent, but I highly suspect
>>>> they
>>>> operated similarly.
>>>
>>> Sent?  How quaint.  Imagine you have some address lines, and some data
>>> lines, and you have push buttons switches between them.
>>>
>>
>> Did they send ASCII codes?  Did they send scan codes?
> [...]
> 
> The TRS-80 model I keyboard didn't "send" anything other than to pull a
> pin to ground.  The BIOS then polled the keyboard's grid to see which
> key position was pushed, and polled the shift key locations, and
> converted that location and shift-status to an ASCII value.
> 

Which means they effectively "sent" a row/column pair.

Trolls are sooo literal...

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

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


#87100

FromKen Brody <kenbrody@spamcop.net>
Date2016-05-02 11:55 -0400
Message-ID<ng7t43$bv1$1@dont-email.me>
In reply to#86940
On 4/29/2016 12:21 PM, Jerry Stuckle wrote:
> On 4/29/2016 11:29 AM, Ken Brody wrote:
>> On 4/29/2016 10:35 AM, Jerry Stuckle wrote:
>>> On 4/29/2016 4:21 AM, Mike Stump wrote:
>>>> In article <ndgrcg$qvq$1@jstuckle.eternal-september.org>,
>>>> Jerry Stuckle  <jstucklex@attglobal.net> wrote:
>>>>> I don't know what the TRS-80 and similar sent, but I highly suspect
>>>>> they
>>>>> operated similarly.
>>>>
>>>> Sent?  How quaint.  Imagine you have some address lines, and some data
>>>> lines, and you have push buttons switches between them.
>>>>
>>>
>>> Did they send ASCII codes?  Did they send scan codes?
>> [...]
>>
>> The TRS-80 model I keyboard didn't "send" anything other than to pull a
>> pin to ground.  The BIOS then polled the keyboard's grid to see which
>> key position was pushed, and polled the shift key locations, and
>> converted that location and shift-status to an ASCII value.
>>
>
> Which means they effectively "sent" a row/column pair.

To me, there's a difference between "sent"/"push", and "made available to be 
read"/"pull".

> Trolls are sooo literal...

A woman asks her husband, a programmer, to go shopping.

Wife: “Dear, please, go to the nearby grocery store to buy some bread. 
Also, if they have eggs, buy 6.”

Husband: “O.K., hun.”

Twenty minutes later the husband comes back bringing 6 loaves of bread. His 
wife is flabbergasted.

Wife: “Dear, why on earth did you buy 6 loaves of bread?”

Husband: “They had eggs.”

-- 
Kenneth Brody

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


#87111

FromJerry Stuckle <jstucklex@attglobal.net>
Date2016-05-02 13:13 -0400
Message-ID<ng81lr$via$1@jstuckle.eternal-september.org>
In reply to#87100
On 5/2/2016 11:55 AM, Ken Brody wrote:
> On 4/29/2016 12:21 PM, Jerry Stuckle wrote:
>> On 4/29/2016 11:29 AM, Ken Brody wrote:
>>> On 4/29/2016 10:35 AM, Jerry Stuckle wrote:
>>>> On 4/29/2016 4:21 AM, Mike Stump wrote:
>>>>> In article <ndgrcg$qvq$1@jstuckle.eternal-september.org>,
>>>>> Jerry Stuckle  <jstucklex@attglobal.net> wrote:
>>>>>> I don't know what the TRS-80 and similar sent, but I highly suspect
>>>>>> they
>>>>>> operated similarly.
>>>>>
>>>>> Sent?  How quaint.  Imagine you have some address lines, and some data
>>>>> lines, and you have push buttons switches between them.
>>>>>
>>>>
>>>> Did they send ASCII codes?  Did they send scan codes?
>>> [...]
>>>
>>> The TRS-80 model I keyboard didn't "send" anything other than to pull a
>>> pin to ground.  The BIOS then polled the keyboard's grid to see which
>>> key position was pushed, and polled the shift key locations, and
>>> converted that location and shift-status to an ASCII value.
>>>
>>
>> Which means they effectively "sent" a row/column pair.
> 
> To me, there's a difference between "sent"/"push", and "made available
> to be read"/"pull".
>

All keyboards are just switches, and switches don't "send" anything -
they just provide a row/column or similar contact closure.  Electronics
then convert that into a scan code to be sent to the processor.

The only difference between current keyboards and the TRS-80 is where
that chip is located.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

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


#85325

Fromsupercat@casperkitty.com
Date2016-03-30 08:15 -0700
Message-ID<f8b67131-a275-4b85-89a8-1b45a7072ece@googlegroups.com>
In reply to#85296
On Wednesday, March 30, 2016 at 4:26:30 AM UTC-5, Alla _ wrote:
>                                                              Does
> it mean that when I type any character using keyboard, the OS has 
> to interpret whatever keyboard produces and to turn that into
> a genuine ASCII character? It can't be so, can it?

On some old equipment including the Apple II, the keyboard switches were
wired in a grid in ASCII order; the shift key would reverse the state of
bit 4 (digit 1 is 0x31; an exclamation mark is 0x21.  A period is 0x2E; a
greater-than is 0x3E.  An "N" is 0x4E; shift-N generated a caret which is
0x5E.)  The Apple //e changed the mapping associated with shifted characters,
but did so in hardware in order to ensure compatibility with software that
read the keyboard hardware directly.

Most other modern machines, including the VIC-20 and subsequent Commodore
machines, as well as the IBM PC and Macintosh, have shifted the job of
keyboard mapping from hardware to software.  In the days when the Apple I
was being designed, having a working keyboard greatly facilitated software
design (the alternative would be stuffing bytes into a PROM or EPROM using
lots of switches) so doing keyboard mapping in hardware avoided the need to
create keyboard translation logic without having a keyboard.  Many other
machines were designed be people who had computers to work with, and could
thus use those computers to create the keyboard translation logic for the
new machines.

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


Page 16 of 17 — ← Prev page 1 … 14 15 [16] 17  Next page →

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


csiph-web