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

Testing nodes and lists for hashtable

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

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

  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 9 of 17 — ← Prev page 1 … 7 8 [9] 10 11 … 17 Next page →

#84003

From	Alla _ <modelling.data@gmail.com>
Date	2016-03-15 02:30 -0700
Message-ID	<2d8df2fe-2819-4adb-974a-e96a1b7e23e5@googlegroups.com>
In reply to	#83999

On Tuesday, March 15, 2016 at 1:15:11 PM UTC+4, luser droog wrote:
> On Tuesday, March 15, 2016 at 4:10:13 AM UTC-5, Alla _ wrote:
> > On Tuesday, March 15, 2016 at 1:03:25 PM UTC+4, luser droog wrote:
> > > On Tuesday, March 15, 2016 at 3:53:21 AM UTC-5, Alla _ wrote:
> > > > On Monday, March 14, 2016 at 11:35:35 PM UTC+4, Ben Bacarisse wrote:
> > > > > Alla _ <modelling.data@gmail.com> writes:
> > > > > <snip>
> > > > > > Thank you, but it's confusing ) I am not supposed to have any main() in 
> > > > > > dictionary_test.c, and not supposed to do anything at the 
> > > > > > command line (apart from compiling the speller.c), because I am provided 
> > > > > > with the Makefile. Unfortunately, I can't yet write the makefile myself, 
> > > > > > so I don't truly understand if I shall compile dictionary_test.c, or 
> > > > > > should I compile only speller.c. For the moment neither option works.
> > > > > 
> > > > > Thanks for providing speller_test.c and the Makefile.  That enabled me
> > > > > to test.  As far as I can see it's all fine.  I can build the program
> > > > > just by typing make, so the problem is elsewhere.
> > > > > 
> > > > > What commands does make try to run when you run it?  For example, I get:
> > > > > 
> > > > >   clang -ggdb3 -O0 -Qunused-arguments -std=c11 -Wall -Werror   -c -o speller_test.o speller_test.c
> > > > >   clang -ggdb3 -O0 -Qunused-arguments -std=c11 -Wall -Werror   -c -o dictionary_test.o dictionary_test.c
> > > > >   clang -ggdb3 -O0 -Qunused-arguments -std=c11 -Wall -Werror -o speller_test speller_test.o dictionary_test.o 
> > > > > 
> > > > > This is using the dictionary_test.c and dictionary_test.h files you
> > > > > posted earlier in thus sub-thread.
> > > > > 
> > > > > <snip>
> > > > > -- 
> > > > > Ben.
> > > > 
> > > > Sorry - it seems it was a mistake from my side not to publish all programs,
> > > > including Makefile, at the beginning (
> > > > I don't use make, I use the command Richard has kindly taught me to use some
> > > > time ago:
> > > > gcc -Wall -Werror -Wextra -pedantic -std=c99 program.c -o program
> > > > 
> > > > I do this:
> > > > gcc -Wall -Werror -Wextra -pedantic -std=c99 speller_test.c -o speller_test
> > > > 
> > > > And I get this:
> > > > 
> > > > Undefined symbols for architecture x86_64:
> > > >   "_check", referenced from:
> > > >       _main in ccDbTksE.o
> > > >   "_load", referenced from:
> > > >       _main in ccDbTksE.o
> > > >   "_size", referenced from:
> > > >       _main in ccDbTksE.o
> > > >   "_unload", referenced from:
> > > >       _main in ccDbTksE.o
> > > > ld: symbol(s) not found for architecture x86_64
> > > > collect2: ld returned 1 exit status
> > > > 
> > > > As you have explained to me, I can't compile dictionary_test.c because
> > > > it doesn't have main() function. No where in the spec I could find
> > > > the information on any unusual methods to work with these file, so I 
> > > > was sure that I just need to compile speller_test.c after filling in 
> > > > dictionary_test.c and dictionary_test.h (and updating them by saving 
> > > > changes). The only thing I have altered are names of these files by 
> > > > adding the word 'test', and changing their respective names in each file.
> > > > 
> > > > Do I understand correctly that all struct declarations shall be within
> > > > .h file, and initialization should be within .c file, which should 
> > > > have .h included?
> > > 
> > > If you have a makefile, you should type
> > > 
> > >   make
> > > 
> > > If you ever need to add stuff add it to make
> > > 
> > >   make CFLAGS+=-g LDLIBS+=-lm
> > > 
> > > (But don't add libs like that).
> > 
> > Thank you. I have just tried, but no, it didn't work (I am in correct
> > directory, files are in there, all checked):
> > 
> > make speller_test.c
> > make: Nothing to be done for `speller_test.c'
> > 
> > make dictionary_test.c
> > make: Nothing to be done for `dictionary_test.c'.
> 
> Your makefile has a default target (trust me), so 
> just type
> 
>   make
> 
> with no arguments.

It's truly funny - I spent hours yesterday and today in the morning 
analyzing what could be wrong with all three files and why they
don't compile; and I couldn't find anything )))

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

