Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #383248 > unrolled thread
| Started by | Lynn McGuire <lynnmcguire5@gmail.com> |
|---|---|
| First post | 2024-03-02 17:13 -0600 |
| Last post | 2024-03-12 16:00 -0300 |
| Articles | 20 on this page of 237 — 35 participants |
Back to article view | Back to comp.lang.c
"White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lynn McGuire <lynnmcguire5@gmail.com> - 2024-03-02 17:13 -0600
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-03 00:05 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 13:42 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" John McCue <jmccue@neutron.jmcunx.com> - 2024-03-03 02:10 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-03 02:23 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-03-03 11:11 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-03 03:30 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-03 08:54 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-03 20:11 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 13:49 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-03 22:11 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-03 23:27 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-07 06:46 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-03 08:52 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-03 11:10 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-03 12:01 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-03 16:03 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-03 18:18 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-03 21:23 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 14:01 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-04 09:44 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-04 11:38 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 12:46 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 12:36 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 12:41 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-05 10:01 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-05 12:51 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-06 11:43 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-06 14:18 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-08 13:23 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-09 13:25 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-09 14:16 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-09 14:18 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-03 23:31 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-04 17:05 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-04 18:24 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-05 02:46 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-05 11:23 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-03 20:10 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 14:06 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-03 23:29 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 15:53 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" bart <bc@freeuk.com> - 2024-03-04 01:00 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-04 11:44 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-04 21:07 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-05 00:59 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-05 01:54 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 22:18 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-05 07:06 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 23:10 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-05 11:11 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-05 22:58 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-06 14:02 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" bart <bc@freeuk.com> - 2024-03-06 12:28 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-07 00:00 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-07 11:35 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-07 13:44 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-07 16:36 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-07 17:18 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Paavo Helde <eesnimi@osa.pri.ee> - 2024-03-08 14:41 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-08 15:07 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" bart <bc@freeuk.com> - 2024-03-08 15:15 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-08 17:55 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Ross Finlayson <ross.a.finlayson@gmail.com> - 2024-03-08 10:08 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-29 00:05 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-04-28 17:14 -0700
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-29 01:58 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-04-28 19:01 -0700
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <643-408-1753@kylheku.com> - 2024-04-29 04:28 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-04-29 13:40 -0700
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" paavo512 <paavo@osa.pri.ee> - 2024-04-29 12:45 +0300
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-04-29 13:42 -0700
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" scott@slp53.sl.home (Scott Lurndal) - 2024-04-30 16:46 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-07 16:35 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-08 08:25 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-08 12:57 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-08 15:32 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-08 16:57 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-29 00:02 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" aph@littlepinkcloud.invalid - 2024-04-29 08:55 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-07 01:45 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" aph@littlepinkcloud.invalid - 2024-03-06 14:30 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-07 01:46 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-06 18:00 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-07 02:37 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-06 20:36 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-07 01:44 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-03-14 15:39 -0700
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" gazelle@shell.xmission.com (Kenny McCormack) - 2024-03-04 00:44 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 12:57 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 13:48 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" scott@slp53.sl.home (Scott Lurndal) - 2024-03-03 15:31 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lynn McGuire <lynnmcguire5@gmail.com> - 2024-03-05 00:09 -0600
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-05 07:07 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" scott@slp53.sl.home (Scott Lurndal) - 2024-03-05 14:56 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-03 22:14 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 14:15 -0800
[OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-03-04 16:39 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" scott@slp53.sl.home (Scott Lurndal) - 2024-03-04 17:21 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-07 06:48 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-06 23:01 -0800
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-07 08:15 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-07 08:23 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Richard Harnden <richard.nospam@gmail.invalid> - 2024-03-07 10:20 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-09 06:23 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-09 06:21 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" scott@slp53.sl.home (Scott Lurndal) - 2024-03-07 14:34 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-07 07:58 -0800
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" gazelle@shell.xmission.com (Kenny McCormack) - 2024-03-07 18:09 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-03-07 14:39 -0500
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Ben <ben.usenet@bsb.me.uk> - 2024-03-07 11:23 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-09 06:27 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-08 23:27 -0800
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-09 12:21 +0000
Re: [OT] UTF-8 sig. vallor <vallor@cultnix.org> - 2024-03-09 15:02 +0000
Re: [OT] UTF-8 sig. Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-09 23:11 +0000
Re: [OT] UTF-8 sig. Anton Shepelev <anton.txt@gmail.moc> - 2024-03-21 14:47 +0300
Re: [OT] UTF-8 sig. Ben <ben.usenet@bsb.me.uk> - 2024-03-09 10:40 +0000
Re: [OT] UTF-8 sig. Richard Harnden <richard.nospam@gmail.invalid> - 2024-03-09 11:56 +0000
Re: [OT] UTF-8 sig. Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-03-10 14:03 +0000
Re: [OT] UTF-8 sig. Richard Harnden <richard.nospam@gmail.invalid> - 2024-03-10 19:07 +0000
Re: [OT] UTF-8 sig. Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-09 12:25 +0000
Re: [OT] UTF-8 sig. Richard Harnden <richard.nospam@gmail.invalid> - 2024-03-09 13:11 +0000
Re: [OT] UTF-8 sig. Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-09 23:13 +0000
Re: [OT] UTF-8 sig. Ben Bacarisse <ben.usenet@bsb.me.uk> - 2024-03-10 00:13 +0000
Re: [OT] UTF-8 sig. Michael S <already5chosen@yahoo.com> - 2024-03-10 10:17 +0200
Re: [OT] UTF-8 sig. Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-10 13:35 +0000
Re: [OT] UTF-8 sig. Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-10 17:15 +0000
avoiding strdup() (was: Re: [OT] UTF-8 sig.) vallor <vallor@cultnix.org> - 2024-03-09 13:19 +0000
Re: avoiding strdup() Spiros Bousbouras <spibou@gmail.com> - 2024-03-09 15:25 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-09 16:37 -0800
Re: avoiding strdup() Michael S <already5chosen@yahoo.com> - 2024-03-10 10:11 +0200
Re: avoiding strdup() Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> - 2024-03-10 13:38 +0000
Re: avoiding strdup() Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-10 17:12 +0000
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-10 18:47 +0000
Re: avoiding strdup() Richard Harnden <richard.nospam@gmail.invalid> - 2024-03-10 19:20 +0000
Re: avoiding strdup() Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-11 16:23 +0000
Re: avoiding strdup() Michael S <already5chosen@yahoo.com> - 2024-03-11 18:50 +0200
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-11 17:05 +0000
Re: avoiding strdup() Michael S <already5chosen@yahoo.com> - 2024-03-11 19:35 +0200
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-11 18:06 +0000
Re: avoiding strdup() Michael S <already5chosen@yahoo.com> - 2024-03-11 20:29 +0200
Re: avoiding strdup() Spiros Bousbouras <spibou@gmail.com> - 2024-03-11 19:57 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-11 10:13 -0700
Re: avoiding strdup() Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-11 17:58 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-11 11:28 -0700
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-11 17:58 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-11 11:30 -0700
Re: avoiding strdup() Spiros Bousbouras <spibou@gmail.com> - 2024-03-11 19:45 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-11 13:11 -0700
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-11 17:00 +0000
Re: avoiding strdup() Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-11 17:52 +0000
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-11 18:10 +0000
Re: avoiding strdup() Richard Kettlewell <invalid@invalid.invalid> - 2024-03-11 19:11 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-11 12:34 -0700
Re: avoiding strdup() Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-12 01:12 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-11 18:20 -0700
Re: avoiding strdup() Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-12 15:40 +0000
Re: avoiding strdup() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-12 15:31 -0700
Re: avoiding strdup() Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-13 09:50 +0000
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-12 15:55 +0000
Re: avoiding strdup() Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-12 22:44 +0000
Re: avoiding strdup() scott@slp53.sl.home (Scott Lurndal) - 2024-03-12 23:50 +0000
Re: avoiding strdup() James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-03-13 03:46 -0400
Re: avoiding strdup() David Brown <david.brown@hesbynett.no> - 2024-03-13 16:08 +0100
Re: avoiding strdup() Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-04-29 00:53 +0000
Re: avoiding strdup() i@fuzy.me - 2024-04-29 22:38 +0800
Re: avoiding strdup() steve <sgonedes1977@gmail.com> - 2024-04-30 23:36 -0400
Re: avoiding strdup() Richard Harnden <richard.nospam@gmail.invalid> - 2024-03-10 10:02 +0000
Re: [OT] UTF-8 sig. Was: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" yeti <yeti@tilde.institute> - 2024-03-07 17:52 +0042
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lynn McGuire <lynnmcguire5@gmail.com> - 2024-03-05 00:02 -0600
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David LaRue <huey.dll@tampabay.rr.com> - 2024-03-03 23:59 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-03 16:06 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-04 05:43 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 13:15 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-04 21:26 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 13:28 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 13:29 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-05 02:46 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 19:40 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-05 04:43 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 21:23 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-05 07:07 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-05 13:48 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-06 00:25 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-05 22:01 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-07 23:42 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-07 16:21 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2024-03-05 03:32 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 19:42 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lynn McGuire <lynnmcguire5@gmail.com> - 2024-03-05 00:03 -0600
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-05 07:08 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-05 11:27 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-05 13:01 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-05 21:24 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-05 13:44 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-05 14:11 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-05 14:34 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-06 14:31 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" bart <bc@freeuk.com> - 2024-03-06 13:50 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Michael S <already5chosen@yahoo.com> - 2024-03-06 16:18 +0200
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" bart <bc@freeuk.com> - 2024-03-06 14:38 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" bart <bc@freeuk.com> - 2024-03-06 19:46 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" scott@slp53.sl.home (Scott Lurndal) - 2024-03-06 19:50 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-03-06 14:14 -0500
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Kaz Kylheku <433-929-6894@kylheku.com> - 2024-03-06 19:50 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-06 21:13 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Ross Finlayson <ross.a.finlayson@gmail.com> - 2024-03-08 21:36 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-12 00:07 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Ross Finlayson <ross.a.finlayson@gmail.com> - 2024-03-11 20:05 -0700
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-03-06 19:27 -0500
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-07 03:06 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-03-07 14:28 -0500
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-07 23:44 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-06 07:42 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-06 14:14 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-03-05 13:58 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-05 14:02 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-06 14:34 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-06 14:13 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-07 23:43 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-08 09:01 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-12 00:03 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-04 11:54 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-04 15:41 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" scott@slp53.sl.home (Scott Lurndal) - 2024-03-04 15:28 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-03-04 18:51 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-04 21:11 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-05 11:31 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-06 00:25 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" David Brown <david.brown@hesbynett.no> - 2024-03-06 14:40 +0100
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Derek <derek-nospam@shape-of-code.com> - 2024-03-04 12:18 +0000
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-04 12:52 -0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-03-05 21:51 +0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-03-06 15:43 +0800
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Thiago Adams <thiago.adams@gmail.com> - 2024-03-12 15:54 -0300
Re: "White House to Developers: Using C or C++ Invites Cybersecurity Risks" Thiago Adams <thiago.adams@gmail.com> - 2024-03-12 16:00 -0300
Page 10 of 12 — ← Prev page 1 … 8 9 [10] 11 12 Next page →
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-03-05 04:43 +0000 |
| Message-ID | <us67t9$3jpc3$1@dont-email.me> |
| In reply to | #383358 |
On Tue, 5 Mar 2024 02:46:33 +0000, Malcolm McLean wrote: > The less code you have, the less that can go wrong. This can also mean using the build system to automatically generate some repetitive things, to avoid having to write them manually.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-04 21:23 -0800 |
| Message-ID | <us6a95$3k45j$1@dont-email.me> |
| In reply to | #383363 |
On 3/4/2024 8:43 PM, Lawrence D'Oliveiro wrote: > On Tue, 5 Mar 2024 02:46:33 +0000, Malcolm McLean wrote: > >> The less code you have, the less that can go wrong. > > This can also mean using the build system to automatically generate some > repetitive things, to avoid having to write them manually. Does the build system depend on anything coded in C?
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-03-05 07:07 +0000 |
| Message-ID | <us6gc4$3l59s$3@dont-email.me> |
| In reply to | #383367 |
On Mon, 4 Mar 2024 21:23:49 -0800, Chris M. Thomasson wrote: > On 3/4/2024 8:43 PM, Lawrence D'Oliveiro wrote: > >> On Tue, 5 Mar 2024 02:46:33 +0000, Malcolm McLean wrote: >> >>> The less code you have, the less that can go wrong. >> >> This can also mean using the build system to automatically generate >> some repetitive things, to avoid having to write them manually. > > Does the build system depend on anything coded in C? These days, it might be Rust.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-05 13:48 -0800 |
| Message-ID | <us83v8$3vinv$2@dont-email.me> |
| In reply to | #383374 |
On 3/4/2024 11:07 PM, Lawrence D'Oliveiro wrote: > On Mon, 4 Mar 2024 21:23:49 -0800, Chris M. Thomasson wrote: > >> On 3/4/2024 8:43 PM, Lawrence D'Oliveiro wrote: >> >>> On Tue, 5 Mar 2024 02:46:33 +0000, Malcolm McLean wrote: >>> >>>> The less code you have, the less that can go wrong. >>> >>> This can also mean using the build system to automatically generate >>> some repetitive things, to avoid having to write them manually. >> >> Does the build system depend on anything coded in C? > > These days, it might be Rust. The keyword is might... Right?
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-03-06 00:25 +0000 |
| Message-ID | <us8d6d$1a24$2@dont-email.me> |
| In reply to | #383398 |
On Tue, 5 Mar 2024 13:48:25 -0800, Chris M. Thomasson wrote: > On 3/4/2024 11:07 PM, Lawrence D'Oliveiro wrote: > >> On Mon, 4 Mar 2024 21:23:49 -0800, Chris M. Thomasson wrote: >> >>> Does the build system depend on anything coded in C? >> >> These days, it might be Rust. > > The keyword is might... Right? Might does not make right.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-05 22:01 -0800 |
| Message-ID | <us90qt$86c5$1@dont-email.me> |
| In reply to | #383405 |
On 3/5/2024 4:25 PM, Lawrence D'Oliveiro wrote: > On Tue, 5 Mar 2024 13:48:25 -0800, Chris M. Thomasson wrote: > >> On 3/4/2024 11:07 PM, Lawrence D'Oliveiro wrote: >> >>> On Mon, 4 Mar 2024 21:23:49 -0800, Chris M. Thomasson wrote: >>> >>>> Does the build system depend on anything coded in C? >>> >>> These days, it might be Rust. >> >> The keyword is might... Right? > > Might does not make right. So, what is the right language to use?
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-03-07 23:42 +0000 |
| Message-ID | <usdjch$1a50p$5@dont-email.me> |
| In reply to | #383407 |
On Tue, 5 Mar 2024 22:01:01 -0800, Chris M. Thomasson wrote: > On 3/5/2024 4:25 PM, Lawrence D'Oliveiro wrote: > > So, what is the right language to use? Learn to use more than one.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-07 16:21 -0800 |
| Message-ID | <usdllh$1ambo$2@dont-email.me> |
| In reply to | #383462 |
On 3/7/2024 3:42 PM, Lawrence D'Oliveiro wrote: > On Tue, 5 Mar 2024 22:01:01 -0800, Chris M. Thomasson wrote: > >> On 3/5/2024 4:25 PM, Lawrence D'Oliveiro wrote: >> >> So, what is the right language to use? > > Learn to use more than one. Indeed, I do. Btw, are you an AI? Still not exactly sure why I think that.
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2024-03-05 03:32 +0100 |
| Message-ID | <us607o$3ijur$1@dont-email.me> |
| In reply to | #383330 |
On 04.03.2024 22:15, Chris M. Thomasson wrote: > On 3/3/2024 9:43 PM, Lawrence D'Oliveiro wrote: >> On Sun, 3 Mar 2024 16:06:24 -0800, Chris M. Thomasson wrote: >> >>> I remember a while back when some people would try to tell me that [Ada] >>> solves all issues... >> >> It did make a difference. Did you know the life-support system on the >> International Space Station was written in Ada? Not something you >> would trust C++ code to, let’s face it. > > Would you trust a "safe" language that had some critical libraries that > were written in say, C? You named them as "critical libraries", which (as a project manager) I'd handle as such; be sure about their quality, about certificates, write own test cases if necessary, or demand source code for reviews for own verification. As already said, there's more factors than the language. An external library is also an externality to consider, and to not consider it (per se) as okay. Janis
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-04 19:42 -0800 |
| Message-ID | <us64bu$3j82c$2@dont-email.me> |
| In reply to | #383355 |
On 3/4/2024 6:32 PM, Janis Papanagnou wrote: > On 04.03.2024 22:15, Chris M. Thomasson wrote: >> On 3/3/2024 9:43 PM, Lawrence D'Oliveiro wrote: >>> On Sun, 3 Mar 2024 16:06:24 -0800, Chris M. Thomasson wrote: >>> >>>> I remember a while back when some people would try to tell me that [Ada] >>>> solves all issues... >>> >>> It did make a difference. Did you know the life-support system on the >>> International Space Station was written in Ada? Not something you >>> would trust C++ code to, let’s face it. >> >> Would you trust a "safe" language that had some critical libraries that >> were written in say, C? > > You named them as "critical libraries", which (as a project manager) > I'd handle as such; be sure about their quality, about certificates, > write own test cases if necessary, or demand source code for reviews > for own verification. > > As already said, there's more factors than the language. An external > library is also an externality to consider, and to not consider it > (per se) as okay. Think of a critical library as an essential part of a runtime for a language, perhaps? Say you create a new language that depends on certain things that are coded in C and/or ASM. Fair enough?
[toc] | [prev] | [next] | [standalone]
| From | Lynn McGuire <lynnmcguire5@gmail.com> |
|---|---|
| Date | 2024-03-05 00:03 -0600 |
| Message-ID | <us6ckb$3khma$2@dont-email.me> |
| In reply to | #383294 |
On 3/3/2024 11:43 PM, Lawrence D'Oliveiro wrote: > On Sun, 3 Mar 2024 16:06:24 -0800, Chris M. Thomasson wrote: > >> I remember a while back when some people would try to tell me that [Ada] >> solves all issues... > > It did make a difference. Did you know the life-support system on the > International Space Station was written in Ada? Not something you > would trust C++ code to, let’s face it. > > And here > <https://devclass.com/2022/11/08/spark-as-good-as-rust-for-safer-coding-adacore-cites-nvidia-case-study/> > is a project to make it even safer. Most of the Ada code was written in C or C++ and converted to Ada for delivery. Lynn
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-03-05 07:08 +0000 |
| Message-ID | <us6ge5$3l59s$4@dont-email.me> |
| In reply to | #383369 |
On Tue, 5 Mar 2024 00:03:54 -0600, Lynn McGuire wrote: > On 3/3/2024 11:43 PM, Lawrence D'Oliveiro wrote: > >> Did you know the life-support system on the >> International Space Station was written in Ada? Not something you would >> trust C++ code to, let’s face it. > > Most of the Ada code was written in C or C++ and converted to Ada for > delivery. Was it debugged again? Or was it assumed that the translation was bug- free?
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2024-03-05 11:27 +0100 |
| Message-ID | <us6s1l$3nb7r$2@dont-email.me> |
| In reply to | #383375 |
On 05/03/2024 08:08, Lawrence D'Oliveiro wrote: > On Tue, 5 Mar 2024 00:03:54 -0600, Lynn McGuire wrote: > >> On 3/3/2024 11:43 PM, Lawrence D'Oliveiro wrote: >> >>> Did you know the life-support system on the >>> International Space Station was written in Ada? Not something you would >>> trust C++ code to, let’s face it. >> >> Most of the Ada code was written in C or C++ and converted to Ada for >> delivery. > > Was it debugged again? Or was it assumed that the translation was bug- > free? With Ada, if you can get it to compile, it's ready to ship :-)
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-05 13:01 -0800 |
| Message-ID | <us8180$3v3cu$1@dont-email.me> |
| In reply to | #383381 |
On 3/5/2024 2:27 AM, David Brown wrote: > On 05/03/2024 08:08, Lawrence D'Oliveiro wrote: >> On Tue, 5 Mar 2024 00:03:54 -0600, Lynn McGuire wrote: >> >>> On 3/3/2024 11:43 PM, Lawrence D'Oliveiro wrote: >>> >>>> Did you know the life-support system on the >>>> International Space Station was written in Ada? Not something you would >>>> trust C++ code to, let’s face it. >>> >>> Most of the Ada code was written in C or C++ and converted to Ada for >>> delivery. >> >> Was it debugged again? Or was it assumed that the translation was bug- >> free? > > With Ada, if you can get it to compile, it's ready to ship :-) > > Really? Any logic errors in the program itself?
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <433-929-6894@kylheku.com> |
|---|---|
| Date | 2024-03-05 21:24 +0000 |
| Message-ID | <20240305132240.241@kylheku.com> |
| In reply to | #383394 |
On 2024-03-05, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote: > On 3/5/2024 2:27 AM, David Brown wrote: >> On 05/03/2024 08:08, Lawrence D'Oliveiro wrote: >>> On Tue, 5 Mar 2024 00:03:54 -0600, Lynn McGuire wrote: >>> >>>> On 3/3/2024 11:43 PM, Lawrence D'Oliveiro wrote: >>>> >>>>> Did you know the life-support system on the >>>>> International Space Station was written in Ada? Not something you would >>>>> trust C++ code to, let’s face it. >>>> >>>> Most of the Ada code was written in C or C++ and converted to Ada for >>>> delivery. >>> >>> Was it debugged again? Or was it assumed that the translation was bug- >>> free? >> >> With Ada, if you can get it to compile, it's ready to ship :-) >> > Really? Any logic errors in the program itself? Ariane 5 rocket incident of 1996: The Ada code didn't catch the hardware overflow exception from forcing a 64 bit floating-point value into a 16 bit integer. The situation was not expected by the code which was developed for the Ariane 4, or something like that. -- 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 | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-05 13:44 -0800 |
| Message-ID | <us83nu$3vinv$1@dont-email.me> |
| In reply to | #383395 |
On 3/5/2024 1:24 PM, Kaz Kylheku wrote: > On 2024-03-05, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote: >> On 3/5/2024 2:27 AM, David Brown wrote: >>> On 05/03/2024 08:08, Lawrence D'Oliveiro wrote: >>>> On Tue, 5 Mar 2024 00:03:54 -0600, Lynn McGuire wrote: >>>> >>>>> On 3/3/2024 11:43 PM, Lawrence D'Oliveiro wrote: >>>>> >>>>>> Did you know the life-support system on the >>>>>> International Space Station was written in Ada? Not something you would >>>>>> trust C++ code to, let’s face it. >>>>> >>>>> Most of the Ada code was written in C or C++ and converted to Ada for >>>>> delivery. >>>> >>>> Was it debugged again? Or was it assumed that the translation was bug- >>>> free? >>> >>> With Ada, if you can get it to compile, it's ready to ship :-) >>> >> Really? Any logic errors in the program itself? > > Ariane 5 rocket incident of 1996: The Ada code didn't catch the hardware > overflow exception from forcing a 64 bit floating-point value into a 16 > bit integer. The situation was not expected by the code which was > developed for the Ariane 4, or something like that. > I need to study up on that one; Thanks. Fwiw, the joint strike fighter C++ rules are interesting to me as well. Can a little bugger make one of its air-to-air missiles fire? Now I can hear one of my friends saying, see, I told you that human programmers cannot be trusted... ;^) lol. ADA is bullet proof... Until its not... ;^)
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2024-03-05 14:11 -0800 |
| Message-ID | <87le6wpbvc.fsf@nosuchdomain.example.com> |
| In reply to | #383397 |
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:
[...]
> ADA is bullet proof... Until its not... ;^)
The language is called Ada, not ADA.
Of course no language that can be used for real work can be completely
bulletproof. Ada is designed to be relatively safe (and neither of
these newsgroups is the place to discuss the details.)
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-05 14:34 -0800 |
| Message-ID | <us86kr$7j8$1@dont-email.me> |
| In reply to | #383401 |
On 3/5/2024 2:11 PM, Keith Thompson wrote: > "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes: > [...] >> ADA is bullet proof... Until its not... ;^) > > The language is called Ada, not ADA. I wonder how many people got confused? > Of course no language that can be used for real work can be completely > bulletproof. Ada is designed to be relatively safe (and neither of > these newsgroups is the place to discuss the details.) > That's fine.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2024-03-06 14:31 +0100 |
| Message-ID | <us9r86$eiqh$1@dont-email.me> |
| In reply to | #383402 |
On 05/03/2024 23:34, Chris M. Thomasson wrote: > On 3/5/2024 2:11 PM, Keith Thompson wrote: >> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes: >> [...] >>> ADA is bullet proof... Until its not... ;^) >> >> The language is called Ada, not ADA. > > I wonder how many people got confused? > Apparently you and Malcolm got confused. Others who mentioned the language know it is called "Ada". I not only corrected you, but gave an explanation of it, in the hope that with that clarity, you'd learn.
[toc] | [prev] | [next] | [standalone]
| From | bart <bc@freeuk.com> |
|---|---|
| Date | 2024-03-06 13:50 +0000 |
| Message-ID | <us9sao$erpl$1@dont-email.me> |
| In reply to | #383412 |
On 06/03/2024 13:31, David Brown wrote: > On 05/03/2024 23:34, Chris M. Thomasson wrote: >> On 3/5/2024 2:11 PM, Keith Thompson wrote: >>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes: >>> [...] >>>> ADA is bullet proof... Until its not... ;^) >>> >>> The language is called Ada, not ADA. >> >> I wonder how many people got confused? >> > > Apparently you and Malcolm got confused. > > Others who mentioned the language know it is called "Ada". I not only > corrected you, but gave an explanation of it, in the hope that with that > clarity, you'd learn. > Whoever wrote this short Wikipedia article on it got confused too as it uses both Ada and ADA: https://simple.wikipedia.org/wiki/Ada_(programming_language) (The example program also includes 'Ada' as some package name. Since it is case-insensitive, 'ADA' would also work.) Here's also a paper that uses 'ADA' (I assume it is the same language): https://www.sciencedirect.com/science/article/abs/pii/0166361582900136 Personally I'm not bothered whether anyone uses Ada or ADA. Is 'C' written in all-caps or only capitalised? You can't tell!
[toc] | [prev] | [next] | [standalone]
Page 10 of 12 — ← Prev page 1 … 8 9 [10] 11 12 Next page →
Back to top | Article view | comp.lang.c
csiph-web