Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #387724 > unrolled thread
| Started by | John Forkosh <john@somewhere.com> |
|---|---|
| First post | 2024-08-23 22:03 +0000 |
| Last post | 2024-08-26 02:33 +0000 |
| Articles | 20 on this page of 414 — 21 participants |
Back to article view | Back to comp.lang.c
Top 10 most common hard skills listed on resumes... John Forkosh <john@somewhere.com> - 2024-08-23 22:03 +0000
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-23 23:06 +0000
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-23 17:02 -0700
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-24 02:26 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-24 14:41 +0200
Re: Top 10 most common hard skills listed on resumes... John Forkosh <forkosh@somewhere.com> - 2024-08-25 12:09 +0000
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-25 17:06 +0300
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-25 10:54 -0400
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-25 18:10 +0300
Re: Top 10 most common hard skills listed on resumes... Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-26 21:36 +0100
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-25 18:47 +0200
Re: Top 10 most common hard skills listed on resumes... "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-08-25 12:58 -0700
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-24 20:11 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-24 19:27 +0100
Re: Top 10 most common hard skills listed on resumes... Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-24 21:12 +0100
Re: Top 10 most common hard skills listed on resumes... Thiago Adams <thiago.adams@gmail.com> - 2024-08-24 18:07 -0300
Re: Top 10 most common hard skills listed on resumes... John Forkosh <forkosh@somewhere.com> - 2024-08-25 12:18 +0000
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-25 10:50 -0400
Re: Top 10 most common hard skills listed on resumes... fir <fir@grunge.pl> - 2024-08-25 16:55 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-25 16:30 +0100
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-25 19:17 +0300
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-25 18:17 +0100
Re: Top 10 most common hard skills listed on resumes... tTh <tth@none.invalid> - 2024-08-25 18:20 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-25 18:26 +0100
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-28 14:21 +0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 13:40 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-28 14:51 +0100
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-29 10:41 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-30 03:18 +0000
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 05:41 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-26 12:05 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-26 13:30 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-26 14:54 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-26 12:32 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 13:07 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-28 00:49 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-28 01:39 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-28 15:57 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-28 19:26 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-29 00:43 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-29 11:35 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-29 13:35 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-29 14:10 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-29 16:13 +0100
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-29 15:40 +0000
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-29 16:45 +0100
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-29 15:58 +0000
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-29 17:06 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-29 18:08 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-29 13:30 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-29 22:29 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-29 15:03 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-29 23:45 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-29 16:32 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-30 00:29 +0100
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-30 02:34 +0000
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-30 06:44 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-30 13:41 -0700
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-31 07:08 +0000
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-31 12:45 -0400
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-31 14:03 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-01 09:45 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-01 10:44 -0700
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-01 18:47 +0000
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-01 15:01 -0400
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-01 13:11 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-01 13:14 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-01 14:17 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-31 19:11 +0100
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-31 19:32 +0000
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-31 16:04 -0400
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-31 15:10 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-01 13:15 +0100
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-01 06:30 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-31 15:31 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-01 00:37 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-31 18:17 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-31 20:01 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-31 20:26 -0700
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-01 03:04 +0000
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-01 13:07 -0700
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 06:39 +0200
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-08 10:12 -0400
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 16:37 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 10:46 +0200
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-09 07:03 -0400
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 13:06 +0200
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-09 08:21 -0400
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-17 05:46 -0700
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-09 17:29 +0000
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-09 14:25 -0400
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-17 05:56 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-17 06:57 -0700
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-17 19:02 +0200
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-17 16:26 -0700
Re: Top 10 most common hard skills listed on resumes... antispam@fricas.org - 2024-09-18 15:28 +0000
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-21 06:00 -0700
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-01 13:12 -0400
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-07 03:13 +0000
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-02 13:03 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-02 13:39 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-02 16:22 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-02 20:43 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-02 15:31 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-02 23:48 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-02 15:52 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-02 23:59 +0100
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-02 19:44 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-02 20:04 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-03 16:08 +0100
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-09 18:00 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-29 21:24 -0700
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-05 15:21 +0000
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-05 16:54 +0000
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-05 17:37 -0400
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-06 10:35 +0100
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-06 14:05 +0300
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-06 07:56 -0700
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-08 11:53 +0300
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-09 12:08 -0700
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-06 13:23 -0400
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-06 19:58 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-06 23:38 +0100
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 05:23 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-05 19:10 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-06 10:19 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-06 12:34 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-07 01:44 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-07 11:53 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-08 00:05 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 12:05 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-08 18:13 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 21:18 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 01:19 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-09 12:31 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-10 04:40 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-10 11:52 +0100
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-10 13:55 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-10 14:30 +0100
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-10 16:53 +0300
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-10 16:18 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-12 21:09 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 22:01 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-08 14:15 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 23:33 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-08 16:20 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-09 00:25 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 00:29 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-09 02:07 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 03:04 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 11:14 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 16:46 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 19:21 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 22:04 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-10 09:04 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-10 13:56 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-10 16:28 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-11 23:59 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-12 13:45 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-12 21:28 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-13 16:24 +0200
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-11 17:12 -0400
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-09 12:08 -0700
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-09 16:56 -0400
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-08 18:10 -0700
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 02:06 +0000
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-08 20:14 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-09 15:58 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 16:21 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-09 17:57 +0100
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 19:37 +0200
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-09 18:46 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 21:04 +0200
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-09 13:16 -0700
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-10 09:19 +0200
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-10 12:18 -0700
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-10 22:10 +0200
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-09 22:33 +0000
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-09 16:24 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-09 18:52 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-09 20:07 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-09 20:46 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-09 21:39 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-14 15:07 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-14 15:51 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-10 04:19 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-10 12:49 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-14 15:13 -0700
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-09 00:09 -0400
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 16:50 +0000
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-09 13:05 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 11:01 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-09 12:28 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-09 12:29 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 05:53 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 05:58 +0200
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-08 17:14 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 17:36 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-10 15:24 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-10 17:28 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-11 01:22 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-11 10:34 +0100
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-11 15:15 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-11 16:51 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-12 00:32 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-12 01:40 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-13 01:01 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-11 17:20 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-15 20:05 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-16 10:58 +0100
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-16 11:30 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-16 14:42 +0100
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-16 14:30 +0000
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-16 17:40 +0300
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-16 12:19 -0400
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-16 19:13 +0200
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-09-17 17:32 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-18 09:44 +0200
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-17 14:08 -0400
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-18 10:05 +0200
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-18 07:27 -0400
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-18 14:15 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-16 19:26 +0200
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-09-17 09:27 -0400
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-12 02:11 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-12 12:27 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-12 12:38 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-12 20:54 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-12 13:51 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-13 14:18 +0100
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 05:44 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-08 11:58 +0300
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 11:27 +0100
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-08 16:34 +0300
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-08 16:39 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 17:44 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-10 00:07 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-09 16:53 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-10 01:20 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-09 17:47 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-09 17:51 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-10 15:15 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-10 17:58 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-11 01:02 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-11 10:52 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-12 00:47 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-12 12:00 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-12 12:39 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-12 12:39 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-13 00:46 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-13 15:02 +0100
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-13 15:12 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-09-13 23:01 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-10 13:05 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-09 09:47 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-09 18:27 +0100
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 16:40 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-08 20:09 +0300
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 11:18 +0100
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-09-08 17:22 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-08 19:01 +0100
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-08 18:39 +0000
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-08 12:19 -0700
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-08 11:50 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-06 04:53 -0700
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-09-06 14:48 +0100
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-09 17:57 -0700
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-29 14:26 -0400
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-29 23:53 +0100
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-30 00:08 +0100
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-30 13:28 -0400
Re: Top 10 most common hard skills listed on resumes... Kaz Kylheku <643-408-1753@kylheku.com> - 2024-08-30 17:36 +0000
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-30 14:37 -0400
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-31 02:18 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-31 02:11 -0700
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-30 06:40 -0700
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-29 23:43 +0300
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-26 12:30 -0700
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 21:41 +0000
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-27 14:18 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-27 12:22 -0700
Re: Top 10 most common hard skills listed on resumes... "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-08-27 12:50 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-28 00:15 +0100
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-27 17:46 -0700
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-01 07:07 +0000
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-27 18:19 -0700
Re: Top 10 most common hard skills listed on resumes... Ben Bacarisse <ben@bsb.me.uk> - 2024-08-28 15:47 +0100
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-28 08:18 -0700
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 21:40 +0000
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 05:40 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-25 17:59 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-25 19:28 +0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-25 20:12 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-25 19:24 +0100
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-26 03:43 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-27 01:33 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-27 00:47 +0100
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 07:09 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-27 09:37 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 10:36 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-27 11:32 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 11:47 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-27 14:51 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 15:14 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-27 20:54 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 07:02 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-28 11:26 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 11:30 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 11:49 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-28 13:43 +0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 13:02 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-28 15:06 +0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 14:40 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-30 09:37 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-28 13:49 +0300
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-28 14:25 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-08 21:34 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 11:34 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 14:36 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-09 17:11 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-09 23:58 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-10 11:20 +0200
Re: Top 10 most common hard skills listed on resumes... Waldek Hebisch <antispam@fricas.org> - 2024-09-13 02:16 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-09-13 16:25 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-09-13 18:05 +0300
Re: Top 10 most common hard skills listed on resumes... scott@slp53.sl.home (Scott Lurndal) - 2024-09-13 17:32 +0000
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-28 13:55 +0300
Re: Top 10 most common hard skills listed on resumes... Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-27 21:13 +0100
Re: Top 10 most common hard skills listed on resumes... scott@slp53.sl.home (Scott Lurndal) - 2024-08-27 21:07 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 07:03 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-28 14:01 +0300
Re: Top 10 most common hard skills listed on resumes... "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-08-27 12:39 -0700
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-28 18:48 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-25 22:00 +0300
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 05:39 +0000
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 17:16 -0700
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 07:10 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 05:17 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 07:23 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 06:47 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 08:58 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 23:44 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 06:59 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-28 05:39 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 08:04 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-30 03:21 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-30 10:43 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-31 00:01 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-31 06:44 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-31 22:30 +0000
Re: Top 10 most common hard skills listed on resumes... scott@slp53.sl.home (Scott Lurndal) - 2024-08-30 14:38 +0000
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-31 00:02 +0000
Re: Top 10 most common hard skills listed on resumes... scott@slp53.sl.home (Scott Lurndal) - 2024-09-01 15:19 +0000
Re: Top 10 most common hard skills listed on resumes... scott@slp53.sl.home (Scott Lurndal) - 2024-09-01 15:22 +0000
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-01 23:48 +0000
Re: Top 10 most common hard skills listed on resumes... Thiago Adams <thiago.adams@gmail.com> - 2024-08-28 08:09 -0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 13:32 +0200
Re: Top 10 most common hard skills listed on resumes... Thiago Adams <thiago.adams@gmail.com> - 2024-08-28 08:47 -0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 14:58 +0200
Re: Top 10 most common hard skills listed on resumes... Thiago Adams <thiago.adams@gmail.com> - 2024-08-28 10:35 -0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 15:45 +0200
Re: Top 10 most common hard skills listed on resumes... Thiago Adams <thiago.adams@gmail.com> - 2024-08-28 10:52 -0300
Re: Top 10 most common hard skills listed on resumes... Thiago Adams <thiago.adams@gmail.com> - 2024-08-28 11:04 -0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 16:18 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-28 16:51 +0100
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 18:58 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 16:55 +0200
Re: Top 10 most common hard skills listed on resumes... Thiago Adams <thiago.adams@gmail.com> - 2024-08-28 14:02 -0300
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 19:13 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-28 19:29 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 19:33 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-27 15:06 +0300
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-27 12:49 +0300
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-27 12:44 +0300
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 23:50 +0000
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-28 06:31 -0700
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-25 18:28 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 05:38 +0000
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-25 18:23 +0200
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-25 17:58 +0200
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-25 18:51 +0200
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-25 18:36 +0200
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-25 20:11 +0300
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-25 17:48 -0700
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-26 10:54 +0300
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 17:55 -0700
Re: Top 10 most common hard skills listed on resumes... Michael S <already5chosen@yahoo.com> - 2024-08-27 12:33 +0300
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-27 19:38 -0700
Re: Top 10 most common hard skills listed on resumes... James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-08-27 09:45 -0400
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-31 03:56 -0700
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-26 15:46 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 04:36 +0000
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-27 09:44 +0200
Re: Top 10 most common hard skills listed on resumes... Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-08-27 12:16 -0700
Re: Top 10 most common hard skills listed on resumes... David Brown <david.brown@hesbynett.no> - 2024-08-27 21:53 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 23:55 +0000
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 23:53 +0000
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-28 01:28 +0100
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-28 05:45 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-28 09:49 +0200
Re: Top 10 most common hard skills listed on resumes... Bart <bc@freeuk.com> - 2024-08-26 15:13 +0100
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 18:16 -0700
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-28 19:57 +0200
Re: Top 10 most common hard skills listed on resumes... scott@slp53.sl.home (Scott Lurndal) - 2024-08-28 18:37 +0000
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-28 23:18 +0200
Re: Top 10 most common hard skills listed on resumes... scott@slp53.sl.home (Scott Lurndal) - 2024-08-28 22:11 +0000
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-28 13:42 -0700
Re: Top 10 most common hard skills listed on resumes... Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-08-28 23:22 +0200
Re: Top 10 most common hard skills listed on resumes... Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-28 22:36 -0700
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-27 04:34 +0000
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 11:11 +0200
Re: Top 10 most common hard skills listed on resumes... Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-27 21:20 +0100
Re: Top 10 most common hard skills listed on resumes... Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-31 10:14 +0200
Re: Top 10 most common hard skills listed on resumes... Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-08-26 02:33 +0000
Page 6 of 21 — ← Prev page 1 … 4 5 [6] 7 8 … 21 Next page →
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2024-09-02 13:39 +0100 |
| Message-ID | <vb4blq$2rf0l$1@dont-email.me> |
| In reply to | #388091 |
On 02/09/2024 13:03, Ben Bacarisse wrote: > Kaz Kylheku <643-408-1753@kylheku.com> writes: > >> On 2024-08-29, Ben Bacarisse <ben@bsb.me.uk> wrote: > ... >>> Do you think (or claim) that what is /required/ on each side of an >>> assignment in C is exactly the same thing? The expression on the LHS is >>> required to be a modifiable lvalue expression. That does not apply to >>> the expression on right hand side. >> >> "modifiable lvalue" is a semantic attribute which depends on type >> and qualification. An array is an lvalue, but not modifiable. >> A const-qualified expression is also not a modififiable lvalue. >> >> Bart is insisting that these attributes are not a matter of syntax. > > Your intervention derailed the discussion into one of syntax. Bart then > simply stopped talking about his original claim. Way back I pointed > out that: > > || What is needed on the two sides is not the same. > > And he replied > > | I would argue that it is exactly the same. > > He did, later, say that is was "exactly the same" except for the > differences but then went back to "I do mean exactly the same". I said this: > I explained that. LHS and RHS can be identical terms for assignment in > pretty much every aspect, but there are extra constraints on the LHS. You then sarcastically suggested: >So you use "exactly the same" to mean "exactly the same except for the differences". I then clarified: >No, I do mean exactly the same, both in terms of syntax and (in my >implementations, which are likely typical) internal representation of >those terms. >...So are no differences when considering only valid programs.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben@bsb.me.uk> |
|---|---|
| Date | 2024-09-02 16:22 +0100 |
| Message-ID | <87jzfum66a.fsf@bsb.me.uk> |
| In reply to | #388092 |
Bart <bc@freeuk.com> writes:
> On 02/09/2024 13:03, Ben Bacarisse wrote:
>> Kaz Kylheku <643-408-1753@kylheku.com> writes:
>>
>>> On 2024-08-29, Ben Bacarisse <ben@bsb.me.uk> wrote:
>> ...
>>>> Do you think (or claim) that what is /required/ on each side of an
>>>> assignment in C is exactly the same thing? The expression on the LHS is
>>>> required to be a modifiable lvalue expression. That does not apply to
>>>> the expression on right hand side.
>>>
>>> "modifiable lvalue" is a semantic attribute which depends on type
>>> and qualification. An array is an lvalue, but not modifiable.
>>> A const-qualified expression is also not a modififiable lvalue.
>>>
>>> Bart is insisting that these attributes are not a matter of syntax.
>> Your intervention derailed the discussion into one of syntax. Bart then
>> simply stopped talking about his original claim. Way back I pointed
>> out that:
>> || What is needed on the two sides is not the same.
>> And he replied
>> | I would argue that it is exactly the same.
>> He did, later, say that is was "exactly the same" except for the
>> differences but then went back to "I do mean exactly the same".
>
>
> I said this:
>
>> I explained that. LHS and RHS can be identical terms for assignment in
>> pretty much every aspect, but there are extra constraints on the LHS.
>
> You then sarcastically suggested:
>
>> So you use "exactly the same" to mean "exactly the same except for the
>> differences".
>
> I then clarified:
>
>> No, I do mean exactly the same, both in terms of syntax and (in my
>> implementations, which are likely typical) internal representation of
>> those terms.
>> ...So are no differences when considering only valid programs.
I wonder what it was you were really objecting to in the original remark
that I made. Since ignoring the differences in what is required on the
LHS and RHS all result in invalid programs your summary is (to a first
approximation) correct, but it does not render mine wrong in any
interesting way.
I note that you have, again, indulged in strategic snipping. The "..."
was "There are no differences other than where the type system says your
code is invalid.". What is it about the type system of C that makes
int main(void) {
extern char *p;
*p = 0;
}
invalid? Because sometimes it is, depending on what p is in some other
translation unit. Are you using your own meaning for "type system"? If
so what is it?
And as for your remarks about typical implementations, does your C
parser /really/ accept an assignment expression on both sides of an =
operator? What does that even look like in the code? I have written
one C parser, contributed to one other and (over the years) examined at
least two more, and none of them do what you seem to be suggesting is
typical.
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2024-09-02 20:43 +0100 |
| Message-ID | <vb54hg$2vf04$1@dont-email.me> |
| In reply to | #388093 |
On 02/09/2024 16:22, Ben Bacarisse wrote:
> Bart <bc@freeuk.com> writes:
>
>> On 02/09/2024 13:03, Ben Bacarisse wrote:
>>> Kaz Kylheku <643-408-1753@kylheku.com> writes:
>>>
>>>> On 2024-08-29, Ben Bacarisse <ben@bsb.me.uk> wrote:
>>> ...
>>>>> Do you think (or claim) that what is /required/ on each side of an
>>>>> assignment in C is exactly the same thing? The expression on the LHS is
>>>>> required to be a modifiable lvalue expression. That does not apply to
>>>>> the expression on right hand side.
>>>>
>>>> "modifiable lvalue" is a semantic attribute which depends on type
>>>> and qualification. An array is an lvalue, but not modifiable.
>>>> A const-qualified expression is also not a modififiable lvalue.
>>>>
>>>> Bart is insisting that these attributes are not a matter of syntax.
>>> Your intervention derailed the discussion into one of syntax. Bart then
>>> simply stopped talking about his original claim. Way back I pointed
>>> out that:
>>> || What is needed on the two sides is not the same.
>>> And he replied
>>> | I would argue that it is exactly the same.
>>> He did, later, say that is was "exactly the same" except for the
>>> differences but then went back to "I do mean exactly the same".
>>
>>
>> I said this:
>>
>>> I explained that. LHS and RHS can be identical terms for assignment in
>>> pretty much every aspect, but there are extra constraints on the LHS.
>>
>> You then sarcastically suggested:
>>
>>> So you use "exactly the same" to mean "exactly the same except for the
>>> differences".
>>
>> I then clarified:
>>
>>> No, I do mean exactly the same, both in terms of syntax and (in my
>>> implementations, which are likely typical) internal representation of
>>> those terms.
>>> ...So are no differences when considering only valid programs.
>
> I wonder what it was you were really objecting to in the original remark
> that I made. Since ignoring the differences in what is required on the
> LHS and RHS all result in invalid programs your summary is (to a first
> approximation) correct, but it does not render mine wrong in any
> interesting way.
>
> I note that you have, again, indulged in strategic snipping. The "..."
> was "There are no differences other than where the type system says your
> code is invalid.". What is it about the type system of C that makes
>
> int main(void) {
> extern char *p;
> *p = 0;
> }
>
> invalid? Because sometimes it is,
This is always valid, when compiling this translation unit. If 'p' is
defined wrongly elsewhere, then that's outside the remit of the compiler.
This is separate issue with C, in that it's not possible to check
consistency across translation units of declarations for shared symbols.
(My language solves that for the modules comprising a program, but it
can still exist between programs rather than between modules.)
But this is venturing away from the question of whether the left and
right sides of an assignment are compatible, or the same, or symmetric.
Obviously, one side is written to and the other is read; the RHS can
also contain a wider range of terms than the left side.
But usually what can be legally on the left side on an assignment, can
also written on the right, and with the same syntax, and the same levels
of indirection.
> depending on what p is in some other
> translation unit. Are you using your own meaning for "type system"? If
> so what is it?
>
> And as for your remarks about typical implementations, does your C
> parser /really/ accept an assignment expression on both sides of an =
> operator? What does that even look like in the code? I have written
> one C parser, contributed to one other and (over the years) examined at
> least two more, and none of them do what you seem to be suggesting is
> typical.
>
Few of the compilers I tried reported a syntax error.
For assignment expressions, my code is something like this:
func readassignexpr =
p := readcondexpr() # p is an ast node
if token is an assign operator then
....
q := readassignexpr()
combine p and q into a new p assignment node
end
return p
end
This is for top-down recursive descent. If I'd called 'readunaryexpr'
instead, it would not recognise lots of expressions when what is being
read isn't the LHS of an assignment.
What did yours look like?
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2024-09-02 15:31 -0700 |
| Message-ID | <878qw93cy6.fsf@nosuchdomain.example.com> |
| In reply to | #388094 |
Bart <bc@freeuk.com> writes:
[...]
> But this is venturing away from the question of whether the left and
> right sides of an assignment are compatible, or the same, or
> symmetric.
>
> Obviously, one side is written to and the other is read; the RHS can
> also contain a wider range of terms than the left side.
>
> But usually what can be legally on the left side on an assignment, can
> also written on the right, and with the same syntax, and the same
> levels of indirection.
Yes, but what can legally be on the right side of an assignment very
often cannot be written on the left. I don't call that "symmetric".
[...]
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2024-09-02 23:48 +0100 |
| Message-ID | <vb5fbj$3116v$1@dont-email.me> |
| In reply to | #388096 |
On 02/09/2024 23:31, Keith Thompson wrote:
> Bart <bc@freeuk.com> writes:
> [...]
>> But this is venturing away from the question of whether the left and
>> right sides of an assignment are compatible, or the same, or
>> symmetric.
>>
>> Obviously, one side is written to and the other is read; the RHS can
>> also contain a wider range of terms than the left side.
>>
>> But usually what can be legally on the left side on an assignment, can
>> also written on the right, and with the same syntax, and the same
>> levels of indirection.
>
> Yes, but what can legally be on the right side of an assignment very
> often cannot be written on the left. I don't call that "symmetric".
The symmetry is about when you /do/ legally have the same thing either
side of '='. That is in contrast to BLISS where the RHS needs an
explicit deref symbol, but the LHS doesn't.
BLISS, AFAIK, can also have unbalanced left and right expressions like:
A = .B + .C + .D
which I believe is the point you're making above. Yet that was described
as 'symmetric'.
Here's a more realistic example, negating a variable A:
A = - A; // C, described as 'asymmetric'
A = - .A; // BLISS, described 'symmetric'
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2024-09-02 15:52 -0700 |
| Message-ID | <874j6x3by1.fsf@nosuchdomain.example.com> |
| In reply to | #388097 |
Bart <bc@freeuk.com> writes:
> On 02/09/2024 23:31, Keith Thompson wrote:
[...]
>> Yes, but what can legally be on the right side of an assignment very
>> often cannot be written on the left. I don't call that "symmetric".
>
> The symmetry is about when you /do/ legally have the same thing either
> side of '='. That is in contrast to BLISS where the RHS needs an
> explicit deref symbol, but the LHS doesn't.
Thank you for clarifying what you mean by "symmetric".
I won't waste any more time debating it.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2024-09-02 23:59 +0100 |
| Message-ID | <vb5g0j$3116v$2@dont-email.me> |
| In reply to | #388098 |
On 02/09/2024 23:52, Keith Thompson wrote: > Bart <bc@freeuk.com> writes: >> On 02/09/2024 23:31, Keith Thompson wrote: > [...] >>> Yes, but what can legally be on the right side of an assignment very >>> often cannot be written on the left. I don't call that "symmetric". >> >> The symmetry is about when you /do/ legally have the same thing either >> side of '='. That is in contrast to BLISS where the RHS needs an >> explicit deref symbol, but the LHS doesn't. > > Thank you for clarifying what you mean by "symmetric". > > I won't waste any more time debating it. > I wonder what /you/ had in mind then for 'symmetry'; that you can legally have the same arbitrary expression on either side of '='? That's only going to work when '=' means 'equality'!
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-09-02 19:44 -0700 |
| Message-ID | <86mskppibw.fsf@linuxsc.com> |
| In reply to | #388094 |
Bart <bc@freeuk.com> writes: [...] > But this is venturing away from the question of whether the left > and right sides of an assignment are compatible, or the same, or > symmetric. > > Obviously, one side is written to and the other is read; the RHS > can also contain a wider range of terms than the left side. > > But usually what can be legally on the left side on an assignment, > can also written on the right, and with the same syntax, and the > same levels of indirection. If you wouldn't mind a suggestion or two, here are some. First, look for accurate ways of expressing what you want to say. Syntactically, the relationship being considered is not a symmetry but a subset. Considering just syntax, what can appear on the left side of an assignment is a subset of what can appear on the right side of an assignment. I think everyone would agree on that point. After getting agreement on the syntax side of the issue, the discussion can then pivot to semantic considerations. Second, try not to always be so defensive. Disagreement doesn't always mean criticism. Asking a question usually isn't meant as an attack but just as an attempt to get clarification or more information. Focus on communication, especially on understanding what the other side is saying. Don't think I'm singling you out on this; lots of people here are guilty of not listening as much or as carefully as they should (myself sometimes included). Let me say explicitly, I don't mean either of these suggestions as criticism. My aim is only to help the conversation.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-09-02 20:04 -0700 |
| Message-ID | <86ikvdphdl.fsf@linuxsc.com> |
| In reply to | #388093 |
Ben Bacarisse <ben@bsb.me.uk> writes: [...] > And as for your remarks about typical implementations, does your C > parser /really/ accept an assignment expression on both sides of > an = operator? What does that even look like in the code? I have > written one C parser, contributed to one other and (over the > years) examined at least two more, and none of them do what you > seem to be suggesting is typical. It wouldn't be surprising to see a parser written so it would accept (syntactically) a superset of the well-formed inputs allowed by the language grammar. Any parses not allowed by the grammar could then be flagged as erroneous in a later semantics pass. One reason to do this is to simplify error recovery in the face of syntax errors. It's much easier to recover from a "correct" parse than from one that looks hopelessly lost. I'm not making any claim that such an approach is typical. On the other hand it does seem to fit with some of the diagnostics given by gcc for inputs that are syntactically ill-formed.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben@bsb.me.uk> |
|---|---|
| Date | 2024-09-03 16:08 +0100 |
| Message-ID | <87a5gon59w.fsf@bsb.me.uk> |
| In reply to | #388101 |
Tim Rentsch <tr.17687@z991.linuxsc.com> writes: > Ben Bacarisse <ben@bsb.me.uk> writes: > > [...] > >> And as for your remarks about typical implementations, does your C >> parser /really/ accept an assignment expression on both sides of >> an = operator? What does that even look like in the code? I have >> written one C parser, contributed to one other and (over the >> years) examined at least two more, and none of them do what you >> seem to be suggesting is typical. > > It wouldn't be surprising to see a parser written so it would > accept (syntactically) a superset of the well-formed inputs > allowed by the language grammar. Any parses not allowed by the > grammar could then be flagged as erroneous in a later semantics > pass. Yes, that is pretty much what I've seen in more than one C parser. I'm going to try to stop replying to Bart, partly because I think he finds my replies annoying (so they are likely provoke unproductive exchanges) but mainly because I am too literal. His reply to me shows that he parses C like most of the compilers I've seen -- accepting a superset of valid LH sides (as you say) but not "exactly the same" the syntax on both sides. Recursive decent parses are inherently lopsided in this respect because that's how they implement associativity. > One reason to do this is to simplify error recovery in the face > of syntax errors. It's much easier to recover from a "correct" > parse than from one that looks hopelessly lost. > > I'm not making any claim that such an approach is typical. On > the other hand it does seem to fit with some of the diagnostics > given by gcc for inputs that are syntactically ill-formed. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-09-09 18:00 -0700 |
| Message-ID | <86o74wiapw.fsf@linuxsc.com> |
| In reply to | #388116 |
Ben Bacarisse <ben@bsb.me.uk> writes: > Tim Rentsch <tr.17687@z991.linuxsc.com> writes: > >> Ben Bacarisse <ben@bsb.me.uk> writes: >> >> [...] >> >>> And as for your remarks about typical implementations, does your C >>> parser /really/ accept an assignment expression on both sides of >>> an = operator? What does that even look like in the code? I have >>> written one C parser, contributed to one other and (over the >>> years) examined at least two more, and none of them do what you >>> seem to be suggesting is typical. >> >> It wouldn't be surprising to see a parser written so it would >> accept (syntactically) a superset of the well-formed inputs >> allowed by the language grammar. Any parses not allowed by the >> grammar could then be flagged as erroneous in a later semantics >> pass. > > Yes, that is pretty much what I've seen in more than one C parser. > [...] Thank you for this posting.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-08-29 21:24 -0700 |
| Message-ID | <86seumwsd7.fsf@linuxsc.com> |
| In reply to | #388004 |
Bart <bc@freeuk.com> writes: > I think that these (with x, y having compatible scalar types): > > x + 1 = y; > (x + 1) = y; // in case above was parsed differently > > are both valid syntax in C. The second line does comply with the ISO C grammar (but does not satisfy the constraints for an assignment expression). The first line does not comply with the ISO C grammar. Which is to say, there is no way to reduce the first line to a single nonterminal under the ISO C grammar rules. Disclaimer: the two previous statements represent my best understanding. I'm fairly confident they are right but I wouldn't advise someone to bet their life on that.
[toc] | [prev] | [next] | [standalone]
| From | Waldek Hebisch <antispam@fricas.org> |
|---|---|
| Date | 2024-09-05 15:21 +0000 |
| Message-ID | <vbci8r$1c9e8$1@paganini.bofh.team> |
| In reply to | #388004 |
Bart <bc@freeuk.com> wrote:
>
> So what exactly is different about the LHS and RHS here:
>
> A = A;
>
> (In BLISS, doing the same thing requires 'A = .A' AIUI; while 'A = A' is
> also valid, there is a hidden mismatch in indirection levels between
> left and right. It is asymmetric while in C it is symmetric, although
> seem to disagree on that latter point.)
You seem to miss the point that assigment operator is fundamentally
assymetic. This is quite visible at low level, where typical
machine has 'store' instruction. Store takes address (memory location)
as left argument, but a _value_ as right argument. Your example
introdices fake symmetry, you ealuate right hand side using
a load ant this may look symmetric with store. But even here
there is asymetry, which is better visible with naive compiler.
You may get code like
compute addres of A
load
compute address of A
store
The last step implement '=', the second 'compute address' corresponds
to A on the left had side. First 'compute address' corresponds to
A on the right hand side. Now you see that beside address computation
there is also load corresponding to A on the right hand side.
So clearly in most languages treatment of sides is assymetric:
extra loads are inserted due to 'lvalue convertion'.
To put in more general context: early success of C was related
to exposing address computations, so that programmers could
do optimization by hand (and consequently non-optimizing compiler
could produce reasonably fast object code). This has a cost:
need for explicit point dereferences not needed in other langiages.
Bliss went slightly further and requires explicit derefernces
to get values of variables. My point is that this is logical
regardless if you like it or not.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2024-09-05 16:54 +0000 |
| Message-ID | <20240905094916.287@kylheku.com> |
| In reply to | #388132 |
On 2024-09-05, Waldek Hebisch <antispam@fricas.org> wrote: > Bart <bc@freeuk.com> wrote: >> >> So what exactly is different about the LHS and RHS here: >> >> A = A; >> >> (In BLISS, doing the same thing requires 'A = .A' AIUI; while 'A = A' is >> also valid, there is a hidden mismatch in indirection levels between >> left and right. It is asymmetric while in C it is symmetric, although >> seem to disagree on that latter point.) > > You seem to miss the point that assigment operator is fundamentally > assymetic. Both sides of an assignment can be complex expressions that designate an object (though the right side need not). Only one detail is different: the prior value of the left hand side object is not fetched, but rather overwritten. All constituents of both expressions have to be evaluated the same way. *(a->b[c++].d(arg)) = e(f)[42] the value of a has to be fetched, c has to be incremented, the function pointer .d called and so on. Note also that a swap operator, which is in the assignment family, is completely symmetric. swap(lvalue1, lvalue2) Both expressions get evaluated the same way. They designate objects, the prior values of which are fetched, and then stored back in reverse order. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Date | 2024-09-05 17:37 -0400 |
| Message-ID | <vbd8b8$g8iv$1@dont-email.me> |
| In reply to | #388133 |
On 9/5/24 12:54, Kaz Kylheku wrote: > On 2024-09-05, Waldek Hebisch <antispam@fricas.org> wrote: ... >> You seem to miss the point that assigment operator is fundamentally >> assymetic. > > Both sides of an assignment can be complex expressions that designate > an object (though the right side need not). So you've correctly identified the very fundamental asymmetry.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2024-09-06 10:35 +0100 |
| Message-ID | <vbeick$p6kd$1@dont-email.me> |
| In reply to | #388135 |
On 05/09/2024 22:37, James Kuyper wrote: > On 9/5/24 12:54, Kaz Kylheku wrote: >> On 2024-09-05, Waldek Hebisch <antispam@fricas.org> wrote: > ... >>> You seem to miss the point that assigment operator is fundamentally >>> assymetic. >> >> Both sides of an assignment can be complex expressions that designate >> an object (though the right side need not). > > So you've correctly identified the very fundamental asymmetry. > Sure, if you want to completely disregard all the cases where the symmetry does exist. That means that for you, there is no interesting difference (using my example of assigning A to itself) in a language where you write 'A = A', and one where you write 'A = .A'. (I'd be interested in how, in the latter language, you'd write the equivalent of 'A = A = A' in C, since the middle term is both on the left of '=', and on the right!)
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2024-09-06 14:05 +0300 |
| Message-ID | <20240906140541.00004c8f@yahoo.com> |
| In reply to | #388136 |
On Fri, 6 Sep 2024 10:35:16 +0100 Bart <bc@freeuk.com> wrote: > On 05/09/2024 22:37, James Kuyper wrote: > > On 9/5/24 12:54, Kaz Kylheku wrote: > >> On 2024-09-05, Waldek Hebisch <antispam@fricas.org> wrote: > > ... > >>> You seem to miss the point that assigment operator is > >>> fundamentally assymetic. > >> > >> Both sides of an assignment can be complex expressions that > >> designate an object (though the right side need not). > > > > So you've correctly identified the very fundamental asymmetry. > > > > Sure, if you want to completely disregard all the cases where the > symmetry does exist. > > That means that for you, there is no interesting difference (using my > example of assigning A to itself) in a language where you write 'A = > A', and one where you write 'A = .A'. > > (I'd be interested in how, in the latter language, you'd write the > equivalent of 'A = A = A' in C, since the middle term is both on the > left of '=', and on the right!) The point is that in BLISS everithing that is legal on the right side of asignment is also legal on the left side. I don't know if the point is generally true. In particular, if BLISS supports floatig point, what is meaning of floating point on the left side?
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-09-06 07:56 -0700 |
| Message-ID | <864j6somo7.fsf@linuxsc.com> |
| In reply to | #388138 |
Michael S <already5chosen@yahoo.com> writes:
> On Fri, 6 Sep 2024 10:35:16 +0100
> Bart <bc@freeuk.com> wrote:
>
>> On 05/09/2024 22:37, James Kuyper wrote:
>>
>>> On 9/5/24 12:54, Kaz Kylheku wrote:
>>>
>>>> On 2024-09-05, Waldek Hebisch <antispam@fricas.org> wrote:
>>>
>>> ...
>>>
>>>>> You seem to miss the point that assigment operator is
>>>>> fundamentally assymetic.
>>>>
>>>> Both sides of an assignment can be complex expressions that
>>>> designate an object (though the right side need not).
>>>
>>> So you've correctly identified the very fundamental asymmetry.
>>
>> Sure, if you want to completely disregard all the cases where the
>> symmetry does exist.
>>
>> That means that for you, there is no interesting difference (using my
>> example of assigning A to itself) in a language where you write 'A =
>> A', and one where you write 'A = .A'.
>>
>> (I'd be interested in how, in the latter language, you'd write the
>> equivalent of 'A = A = A' in C, since the middle term is both on the
>> left of '=', and on the right!)
>
> The point is that in BLISS everithing that is legal on the right side of
> asignment is also legal on the left side.
> I don't know if the point is generally true. In particular, if BLISS
> supports floatig point, what is meaning of floating point on the left
> side?
BLISS is word based and typeless. On a PDP-10, doing a
.pi = 0
where 'pi' holds a 36-bit floating-point value (and 3.14159...
presumably), that floating-point value would be used as an
address and 0 would be stored into it (assuming I remember
BLISS correctly).
So probably not what one wants to do. ;)
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2024-09-08 11:53 +0300 |
| Message-ID | <20240908115334.00006322@yahoo.com> |
| In reply to | #388142 |
On Fri, 06 Sep 2024 07:56:56 -0700 Tim Rentsch <tr.17687@z991.linuxsc.com> wrote: > Michael S <already5chosen@yahoo.com> writes: > > > On Fri, 6 Sep 2024 10:35:16 +0100 > > Bart <bc@freeuk.com> wrote: > > > >> On 05/09/2024 22:37, James Kuyper wrote: > >> > >>> On 9/5/24 12:54, Kaz Kylheku wrote: > >>> > >>>> On 2024-09-05, Waldek Hebisch <antispam@fricas.org> wrote: > >>> > >>> ... > >>> > >>>>> You seem to miss the point that assigment operator is > >>>>> fundamentally assymetic. > >>>> > >>>> Both sides of an assignment can be complex expressions that > >>>> designate an object (though the right side need not). > >>> > >>> So you've correctly identified the very fundamental asymmetry. > >> > >> Sure, if you want to completely disregard all the cases where the > >> symmetry does exist. > >> > >> That means that for you, there is no interesting difference (using > >> my example of assigning A to itself) in a language where you write > >> 'A = A', and one where you write 'A = .A'. > >> > >> (I'd be interested in how, in the latter language, you'd write the > >> equivalent of 'A = A = A' in C, since the middle term is both on > >> the left of '=', and on the right!) > > > > The point is that in BLISS everithing that is legal on the right > > side of asignment is also legal on the left side. > > I don't know if the point is generally true. In particular, if > > BLISS supports floatig point, what is meaning of floating point on > > the left side? > > BLISS is word based and typeless. On a PDP-10, doing a > > .pi = 0 > > where 'pi' holds a 36-bit floating-point value (and 3.14159... > presumably), that floating-point value would be used as an > address and 0 would be stored into it (assuming I remember > BLISS correctly). On PDP-10 reinterpreting [18 LS bits of] floating-point as address is natural, because addresses, integers and FP share the same register file. It seems to me that on S/360 or CDC-6K or PDP-11 or VAX it would be less natural. However, natural or not, BLISS was used widely both on PDP-11 and on VAX, which means that it worked well enough. > > So probably not what one wants to do. ;) Yes, LS bits of FP as address do not sound very useful. On the other hand, using several MS bits of FP, although typically fewer than 18, as address is useful in calculations of many transcendental functions.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-09-09 12:08 -0700 |
| Message-ID | <861q1sk5ly.fsf@linuxsc.com> |
| In reply to | #388163 |
Michael S <already5chosen@yahoo.com> writes:
> On Fri, 06 Sep 2024 07:56:56 -0700
> Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:
>
>> Michael S <already5chosen@yahoo.com> writes:
>>
>>> On Fri, 6 Sep 2024 10:35:16 +0100
>>> Bart <bc@freeuk.com> wrote:
>>>
>>>> On 05/09/2024 22:37, James Kuyper wrote:
>>>>
>>>>> On 9/5/24 12:54, Kaz Kylheku wrote:
>>>>>
>>>>>> On 2024-09-05, Waldek Hebisch <antispam@fricas.org> wrote:
>>>>>
>>>>> ...
>>>>>
>>>>>>> You seem to miss the point that assigment operator is
>>>>>>> fundamentally assymetic.
>>>>>>
>>>>>> Both sides of an assignment can be complex expressions that
>>>>>> designate an object (though the right side need not).
>>>>>
>>>>> So you've correctly identified the very fundamental asymmetry.
>>>>
>>>> Sure, if you want to completely disregard all the cases where the
>>>> symmetry does exist.
>>>>
>>>> That means that for you, there is no interesting difference (using
>>>> my example of assigning A to itself) in a language where you write
>>>> 'A = A', and one where you write 'A = .A'.
>>>>
>>>> (I'd be interested in how, in the latter language, you'd write the
>>>> equivalent of 'A = A = A' in C, since the middle term is both on
>>>> the left of '=', and on the right!)
>>>
>>> The point is that in BLISS everithing that is legal on the right
>>> side of asignment is also legal on the left side.
>>> I don't know if the point is generally true. In particular, if
>>> BLISS supports floatig point, what is meaning of floating point on
>>> the left side?
>>
>> BLISS is word based and typeless. On a PDP-10, doing a
>>
>> .pi = 0
>>
>> where 'pi' holds a 36-bit floating-point value (and 3.14159...
>> presumably), that floating-point value would be used as an
>> address and 0 would be stored into it (assuming I remember
>> BLISS correctly).
>
> On PDP-10 reinterpreting [18 LS bits of] floating-point as address is
> natural, because addresses, integers and FP share the same register
> file.
> It seems to me that on S/360 or CDC-6K or PDP-11 or VAX it would be
> less natural.
I don't think one thing has much of anything to do with the
other. It seems just as unlikely to use a floating-point value,
or a portion of a floating-point value, as an address on a PDP-10
as it does on any of the other systems you mentioned.
> However, natural or not, BLISS was used widely both on PDP-11 and on
> VAX, which means that it worked well enough.
BLISS is, or was, closer to the hardware than C. Also it's
harder to scale in BLISS than in C, because BLISS is typeless.
Writing code in BLISS needs more discipline than writing in C.
(Disclaimer: my experience writing code in BLISS is very
close to epsilon, and is very much dimmed by the long passage
of time.)
>> So probably not what one wants to do. ;)
>
> Yes, LS bits of FP as address do not sound very useful.
> On the other hand, using several MS bits of FP, although typically
> fewer than 18, as address is useful in calculations of many
> transcendental functions.
Probably not use it as an address but rather as an index.
Perhaps something like this (please forgive the bastard
mixing of BLISS and C):
// variable d contains a 64-bit double
needed = .(most_digits + (.d >> 52 & 0x1FFF))
to index a table 'most_digits' by the 11-bit exponent of a
"double" floating-point value.
I don't remember enough BLISS to know how to write indexing,
but this construction should accomplish that.
[toc] | [prev] | [next] | [standalone]
Page 6 of 21 — ← Prev page 1 … 4 5 [6] 7 8 … 21 Next page →
Back to top | Article view | comp.lang.c
csiph-web