#83998

From	Richard Heathfield <rjh@cpax.org.uk>
Date	2016-03-15 09:13 +0000
Message-ID	<nc8jhc$24d$1@dont-email.me>
In reply to	#83992

On 15/03/16 08:53, Alla _ wrote:
<snip>

> Sorry - it seems it was a mistake from my side not to publish all programs,
> including Makefile, at the beginning (
> I don't use make, I use the command Richard has kindly taught me to use some
> time ago:
> gcc -Wall -Werror -Wextra -pedantic -std=c99 program.c -o program

That's fine for a standalone program in a single source file. The 
compiler will generally combine the compilation and link phases.

When you have multiple sources, you either have to tell the compiler 
about them all at once: -o programname file1.c file2.c file3.c etc

or you have to separate out the compilation phase from the link phase. 
In a Makefile, you'd do that like this (I wouldn't, because I'd pick 
different CFLAGS, but as you can see that's easy to change):

CC=gcc
CFLAGS=-Wall -Werror -Wextra -pedantic -std=c99
DFLAGS=-g -pg
foo: foo.o bar.o
	$(CC) $(CFLAGS) $(DFLAGS) -o foo foo.o bar.o
foo.o: foo.c
	$(CC) $(CFLAGS) $(DFLAGS) -c -o foo.o foo.c
bar.o: bar.c
	$(CC) $(CFLAGS) $(DFLAGS) -c -o bar.o bar.c

clean:
	rm foo.o
	rm bar.o
	rm foo

install:
	cp foo /usr/local/bin


If, as you say, you don't use make, then (a) why not? and (b) you'd do this:

gcc -Wall -Wextra -Werror -std=c99 -c -o foo.o foo.c
gcc -Wall -Wextra -Werror -std=c99 -c -o bar.o bar.c
gcc -Wall -Wextra -Werror -std=c99 -o foo foo.o bar.o

Some of us just prefer to type:

make

-- 
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]

#84001

From	Alla _ <modelling.data@gmail.com>
Date	2016-03-15 02:28 -0700
Message-ID	<c865d5d0-7cc4-4837-9471-1861387eb9d4@googlegroups.com>
In reply to	#83998

On Tuesday, March 15, 2016 at 1:13:17 PM UTC+4, Richard Heathfield wrote:
> On 15/03/16 08:53, Alla _ wrote:
> <snip>
> 
> > Sorry - it seems it was a mistake from my side not to publish all programs,
> > including Makefile, at the beginning (
> > I don't use make, I use the command Richard has kindly taught me to use some
> > time ago:
> > gcc -Wall -Werror -Wextra -pedantic -std=c99 program.c -o program
> 
> That's fine for a standalone program in a single source file. The 
> compiler will generally combine the compilation and link phases.
> 
> When you have multiple sources, you either have to tell the compiler 
> about them all at once: -o programname file1.c file2.c file3.c etc
> 
> or you have to separate out the compilation phase from the link phase. 
> In a Makefile, you'd do that like this (I wouldn't, because I'd pick 
> different CFLAGS, but as you can see that's easy to change):
> 
> CC=gcc
> CFLAGS=-Wall -Werror -Wextra -pedantic -std=c99
> DFLAGS=-g -pg
> foo: foo.o bar.o
> 	$(CC) $(CFLAGS) $(DFLAGS) -o foo foo.o bar.o
> foo.o: foo.c
> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o foo.o foo.c
> bar.o: bar.c
> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o bar.o bar.c
> 
> clean:
> 	rm foo.o
> 	rm bar.o
> 	rm foo
> 
> install:
> 	cp foo /usr/local/bin
> 
> 
> If, as you say, you don't use make, then (a) why not? and (b) you'd do this:
> 
> gcc -Wall -Wextra -Werror -std=c99 -c -o foo.o foo.c
> gcc -Wall -Wextra -Werror -std=c99 -c -o bar.o bar.c
> gcc -Wall -Wextra -Werror -std=c99 -o foo foo.o bar.o
> 
> Some of us just prefer to type:
> 
> make
> 
Thank you! Yet another thing to learn )

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

#84008

From	Malcolm McLean <malcolm.mclean5@btinternet.com>
Date	2016-03-15 03:15 -0700
Message-ID	<e5ad26b3-b664-4094-a22a-8aa9d638fe5d@googlegroups.com>
In reply to	#83998

On Tuesday, March 15, 2016 at 9:13:17 AM UTC, Richard Heathfield wrote:
> 
> When you have multiple sources, you either have to tell the compiler 
> about them all at once: -o programname file1.c file2.c file3.c etc
> 
gcc *.c

generally does what you want.
You only need to add the -o for your final build, by default it writes to a.out,
which is fine for testing. Sometimes you need to link libraries. I think the -lm
feature (math wasn't linked by default) has finally been fixed.

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

#84014

From	Richard Heathfield <rjh@cpax.org.uk>
Date	2016-03-15 13:26 +0000
Message-ID	<nc92bk$nok$1@dont-email.me>
In reply to	#84008

On 15/03/16 10:15, Malcolm McLean wrote:
> On Tuesday, March 15, 2016 at 9:13:17 AM UTC, Richard Heathfield wrote:
>>
>> When you have multiple sources, you either have to tell the compiler
>> about them all at once: -o programname file1.c file2.c file3.c etc
>>
> gcc *.c
>
> generally does what you want.

Except when it doesn't. For a student (who is likely to have quite a few 
main()-bearing files in one directory), it is spectacularly bad advice.

> You only need to add the -o for your final build, by default it writes to a.out,
> which is fine for testing. Sometimes you need to link libraries. I think the -lm
> feature (math wasn't linked by default) has finally been fixed.

Citation required.

-- 
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]

#84030

From	Keith Thompson <kst-u@mib.org>
Date	2016-03-15 09:18 -0700
Message-ID	<lny49jhfzz.fsf@kst-u.example.com>
In reply to	#84008

Malcolm McLean <malcolm.mclean5@btinternet.com> writes:
> On Tuesday, March 15, 2016 at 9:13:17 AM UTC, Richard Heathfield wrote:
>> 
>> When you have multiple sources, you either have to tell the compiler 
>> about them all at once: -o programname file1.c file2.c file3.c etc
>> 
> gcc *.c
>
> generally does what you want.

(Richard addressed this.)

> You only need to add the -o for your final build, by default it writes
> to a.out, which is fine for testing. Sometimes you need to link
> libraries. I think the -lm feature (math wasn't linked by default) has
> finally been fixed.

No, it hasn't.  *Some* environments link the math library without "-lm",
others do not.

-- 
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]

#84009

From	Alla _ <modelling.data@gmail.com>
Date	2016-03-15 03:19 -0700
Message-ID	<7ae3bff6-e1e3-4089-be8e-e6ebc781c33c@googlegroups.com>
In reply to	#83998

On Tuesday, March 15, 2016 at 1:13:17 PM UTC+4, Richard Heathfield wrote:
> On 15/03/16 08:53, Alla _ wrote:
> <snip>
> 
> > Sorry - it seems it was a mistake from my side not to publish all programs,
> > including Makefile, at the beginning (
> > I don't use make, I use the command Richard has kindly taught me to use some
> > time ago:
> > gcc -Wall -Werror -Wextra -pedantic -std=c99 program.c -o program
> 
> That's fine for a standalone program in a single source file. The 
> compiler will generally combine the compilation and link phases.
> 
> When you have multiple sources, you either have to tell the compiler 
> about them all at once: -o programname file1.c file2.c file3.c etc
> 
> or you have to separate out the compilation phase from the link phase. 
> In a Makefile, you'd do that like this (I wouldn't, because I'd pick 
> different CFLAGS, but as you can see that's easy to change):
> 
> CC=gcc
> CFLAGS=-Wall -Werror -Wextra -pedantic -std=c99
> DFLAGS=-g -pg
> foo: foo.o bar.o
> 	$(CC) $(CFLAGS) $(DFLAGS) -o foo foo.o bar.o
> foo.o: foo.c
> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o foo.o foo.c
> bar.o: bar.c
> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o bar.o bar.c
> 
> clean:
> 	rm foo.o
> 	rm bar.o
> 	rm foo
> 
> install:
> 	cp foo /usr/local/bin
> 
> 
> If, as you say, you don't use make, then (a) why not? and (b) you'd do this:
> 
> gcc -Wall -Wextra -Werror -std=c99 -c -o foo.o foo.c
> gcc -Wall -Wextra -Werror -std=c99 -c -o bar.o bar.c
> gcc -Wall -Wextra -Werror -std=c99 -o foo foo.o bar.o
> 
> Some of us just prefer to type:
> 
> make

I am installing valgrind now, and while running make for it, in 
the horribly cryptic and frantically run set of different characters
that kept appearing on the screen, I could discern a flag -Wmissing.
Will it be helpful if I include it to my gcc set?

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

#84016

From	David Brown <david.brown@hesbynett.no>
Date	2016-03-15 15:21 +0100
Message-ID	<nc95k5$5a2$1@dont-email.me>
In reply to	#84009

On 15/03/16 11:19, Alla _ wrote:
> On Tuesday, March 15, 2016 at 1:13:17 PM UTC+4, Richard Heathfield wrote:
>> On 15/03/16 08:53, Alla _ wrote:
>> <snip>
>>
>>> Sorry - it seems it was a mistake from my side not to publish all programs,
>>> including Makefile, at the beginning (
>>> I don't use make, I use the command Richard has kindly taught me to use some
>>> time ago:
>>> gcc -Wall -Werror -Wextra -pedantic -std=c99 program.c -o program
>>
>> That's fine for a standalone program in a single source file. The 
>> compiler will generally combine the compilation and link phases.
>>
>> When you have multiple sources, you either have to tell the compiler 
>> about them all at once: -o programname file1.c file2.c file3.c etc
>>
>> or you have to separate out the compilation phase from the link phase. 
>> In a Makefile, you'd do that like this (I wouldn't, because I'd pick 
>> different CFLAGS, but as you can see that's easy to change):
>>
>> CC=gcc
>> CFLAGS=-Wall -Werror -Wextra -pedantic -std=c99
>> DFLAGS=-g -pg
>> foo: foo.o bar.o
>> 	$(CC) $(CFLAGS) $(DFLAGS) -o foo foo.o bar.o
>> foo.o: foo.c
>> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o foo.o foo.c
>> bar.o: bar.c
>> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o bar.o bar.c
>>
>> clean:
>> 	rm foo.o
>> 	rm bar.o
>> 	rm foo
>>
>> install:
>> 	cp foo /usr/local/bin
>>
>>
>> If, as you say, you don't use make, then (a) why not? and (b) you'd do this:
>>
>> gcc -Wall -Wextra -Werror -std=c99 -c -o foo.o foo.c
>> gcc -Wall -Wextra -Werror -std=c99 -c -o bar.o bar.c
>> gcc -Wall -Wextra -Werror -std=c99 -o foo foo.o bar.o
>>
>> Some of us just prefer to type:
>>
>> make
> 
> I am installing valgrind now, and while running make for it, in 
> the horribly cryptic and frantically run set of different characters
> that kept appearing on the screen, I could discern a flag -Wmissing.
> Will it be helpful if I include it to my gcc set?
> 

gcc supports a wide range of warning options, many of which are not
enabled by either -Wall or -Wextra (because they cause warnings with a
lot of existing code and don't indicate bugs in the code - merely
possible improvements).  Exactly which warnings you want will depend on
many factors, such as the version of gcc, and some aspects of how you
want to write code.  For example, the warning "-Wdouble-promotion" is
very helpful for the kind of system I work with, but almost totally
useless for work on PC's.  However, "-Wall -Wextra" covers the most
important ones for most uses.

There is no "-Wmissing" flag, but there are a few that start with
"-Wmissing".  The one you probably want is "-Wmissing-prototypes", and I
would definitely recommend using it.

Also note that gcc can do a better job of static error checking when
optimisation is enabled, as that leads to more extensive code analysis.
 So enable "-O1" or "-O2".

<https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html>

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

#84022

From	Alla _ <modelling.data@gmail.com>
Date	2016-03-15 08:39 -0700
Message-ID	<deb74984-6206-4691-9431-c63e821cbbec@googlegroups.com>
In reply to	#84016

On Tuesday, March 15, 2016 at 6:22:05 PM UTC+4, David Brown wrote:
> On 15/03/16 11:19, Alla _ wrote:
> > On Tuesday, March 15, 2016 at 1:13:17 PM UTC+4, Richard Heathfield wrote:
> >> On 15/03/16 08:53, Alla _ wrote:
> >> <snip>
> >>
> >>> Sorry - it seems it was a mistake from my side not to publish all programs,
> >>> including Makefile, at the beginning (
> >>> I don't use make, I use the command Richard has kindly taught me to use some
> >>> time ago:
> >>> gcc -Wall -Werror -Wextra -pedantic -std=c99 program.c -o program
> >>
> >> That's fine for a standalone program in a single source file. The 
> >> compiler will generally combine the compilation and link phases.
> >>
> >> When you have multiple sources, you either have to tell the compiler 
> >> about them all at once: -o programname file1.c file2.c file3.c etc
> >>
> >> or you have to separate out the compilation phase from the link phase. 
> >> In a Makefile, you'd do that like this (I wouldn't, because I'd pick 
> >> different CFLAGS, but as you can see that's easy to change):
> >>
> >> CC=gcc
> >> CFLAGS=-Wall -Werror -Wextra -pedantic -std=c99
> >> DFLAGS=-g -pg
> >> foo: foo.o bar.o
> >> 	$(CC) $(CFLAGS) $(DFLAGS) -o foo foo.o bar.o
> >> foo.o: foo.c
> >> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o foo.o foo.c
> >> bar.o: bar.c
> >> 	$(CC) $(CFLAGS) $(DFLAGS) -c -o bar.o bar.c
> >>
> >> clean:
> >> 	rm foo.o
> >> 	rm bar.o
> >> 	rm foo
> >>
> >> install:
> >> 	cp foo /usr/local/bin
> >>
> >>
> >> If, as you say, you don't use make, then (a) why not? and (b) you'd do this:
> >>
> >> gcc -Wall -Wextra -Werror -std=c99 -c -o foo.o foo.c
> >> gcc -Wall -Wextra -Werror -std=c99 -c -o bar.o bar.c
> >> gcc -Wall -Wextra -Werror -std=c99 -o foo foo.o bar.o
> >>
> >> Some of us just prefer to type:
> >>
> >> make
> > 
> > I am installing valgrind now, and while running make for it, in 
> > the horribly cryptic and frantically run set of different characters
> > that kept appearing on the screen, I could discern a flag -Wmissing.
> > Will it be helpful if I include it to my gcc set?
> > 
> 
> gcc supports a wide range of warning options, many of which are not
> enabled by either -Wall or -Wextra (because they cause warnings with a
> lot of existing code and don't indicate bugs in the code - merely
> possible improvements).  Exactly which warnings you want will depend on
> many factors, such as the version of gcc, and some aspects of how you
> want to write code.  For example, the warning "-Wdouble-promotion" is
> very helpful for the kind of system I work with, but almost totally
> useless for work on PC's.  However, "-Wall -Wextra" covers the most
> important ones for most uses.
> 
> There is no "-Wmissing" flag, but there are a few that start with
> "-Wmissing".  The one you probably want is "-Wmissing-prototypes", and I
> would definitely recommend using it.
> 
> Also note that gcc can do a better job of static error checking when
> optimisation is enabled, as that leads to more extensive code analysis.
>  So enable "-O1" or "-O2".
> 
> 
> 
> <https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html>

Thank you

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

#84033

From	Keith Thompson <kst-u@mib.org>
Date	2016-03-15 09:26 -0700
Message-ID	<lnmvpzhfma.fsf@kst-u.example.com>
In reply to	#84022

Alla _ <modelling.data@gmail.com> writes:
> On Tuesday, March 15, 2016 at 6:22:05 PM UTC+4, David Brown wrote:
[77 lines deleted]
>
> Thank you

Alla, please don't quote an entire long article just to add a 1-line
response.  In this case, you should have trimmed most of what David
wrote, and *all* of what any previous posters wrote.

Just leave enough context in place so that your followup makes sense.
If you're specfically discussing something someone else has written, by
all means quote it.

-- 
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]

#84066

From	Alla _ <modelling.data@gmail.com>
Date	2016-03-16 00:10 -0700
Message-ID	<7656f92e-b661-42cb-9e04-ceebf317f604@googlegroups.com>
In reply to	#84033

On Tuesday, March 15, 2016 at 8:26:33 PM UTC+4, Keith Thompson wrote:
> Alla _ <modelling.data@gmail.com> writes:
> > On Tuesday, March 15, 2016 at 6:22:05 PM UTC+4, David Brown wrote:
> [77 lines deleted]
> >
> > Thank you
> 
> Alla, please don't quote an entire long article just to add a 1-line
> response.  In this case, you should have trimmed most of what David
> wrote, and *all* of what any previous posters wrote.
> 
> Just leave enough context in place so that your followup makes sense.
> If you're specfically discussing something someone else has written, by
> all means quote it.
> 
I am trying ) It seems I often fail to recognize how much to leave and how
much to snip )

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

#84031

From	Keith Thompson <kst-u@mib.org>
Date	2016-03-15 09:19 -0700
Message-ID	<lntwk7hfx7.fsf@kst-u.example.com>
In reply to	#84009

Alla _ <modelling.data@gmail.com> writes:
[...]
> I am installing valgrind now, and while running make for it,
[...]

Depending on your OS, you shouldn't need to "make" valgrind.

On my system, for example, I installed valgrind with:

    sudo apt-get install valgrind

What OS are you using?

-- 
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]

#84065

From	Alla _ <modelling.data@gmail.com>
Date	2016-03-16 00:08 -0700
Message-ID	<0f84eb03-5969-44a8-bed2-b9328281fd90@googlegroups.com>
In reply to	#84031

On Tuesday, March 15, 2016 at 8:19:54 PM UTC+4, Keith Thompson wrote:
> Alla _ <modelling.data@gmail.com> writes:
> [...]
> > I am installing valgrind now, and while running make for it,
> [...]
> 
> Depending on your OS, you shouldn't need to "make" valgrind.
> 
> On my system, for example, I installed valgrind with:
> 
>     sudo apt-get install valgrind
> 
> What OS are you using?
> 
I did struggle for quite some time before installing Valgrind,
because Xcode's CLT don't have autoconf and automake. Then 
after running 'make install' per Valgrind's README, I got 
an error; only 'sudo make install' solved the problem.

I have an already outdated OS Mac OS X 10.7.5 on MacBook Pro 17, 
december 2011.

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

#84074

From	David Brown <david.brown@hesbynett.no>
Date	2016-03-16 08:55 +0100
Message-ID	<ncb3bh$kpv$2@dont-email.me>
In reply to	#84065

On 16/03/16 08:08, Alla _ wrote:
> On Tuesday, March 15, 2016 at 8:19:54 PM UTC+4, Keith Thompson wrote:
>> Alla _ <modelling.data@gmail.com> writes:
>> [...]
>>> I am installing valgrind now, and while running make for it,
>> [...]
>>
>> Depending on your OS, you shouldn't need to "make" valgrind.
>>
>> On my system, for example, I installed valgrind with:
>>
>>     sudo apt-get install valgrind
>>
>> What OS are you using?
>>
> I did struggle for quite some time before installing Valgrind,
> because Xcode's CLT don't have autoconf and automake. Then 
> after running 'make install' per Valgrind's README, I got 
> an error; only 'sudo make install' solved the problem.
> 
> I have an already outdated OS Mac OS X 10.7.5 on MacBook Pro 17, 
> december 2011. 
> 

You might find it easier to use clang or gcc's sanitize options rather
than valgrind.  I have not used either system myself, so I can't help
with details, but the sanitize options are built into the compiler and
toolchain rather than using an external library and tool.

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

#84131

From	Keith Thompson <kst-u@mib.org>
Date	2016-03-16 09:17 -0700
Message-ID	<lna8lygzx4.fsf@kst-u.example.com>
In reply to	#84065

Alla _ <modelling.data@gmail.com> writes:
> On Tuesday, March 15, 2016 at 8:19:54 PM UTC+4, Keith Thompson wrote:
>> Alla _ <modelling.data@gmail.com> writes:
>> [...]
>> > I am installing valgrind now, and while running make for it,
>> [...]
>> 
>> Depending on your OS, you shouldn't need to "make" valgrind.
>> 
>> On my system, for example, I installed valgrind with:
>> 
>>     sudo apt-get install valgrind
>> 
>> What OS are you using?
>> 
> I did struggle for quite some time before installing Valgrind,
> because Xcode's CLT don't have autoconf and automake. Then 
> after running 'make install' per Valgrind's README, I got 
> an error; only 'sudo make install' solved the problem.
>
> I have an already outdated OS Mac OS X 10.7.5 on MacBook Pro 17, 
> december 2011. 

I don't use MacOS myself, but apparently "homebrew" is similar to the
package managers used with most Linux distributions.  Installing
valgrind in particular is discussed here:
http://stackoverflow.com/q/26564125/827263

-- 
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]

#84133

From	Alla _ <modelling.data@gmail.com>
Date	2016-03-16 09:25 -0700
Message-ID	<78605076-0c41-40af-a3ba-c52e83616273@googlegroups.com>
In reply to	#84131

On Wednesday, March 16, 2016 at 8:17:53 PM UTC+4, Keith Thompson wrote:
> Alla _ <modelling.data@gmail.com> writes:
> > On Tuesday, March 15, 2016 at 8:19:54 PM UTC+4, Keith Thompson wrote:
> >> Alla _ <modelling.data@gmail.com> writes:
> >> [...]
> >> > I am installing valgrind now, and while running make for it,
> >> [...]
> >> 
> >> Depending on your OS, you shouldn't need to "make" valgrind.
> >> 
> >> On my system, for example, I installed valgrind with:
> >> 
> >>     sudo apt-get install valgrind
> >> 
> >> What OS are you using?
> >> 
> > I did struggle for quite some time before installing Valgrind,
> > because Xcode's CLT don't have autoconf and automake. Then 
> > after running 'make install' per Valgrind's README, I got 
> > an error; only 'sudo make install' solved the problem.
> >
> > I have an already outdated OS Mac OS X 10.7.5 on MacBook Pro 17, 
> > december 2011. 
> 
> I don't use MacOS myself, but apparently "homebrew" is similar to the
> package managers used with most Linux distributions.  Installing
> valgrind in particular is discussed here:
> http://stackoverflow.com/q/26564125/827263
> 
Thank you! Well, I am already working with Valgrind, I have installed
it yesterday.

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

#83916

From	Malcolm McLean <malcolm.mclean5@btinternet.com>
Date	2016-03-14 13:06 -0700
Message-ID	<d6ea4edd-53fc-4e22-9ecb-831e9310b438@googlegroups.com>
In reply to	#83905

On Monday, March 14, 2016 at 6:41:51 PM UTC, Alla _ wrote:
>
> Unfortunately, I can't yet write the makefile myself, 
> so I don't truly understand if I shall compile dictionary_test.c, or 
> should I compile only speller.c. 
>
No-one can understand makefiles.
They're incomprehensible. Modern systems use CMake, which generates
makefiles from more readable scripts. However the CMake scripts
are themselves becoming hard to read, which in due course of
time can only lead to the invention of DMake.

In fact that could be your first real programming project.

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

#83918

From	Gareth Owen <gwowen@gmail.com>
Date	2016-03-14 20:29 +0000
Message-ID	<87mvq0n6qq.fsf@gmail.com>
In reply to	#83916

Malcolm McLean <malcolm.mclean5@btinternet.com> writes:

> On Monday, March 14, 2016 at 6:41:51 PM UTC, Alla _ wrote:
>>
>> Unfortunately, I can't yet write the makefile myself, 
>> so I don't truly understand if I shall compile dictionary_test.c, or 
>> should I compile only speller.c. 
>>
> No-one can understand makefiles. They're incomprehensible. 
> Modern systems use CMake.

Ah, so we've discovered the subject of this weeks episode of 
"Malcolm Talks Absolute Claptrap About..."

*fetches popcorn*

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

#83923

From	Richard Heathfield <rjh@cpax.org.uk>
Date	2016-03-14 21:03 +0000
Message-ID	<nc78q4$5oe$1@dont-email.me>
In reply to	#83916

On 14/03/16 20:06, Malcolm McLean wrote:
> On Monday, March 14, 2016 at 6:41:51 PM UTC, Alla _ wrote:
>>
>> Unfortunately, I can't yet write the makefile myself,
>> so I don't truly understand if I shall compile dictionary_test.c, or
>> should I compile only speller.c.
>>
> No-one can understand makefiles.

That's not true.

Makefiles can be as simple or complicated as you like. I like to keep 
mine relatively simple, but I know plenty of people who write really 
scary makefiles that they can understand just fine. And there's always 
the documentation, if you're really desperate.

-- 
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]

#83937

From	Keith Thompson <kst-u@mib.org>
Date	2016-03-14 14:57 -0700
Message-ID	<ln7fh4k9io.fsf@kst-u.example.com>
In reply to	#83923

Richard Heathfield <rjh@cpax.org.uk> writes:
> On 14/03/16 20:06, Malcolm McLean wrote:
>> On Monday, March 14, 2016 at 6:41:51 PM UTC, Alla _ wrote:
>>>
>>> Unfortunately, I can't yet write the makefile myself,
>>> so I don't truly understand if I shall compile dictionary_test.c, or
>>> should I compile only speller.c.
>>>
>> No-one can understand makefiles.
>
> That's not true.
>
> Makefiles can be as simple or complicated as you like. I like to keep 
> mine relatively simple, but I know plenty of people who write really 
> scary makefiles that they can understand just fine. And there's always 
> the documentation, if you're really desperate.

And *some* Makefiles are generated automatically by other tools.  Such
Makefiles tend not to be particularly legible.  (Of course that doesn't
justify Malcolm's overly general statement.)

-- 
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]

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

csiph-web

Testing nodes and lists for hashtable

Contents

#84003

#83998

#84001

#84008

#84014

#84030

#84009

#84016

#84022

#84033

#84066

#84031

#84065

#84074

#84131

#84133

#83916

#83918

#83923

#83937