Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #390416 > unrolled thread
| Started by | Ar Rakin <rakinar2@onesoftnet.eu.org> |
|---|---|
| First post | 2025-02-25 21:15 +0600 |
| Last post | 2025-03-18 13:59 +0100 |
| Articles | 20 on this page of 295 — 27 participants |
Back to article view | Back to comp.lang.c
Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-25 21:15 +0600
Re: Which code style do you prefer the most? David LaRue <huey.dll@tampabay.rr.com> - 2025-02-25 15:23 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-25 21:34 +0600
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-25 16:17 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-25 22:50 +0600
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-25 22:51 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-25 17:28 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-25 22:52 +0600
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-25 20:35 +0100
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-25 23:02 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 09:41 +0100
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 13:25 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-26 17:43 +0600
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 13:39 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 01:03 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 05:58 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 22:11 +0600
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 15:37 +0100
Re: Which code style do you prefer the most? bks@panix.com (Bradley K. Sherman) - 2025-02-26 14:39 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 17:32 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-26 16:47 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 20:45 +0100
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-09 12:18 -0700
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-09 22:30 +0100
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-10 13:21 -0700
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 18:13 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 20:56 +0100
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 06:57 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-27 16:47 +0100
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-02-28 00:29 +0000
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-02-28 14:44 +0200
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-28 21:14 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-02 13:17 -0800
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-03-03 14:13 +0200
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-03 12:29 +0000
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-03-03 13:33 +0000
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-03 13:57 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-04 03:16 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-03 10:49 -0800
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-03 15:25 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-03 10:34 -0800
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-03 15:23 -0800
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-04 03:17 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-04 06:12 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-04 05:39 +0000
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-04 03:42 -0800
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-04 15:55 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-04 20:49 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-04 22:15 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 05:09 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-05 04:24 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-21 02:41 -0700
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-21 14:06 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-21 14:08 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-22 06:49 -0700
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-22 14:32 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-22 12:45 -0700
Re: 80 char lines and holerith cards [Was:Which code style do you prefer the most?] Jakob Bohm <egenagwemdimtapsar@jbohm.dk> - 2025-04-01 05:46 +0200
Re: 80 char lines and holerith cards [Was:Which code style do you prefer the most?] Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-01 09:46 +0200
Re: 80 char lines and holerith cards [Was:Which code style do you prefer the most?] scott@slp53.sl.home (Scott Lurndal) - 2025-04-01 13:52 +0000
Re: 80 char lines and holerith cards [Was:Which code style do you prefer the most?] Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-04-01 19:11 +0200
Re: 80 char lines and holerith cards [Was:Which code style do you prefer the most?] scott@slp53.sl.home (Scott Lurndal) - 2025-04-01 17:20 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-28 10:00 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-28 12:54 +0100
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-02-28 12:21 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-28 16:44 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-28 21:10 +0000
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-02-28 23:32 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-02-28 23:49 +0000
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-02-28 16:15 -0800
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-03-01 01:02 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-01 17:30 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-01 02:55 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-01 07:07 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 22:04 +0600
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-27 21:10 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 01:04 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 07:06 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 06:17 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 09:38 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 09:15 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-28 08:50 +0100
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-02-28 08:55 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-28 10:21 +0100
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-02-28 10:19 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-28 14:26 +0100
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-02-28 14:22 +0000
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-02-28 16:34 +0200
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-28 21:09 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-28 21:55 +0600
Re: Which code style do you prefer the most? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2025-02-28 10:47 -0800
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-02-28 18:53 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-28 21:08 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-01 17:32 +0100
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-01 21:32 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-01 22:20 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-01 23:43 +0100
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-01 17:24 -0800
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-02 02:42 +0000
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-01 20:46 -0800
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-01 21:29 -0800
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-02 06:46 +0100
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-02 06:48 +0100
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-02 11:31 +0000
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-02 12:17 -0800
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-02 22:13 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-02 12:52 +0100
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-02 13:42 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-02 19:04 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-02 16:32 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-02 17:50 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-02 18:28 +0000
[OT] Pascal identifiers [digression] (was Re: Which code style do you prefer the most?) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-02 23:00 +0100
Re: [OT] Pascal identifiers [digression] (was Re: Which code style do you prefer the most?) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-02 14:49 -0800
Re: [OT] Pascal identifiers [digression] (was Re: Which code style do you prefer the most?) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-03 02:16 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-02 22:07 +0000
Re: Which code style do you prefer the most? cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-01 21:41 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-02 05:52 -0800
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-02 14:21 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-03 17:03 -0800
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-25 22:59 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-25 15:43 +0000
Re: Which code style do you prefer the most? John McCue <jmccue@reddwf.jmcunx.com> - 2025-02-25 18:36 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-26 00:39 +0600
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-02-25 18:51 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-25 19:33 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-02-25 20:40 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-25 21:09 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-25 23:10 +0100
Re: Which code style do you prefer the most? G <g@nowhere.invalid> - 2025-02-26 09:21 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 13:58 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-26 17:53 +0600
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 14:06 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 15:58 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-26 16:26 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 17:47 +0100
Re: Which code style do you prefer the most? John McCue <jmccue@whitedwf.jmcunx.com> - 2025-02-26 19:32 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-26 19:50 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 01:22 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 07:34 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 08:06 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 09:47 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 09:16 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 21:09 +0100
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 07:59 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-26 21:01 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-26 22:13 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-02 00:49 -0800
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 17:32 +0100
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-02-26 13:31 -0800
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 01:10 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 19:05 +0600
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-27 17:23 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 23:17 +0600
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-02 06:00 -0800
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-03-02 16:20 +0200
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-02 15:53 +0100
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-02-25 20:21 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-26 17:51 +0600
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-02-26 17:59 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-26 18:59 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 08:14 +0100
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-02 00:21 -0800
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-02 13:21 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 19:02 +0600
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-28 10:32 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-28 18:54 +0600
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 01:08 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 18:59 +0600
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-02 06:22 -0800
Re: Which code style do you prefer the most? Rosario19 <Ros@invalid.invalid> - 2025-02-25 22:46 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-26 17:54 +0600
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-25 22:47 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-25 22:48 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-26 17:59 +0600
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 14:26 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-26 21:44 +0000
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-02-26 23:17 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 18:56 +0600
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-02-27 14:13 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 21:12 +0600
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-27 17:26 +0100
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 23:17 +0600
Re: Which code style do you prefer the most? candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-28 02:40 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-02-28 04:29 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-28 10:21 +0100
Re: Which code style do you prefer the most? candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-28 17:30 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-02-28 18:39 +0000
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-02-28 15:30 +0200
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-28 18:59 +0600
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-02-27 13:24 -0800
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-28 10:22 +0100
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-02-28 10:24 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-28 13:03 +0100
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-02 09:35 +0000
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-02-28 14:19 +0200
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-01 21:30 -0800
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-02 09:29 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-03 02:17 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-03 02:46 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-03 03:28 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-11 22:11 -0700
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-12 06:52 +0000
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-03-12 11:12 +0200
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-12 09:23 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-13 00:06 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-15 09:26 -0700
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-15 18:23 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-28 21:15 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-02-28 22:15 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-28 22:38 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-02-28 23:21 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-01 02:56 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-01 06:17 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-01 20:25 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-01 21:03 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-01 22:21 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-02-27 14:16 +0000
Re: Which code style do you prefer the most? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2025-02-27 14:21 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 21:13 +0600
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-27 17:33 +0100
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-02-27 17:27 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-02-27 21:14 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 23:24 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-28 22:12 +0600
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-28 21:25 +0000
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-02-27 14:18 +0000
Re: Which code style do you prefer the most? Ar Rakin <rakinar2@onesoftnet.eu.org> - 2025-02-27 21:11 +0600
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-01 21:56 -0800
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-27 08:45 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-27 08:08 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-02 04:01 -0800
Re: Which code style do you prefer the most? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2025-03-04 17:56 +0300
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-04 15:18 +0000
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-04 16:01 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-04 18:14 +0000
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-03-04 21:49 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-04 22:17 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-04 22:26 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-04 22:40 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-04 23:45 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 05:46 +0100
Re: Which code style do you prefer the most? vallor <vallor@cultnix.org> - 2025-03-05 07:02 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 09:35 +0100
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-05 08:39 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 09:58 +0100
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-05 19:12 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 21:53 +0100
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-06 01:22 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-06 02:34 +0000
Re: Which code style do you prefer the most? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2025-03-05 15:22 +0300
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-05 14:44 +0100
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-05 14:20 +0000
Re: Which code style do you prefer the most? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2025-03-05 18:30 +0300
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-05 16:40 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 18:09 +0100
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-03-05 17:32 +0000
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-05 17:51 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 19:50 +0100
Re: Which code style do you prefer the most? richard@cogsci.ed.ac.uk (Richard Tobin) - 2025-03-05 19:09 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-05 19:18 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-05 20:07 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 21:46 +0100
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-05 14:58 -0800
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-06 10:35 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-06 10:29 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-06 14:49 +0000
Re: Which code style do you prefer the most? Richard Harnden <richard.nospam@gmail.invalid> - 2025-03-06 17:52 +0000
Re: Which code style do you prefer the most? Richard Heathfield <rjh@cpax.org.uk> - 2025-03-06 18:05 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-06 21:14 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-07 15:37 +0100
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-07 12:17 -0800
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-08 16:47 +0100
Re: Which code style do you prefer the most? candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-12 22:20 +0000
Re: Which code style do you prefer the most? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-03-12 15:23 -0700
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-13 00:12 +0000
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-13 09:30 +0100
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-13 09:44 +0000
Re: Which code style do you prefer the most? Michael S <already5chosen@yahoo.com> - 2025-03-13 16:19 +0200
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-13 16:20 +0100
Re: Which code style do you prefer the most? David Brown <david.brown@hesbynett.no> - 2025-03-06 20:36 +0100
Re: Which code style do you prefer the most? G <g@nowhere.invalid> - 2025-03-07 09:28 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-07 21:16 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-06 20:49 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-05 22:02 +0000
Re: Which code style do you prefer the most? bart <bc@freeuk.com> - 2025-03-05 23:46 +0000
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-06 00:46 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-06 10:53 +0100
Re: Which code style do you prefer the most? scott@slp53.sl.home (Scott Lurndal) - 2025-03-06 14:48 +0000
Re: Which code style do you prefer the most? Kaz Kylheku <643-408-1753@kylheku.com> - 2025-03-06 21:18 +0000
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-07 08:10 +0100
Re: Which code style do you prefer the most? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-04 23:36 +0000
Re: Which code style do you prefer the most? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-03-09 11:41 -0700
Re: Which code style do you prefer the most? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-03-05 05:21 +0100
Re: Which code style do you prefer the most? Bonita Montero <Bonita.Montero@gmail.com> - 2025-03-18 13:59 +0100
Page 8 of 15 — ← Prev page 1 … 6 7 [8] 9 10 … 15 Next page →
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-27 08:06 +0000 |
| Message-ID | <vpp6f0$31cet$3@dont-email.me> |
| In reply to | #390495 |
On Thu, 27 Feb 2025 07:34:24 +0100, Janis Papanagnou wrote: > From the "commercial world" I have only Cobol, PL/1, Fortran in mind; I > seem to recall none of them working with begin/end parenthesis or > braces. PL/I had DO ... END and BEGIN ... END, depending on whether you wanted a new block scope or not. Fortran I have mentioned elsewhere.
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-02-27 09:47 +0100 |
| Message-ID | <vpp8rd$31rcu$1@dont-email.me> |
| In reply to | #390500 |
On 27.02.2025 09:06, Lawrence D'Oliveiro wrote: > On Thu, 27 Feb 2025 07:34:24 +0100, Janis Papanagnou wrote: > >> From the "commercial world" I have only Cobol, PL/1, Fortran in mind; I >> seem to recall none of them working with begin/end parenthesis or >> braces. > > PL/I had DO ... END and BEGIN ... END, depending on whether you wanted a > new block scope or not. Fortran I have mentioned elsewhere. I may have used misleading wording; I was replying to John's "languages [...] that used braces". So "working with begin/end parenthesis or braces." should be read as "working with begin/end-parenthesis or -braces", or better as "working with parenthesis or braces with begin/end meaning". Sorry for the confusion. Janis
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-27 09:16 +0000 |
| Message-ID | <vppai7$323a3$1@dont-email.me> |
| In reply to | #390503 |
On Thu, 27 Feb 2025 09:47:40 +0100, Janis Papanagnou wrote: > On 27.02.2025 09:06, Lawrence D'Oliveiro wrote: > >> On Thu, 27 Feb 2025 07:34:24 +0100, Janis Papanagnou wrote: >> >>> From the "commercial world" I have only Cobol, PL/1, Fortran in mind; >>> I seem to recall none of them working with begin/end parenthesis or >>> braces. >> >> PL/I had DO ... END and BEGIN ... END, depending on whether you wanted >> a new block scope or not. Fortran I have mentioned elsewhere. > > I may have used misleading wording; I was replying to John's "languages > [...] that used braces". Yeah, I know you meant. I don’t really see any important difference (other than terseness) between different kinds of statement bracketing symbols, whether they be (semi)readable syntax words or special sequences of nonalphabetic characters.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-02-26 21:09 +0100 |
| Message-ID | <vpnsd7$2n8td$1@dont-email.me> |
| In reply to | #390470 |
On 26/02/2025 17:47, Janis Papanagnou wrote: > On 26.02.2025 17:26, Scott Lurndal wrote: >> David Brown <david.brown@hesbynett.no> writes: >> >>> It is also an argument against writing code like : >>> >>> if (flag) >>> doThis(); >>> >>> Not only is adding a "doThat();" error-prone in itself (forgetting to >>> add braces is a real risk), but it means adding (or later removing) a >>> single line is now a three-line change. >> >> Agreed. > > I consider that argument of about the same quality as the suggestion > to write > > if (42 == a) instead of if (a == 42) > > just to prevent the error of writing if (a = 42) in "C" (and > similar languages). > > I don't think this is convincing. The difference is that the mistake : if (flag) doThis(); doThat(); really does happen in actual released code, and has caused significant problems. And if you have mixed tabs and spaces in the code, it is entirely possible that with different editors with different tab sizes, the code appears differently - adding to the confusion and the likelihood of errors going unnoticed. Mistakes like "if (a = 42)" rarely make it past initial testing, and most compilers have warned about such errors for decades. (Some compiles - including modern gcc and clang - can spot the confusing indentation. But that has not been the case for so long.)
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-02-27 07:59 +0100 |
| Message-ID | <vpp2hf$30r3h$1@dont-email.me> |
| In reply to | #390481 |
On 26.02.2025 21:09, David Brown wrote:
> On 26/02/2025 17:47, Janis Papanagnou wrote:
>> On 26.02.2025 17:26, Scott Lurndal wrote:
>>> David Brown <david.brown@hesbynett.no> writes:
>>>
>>>> It is also an argument against writing code like :
>>>>
>>>> if (flag)
>>>> doThis();
>>>>
>>>> Not only is adding a "doThat();" error-prone in itself (forgetting to
>>>> add braces is a real risk), but it means adding (or later removing) a
>>>> single line is now a three-line change.
>>>
>>> Agreed.
>>
>> I consider that argument of about the same quality as the suggestion
>> to write
>>
>> if (42 == a) instead of if (a == 42)
>>
>> just to prevent the error of writing if (a = 42) in "C" (and
>> similar languages).
>>
>> I don't think this is convincing.
>
> The difference is that the mistake :
>
> if (flag)
> doThis();
> doThat();
>
> really does happen in actual released code, and has caused significant
> problems.
Yes, only that there is no _*principle* difference_ compared to
if (a = 42)
that "really does happen in actual released code, and has caused
significant problems".
> And if you have mixed tabs and spaces in the code, it is
> entirely possible that with different editors with different tab sizes,
> the code appears differently - adding to the confusion and the
> likelihood of errors going unnoticed.
>
> Mistakes like "if (a = 42)" rarely make it past initial testing, and
> most compilers have warned about such errors for decades. (Some
> compiles - including modern gcc and clang - can spot the confusing
> indentation. But that has not been the case for so long.)
I cannot confirm what you say. Both sorts of errors *can* be caught
during project review or test phases of "actually released code".
In the contexts I worked in both types of errors were actually made,
the assignment-error actually even more often. And a whole function
('doThat();') that is wrongly executed unconditionally gets quickly
detected, in my experience. - YMMV.
What I wanted to say is that language syntaxes have pitfalls where
you need knowledge and experience. Often _wrong ways_ are chosen to
counter the language (mis-)design. At some point, when the compiler
vendors hear about such problems, they support detection of such
issues (usually with some compile switch activated). But the problem
of 'if(a=42)' is not solved by always *thinking* to instead write it
as 'if(42=a)' (erm, 'if(42==a)'). Since if you anyway _think_ about
that then you can then as well just write 'if(a==42)'. And of course
it also doesn't address the general case in the first place. Whether
'if(a=b)' is correct isn't fixed by getting used to write 'if(b=a)'.
It's similar to with the control constructs without spurious braces.
Teach your programmers to use (in "C"-like languages) '==' if they
intend to compare things, teach them to add braces when collecting
more than one statement in some control construct or block.
Beyond that it's IMO just opinion and preferences.
Janis
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-02-26 21:01 +0100 |
| Message-ID | <vpnrug$2mq8h$3@dont-email.me> |
| In reply to | #390466 |
On 26/02/2025 17:26, Scott Lurndal wrote: > David Brown <david.brown@hesbynett.no> writes: >> On 26/02/2025 14:06, Janis Papanagnou wrote: >>> On 26.02.2025 12:53, Ar Rakin wrote: >>>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes: >>>>> > >> This is a good reason for preferring // comments to /* */ comments - >> every line that is commented-out is clearly a commented-out line, and >> doesn't need the context. > > I disagree with this. A line of code should never be commented out; > simply removed if not necessary. The next maintainer of the code > five years down the line will have no idea why the commented out line > of code was kept in the codebase. That's not unreasonable in the ideal situation. A lot of coding is not ideal, and things get commented out temporarily - and not tied up as it should be. I agree with the principle that code should be either present and useful, or not present at all - but practice does not always match principle. But consider a case of some documentation: // This function should be called like this: // // int x = foo(1, 2, 3); // // The returned value x will be the foo of the arguments. There /are/ legitimate reasons for comments that at least appear to be code. > > Conditional compilation (#if) with appropriate inline documentation > describing _why_ it was left in the codebase, would be acceptable; > but generally I don't like conditional compilation for readability > and maintainability reasons. > > I've seen codebases where every fourth line was a #if, and the > code was almost impossible to follow or maintain. > I agree - conditional compilation can be useful, but it is best kept to a minimum or tidied away in one place. >> It is also an argument against writing code like : >> >> if (flag) >> doThis(); >> >> Not only is adding a "doThat();" error-prone in itself (forgetting to >> add braces is a real risk), but it means adding (or later removing) a >> single line is now a three-line change. > > Agreed. And for those of us old enough, the lack of braces means > that the 'if (flag)' line may need to be repunched to add the opening > brace later...
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2025-02-26 22:13 +0000 |
| Message-ID | <omMvP.110238$4lMb.42397@fx44.iad> |
| In reply to | #390479 |
David Brown <david.brown@hesbynett.no> writes:
>On 26/02/2025 17:26, Scott Lurndal wrote:
>> David Brown <david.brown@hesbynett.no> writes:
>>> On 26/02/2025 14:06, Janis Papanagnou wrote:
>>>> On 26.02.2025 12:53, Ar Rakin wrote:
>>>>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
>>>>>>
>>
>>> This is a good reason for preferring // comments to /* */ comments -
>>> every line that is commented-out is clearly a commented-out line, and
>>> doesn't need the context.
>>
>> I disagree with this. A line of code should never be commented out;
>> simply removed if not necessary. The next maintainer of the code
>> five years down the line will have no idea why the commented out line
>> of code was kept in the codebase.
>
>That's not unreasonable in the ideal situation. A lot of coding is not
>ideal, and things get commented out temporarily - and not tied up as it
>should be. I agree with the principle that code should be either
>present and useful, or not present at all - but practice does not always
>match principle.
>
>But consider a case of some documentation:
>
>// This function should be called like this:
>//
>// int x = foo(1, 2, 3);
>//
>// The returned value x will be the foo of the arguments.
>
>
>There /are/ legitimate reasons for comments that at least appear to be code.
Perhaps. I'd argue that something like doxygen is more useful:
/**
* Create a processor object.
*
* Set the initial power-on processor state.
*
* @param sp The system object to be passed to c_processor::processor_thread
* @param logger The logger object to be used by this processor
* @param procnum The processor number
* @param bootstrap True if this is the bootstrap processor. The bootstrap
* processor starts execution at BASE.+94.6.UN, while
* non-bootstrap processors start with an interrupt
* procedure.
*/
c_processor::c_processor(c_system *sp, c_logger *logger,
processor_number_t procnum, bool bootstrap)
: c_thread("Processor #NN", logger),
p_imask(this),
p_interrupts(this),
p_active_env(this),
p_mop(this),
p_toggles(this)
{
The doxygen-style comments can be post processsed into
html documentation (or customer documentation in PDF). Useful, that.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2025-03-02 00:49 -0800 |
| Message-ID | <86tt8bx1ek.fsf@linuxsc.com> |
| In reply to | #390466 |
scott@slp53.sl.home (Scott Lurndal) writes: > [using // instead of /* ... */ to comment out lines of code] > > I disagree with this. A line of code should never be commented > out; simply removed if not necessary. During development it can be useful to comment out one or more lines of code, but leave the commented lines in the source file. The point is we don't always know what is necessary and what isn't. What matters when code is finished and ready to be shipped is not the same as what matters when code is in the process of being developed. That distinction also applies to other things besides whether to remove certain lines of code or just comment them out.
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-02-26 17:32 +0100 |
| Message-ID | <vpnfm8$2kump$1@dont-email.me> |
| In reply to | #390465 |
On 26.02.2025 15:58, David Brown wrote:
> On 26/02/2025 14:06, Janis Papanagnou wrote:
>> On 26.02.2025 12:53, Ar Rakin wrote:
>>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
>>>>
>>>> Re "goofy style"; I've seen someone preferring
>>>>
>>>> while (q(a,b))
>>>> {
>>>> a=b;
>>>> f(x);
>>>> if (c>d)
>>>> {
>>>> g(y);
>>>> }
>>>> }
>>>>
>>>> To each his own.
>>>
>>> That looks like a nightmare for the code reviewers.
>
> I find that style grating. But I don't think I'd call it a "nightmare"
> - I've seen far worse.
>
> But from all my education and training in coding, mathematics,
> documentation, writing, and typography, I am a solid believer in one
> rule - the most important feature of any written information is the
> spacing. If I were tasked with making that code clear, the first step
> would be to add a few spaces - "a = b;", "if (c > d)" - that would be
> higher priority than using a more "normal" brace style such as the "One
> True Brace Style".
Just note that this was _ad hoc_ code only to illustrate the braces
placement, not the spacing. (The guy I was talking about writes in
fact readable(!) code, i.e. with spacing, sensible naming, comments,
etc. etc.) The only really strange thing in his code are the braces
placement that I've not seen anywhere before. (And I've seen a lot
code, most of it complying more or less to prevalent conventions.)
>
>>
>> I cannot tell where that comes from; the person who uses it is an
>> experienced Perl programmer - may that be some convention in that
>> specific language context? (I can't tell.)
>>
>> WRT code reviews; in the past I had horrendous code that I needed
>> to reformat using a code-beautifier before I could review it. But
>> those were extreme (and only rare) cases. (And above yet isn't as
>> bad as those other artworks I had.)
>>
>
> I think it is more common in such cases to reject the code from the
> review, and insist that the author re-format it appropriately. The
> reviewer's job is to /review/ the code, not fix it or clean it up.
Yes, but there are situations when you have to review code where
the author isn't available any more, as in the as said rare cases
I reported about.
In another somewhat different case we had to rewrite a piece of
code to add new functionality but keep (unspecified!) existing
functionality. That was not exactly a "review" but actually an
analysis, close to a black-box analysis. Reformatting was the
least effort compared to the behavioral analysis and stepwise
refactoring, using Extreme Programming methods, Pair Programming
and ad hoc introduction of regression tests. *That* was a nightmare!
Yes, the simple case is to just reject code. Or to let automated
tools run across the code to reject it in the first place without
any human interaction.
>
> One thing that is important for code reviewers, and any kind of
> comparisons between versions (such as for source code management
> systems), is to try to reduce the number of lines that are changed
> unnecessarily, and to try to make those changed lines clear.
What are you trying to suggest here? (It looks like I've never
had a case where it was important to compare source code with
previous versions just to remove "unnecessary" lines. - This
sounds really strange to me, but you may want to explain it.)
Janis
> [...]
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2025-02-26 13:31 -0800 |
| Message-ID | <877c5cpf3s.fsf@nosuchdomain.example.com> |
| In reply to | #390461 |
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
> On 26.02.2025 12:53, Ar Rakin wrote:
>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
>>>
>>> Re "goofy style"; I've seen someone preferring
>>>
>>> while (q(a,b))
>>> {
>>> a=b;
>>> f(x);
>>> if (c>d)
>>> {
>>> g(y);
>>> }
>>> }
>>>
>>> To each his own.
>>
>> That looks like a nightmare for the code reviewers.
>
> I cannot tell where that comes from; the person who uses it is an
> experienced Perl programmer - may that be some convention in that
> specific language context? (I can't tell.)
No, that's not a Perl convention. Most Perl code uses K&R-style brace
placement
while ($condition) {
do_something();
}
One interesting feature of Perl is that the braces are required.
[...]
--
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 | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-27 01:10 +0000 |
| Message-ID | <vpoe1e$2q6ak$6@dont-email.me> |
| In reply to | #390482 |
On Wed, 26 Feb 2025 13:31:51 -0800, Keith Thompson wrote: > One interesting feature of Perl is that the braces are required. And yet it doesn’t have C-style macros, which to me are the most obvious way one can get into trouble by omitting needed braces.
[toc] | [prev] | [next] | [standalone]
| From | Ar Rakin <rakinar2@onesoftnet.eu.org> |
|---|---|
| Date | 2025-02-27 19:05 +0600 |
| Message-ID | <87wmdbilm0.fsf@onesoftnet.eu.org> |
| In reply to | #390489 |
Lawrence D'Oliveiro <ldo@nz.invalid> writes: > On Wed, 26 Feb 2025 13:31:51 -0800, Keith Thompson wrote: > >> One interesting feature of Perl is that the braces are required. > > And yet it doesn’t have C-style macros, which to me are the most obvious > way one can get into trouble by omitting needed braces. What do you mean? Sorry I'm stupid sometimes.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2025-02-27 17:23 +0100 |
| Message-ID | <vpq3id$35inm$3@dont-email.me> |
| In reply to | #390509 |
On 27/02/2025 14:05, Ar Rakin wrote:
> Lawrence D'Oliveiro <ldo@nz.invalid> writes:
>
>> On Wed, 26 Feb 2025 13:31:51 -0800, Keith Thompson wrote:
>>
>>> One interesting feature of Perl is that the braces are required.
>>
>> And yet it doesn’t have C-style macros, which to me are the most obvious
>> way one can get into trouble by omitting needed braces.
>
> What do you mean? Sorry I'm stupid sometimes.
He is thinking of situations like this (ignore the stupidity of the
example) :
#define message(x) printf("Message: "); printf(x); printf("\n")
void foo(int y) {
message("Starting foo... ");
if (y < 0)
message("Y is negative");
message("Done foo.")
}
Reading "foo", you'd think that it would print "Message: Y is
negative\n" if y is negative. But in fact only the first statement in
the macro is covered by the conditional, and "Y is negative\n" will
always be printed. You can easily imagine how things could get a whole
lot worse from such mixups.
There are many ways to avoid this, including putting a "do { ... } while
(0)" wrapper around the statements in the macro, using an inline
function instead of a macro, writing macro names in all-caps as a
warning (I strongly dislike that convention), and always using braces
with conditionals even if they appear to cover just one statement.
I am not sure if there is a basis for judging the "most obvious" problem
that can occur from omitting braces in conditionals, but this is
certainly a strong contender for the title.
Another case that occurs is confusion about matching up else's with if's
in nested conditionals without braces.
[toc] | [prev] | [next] | [standalone]
| From | Ar Rakin <rakinar2@onesoftnet.eu.org> |
|---|---|
| Date | 2025-02-27 23:17 +0600 |
| Message-ID | <vpq6mq$36sdb$1@dont-email.me> |
| In reply to | #390523 |
On 2/27/25 10:23 PM, David Brown wrote:
> On 27/02/2025 14:05, Ar Rakin wrote:
>> Lawrence D'Oliveiro <ldo@nz.invalid> writes:
>>
>>> On Wed, 26 Feb 2025 13:31:51 -0800, Keith Thompson wrote:
>>>
>>>> One interesting feature of Perl is that the braces are required.
>>>
>>> And yet it doesn’t have C-style macros, which to me are the most obvious
>>> way one can get into trouble by omitting needed braces.
>>
>> What do you mean? Sorry I'm stupid sometimes.
>
> He is thinking of situations like this (ignore the stupidity of the
> example) :
>
> #define message(x) printf("Message: "); printf(x); printf("\n")
>
> void foo(int y) {
> message("Starting foo... ");
> if (y < 0)
> message("Y is negative");
> message("Done foo.")
> }
>
> Reading "foo", you'd think that it would print "Message: Y is
> negative\n" if y is negative. But in fact only the first statement in
> the macro is covered by the conditional, and "Y is negative\n" will
> always be printed. You can easily imagine how things could get a whole
> lot worse from such mixups.
>
> There are many ways to avoid this, including putting a "do { ... } while
> (0)" wrapper around the statements in the macro, using an inline
> function instead of a macro, writing macro names in all-caps as a
> warning (I strongly dislike that convention), and always using braces
> with conditionals even if they appear to cover just one statement.
>
> I am not sure if there is a basis for judging the "most obvious" problem
> that can occur from omitting braces in conditionals, but this is
> certainly a strong contender for the title.
>
> Another case that occurs is confusion about matching up else's with if's
> in nested conditionals without braces.
>
>
>
Ah, I see. Thanks for explaining.
--
Rakin
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2025-03-02 06:00 -0800 |
| Message-ID | <86h64bwn0y.fsf@linuxsc.com> |
| In reply to | #390461 |
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
> On 26.02.2025 12:53, Ar Rakin wrote:
>
>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
>>
>>> Re "goofy style"; I've seen someone preferring
>>>
>>> while (q(a,b))
>>> {
>>> a=b;
>>> f(x);
>>> if (c>d)
>>> {
>>> g(y);
>>> }
>>> }
>>>
>>> To each his own.
>>
>> That looks like a nightmare for the code reviewers.
>
> I cannot tell where that comes from; the person who uses it is an
> experienced Perl programmer - may that be some convention in that
> specific language context? (I can't tell.)
It's called Whitesmith (Whitesmiths?) style. It is (or was?)
used in PJ Plauger's company, who IIANM among other things wrote
one of the first C compilers done outside of Bell Labs.
For those who don't recognize the name, PJ Plauger was involved
in C standardization efforts from an early date, and was a member
of WG14 for more than 20 years even after the first C standard
was published.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2025-03-02 16:20 +0200 |
| Message-ID | <20250302162007.0000723c@yahoo.com> |
| In reply to | #390641 |
On Sun, 02 Mar 2025 06:00:13 -0800
Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:
> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
>
> > On 26.02.2025 12:53, Ar Rakin wrote:
> >
> >> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
> >>
> >>> Re "goofy style"; I've seen someone preferring
> >>>
> >>> while (q(a,b))
> >>> {
> >>> a=b;
> >>> f(x);
> >>> if (c>d)
> >>> {
> >>> g(y);
> >>> }
> >>> }
> >>>
> >>> To each his own.
> >>
> >> That looks like a nightmare for the code reviewers.
> >
> > I cannot tell where that comes from; the person who uses it is an
> > experienced Perl programmer - may that be some convention in that
> > specific language context? (I can't tell.)
>
> It's called Whitesmith (Whitesmiths?) style. It is (or was?)
> used in PJ Plauger's company, who IIANM among other things wrote
> one of the first C compilers done outside of Bell Labs.
>
> For those who don't recognize the name, PJ Plauger was involved
> in C standardization efforts from an early date, and was a member
> of WG14 for more than 20 years even after the first C standard
> was published.
In his younger years he was rather well-regarded SF author.
In his more advanced years specialized on supplying STL to C++ compiler
vendors.
I wonder what he is doing after entering 9th decade.
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-03-02 15:53 +0100 |
| Message-ID | <vq1rcr$qovu$1@dont-email.me> |
| In reply to | #390643 |
On 02.03.2025 15:20, Michael S wrote: > On Sun, 02 Mar 2025 06:00:13 -0800 > Tim Rentsch <tr.17687@z991.linuxsc.com> wrote: >> >> It's called Whitesmith (Whitesmiths?) style. It is (or was?) >> used in PJ Plauger's company, who IIANM among other things wrote >> one of the first C compilers done outside of Bell Labs. >> >> For those who don't recognize the name, PJ Plauger was involved >> in C standardization efforts from an early date, and was a member >> of WG14 for more than 20 years even after the first C standard >> was published. I know him and his reputation but nonetheless don't like that formatting style. - But thanks for letting us know the source. > In his younger years he was rather well-regarded SF author. (Never heard of his SF writings. But there's so many SF authors and yet more different SF styles, and preferences vary anyway.) > In his more advanced years specialized on supplying STL to C++ compiler > vendors. I sort of know him from (I think) a C++ standard library book; I thought it was earlier in the 90's but it was maybe this one: "The Draft Standard C++ Library" (1995). - I don't think that above mentioned formatting style was advertised in this book. (But I've only faint memories here.) Janis
[toc] | [prev] | [next] | [standalone]
| From | bart <bc@freeuk.com> |
|---|---|
| Date | 2025-02-25 20:21 +0000 |
| Message-ID | <vpl8no$25m4r$1@dont-email.me> |
| In reply to | #390427 |
On 25/02/2025 18:51, Kaz Kylheku wrote:
> On 2025-02-25, John McCue <jmccue@reddwf.jmcunx.com> wrote:
>> Ar Rakin <rakinar2@onesoftnet.eu.org> wrote:
>>> Hello there,
>>>
>>> I've been writing C code for a long time, in different styles, but
>>> always wanted to know which code style most people prefer. This is all
>>> about that question. Which one of the following do you prefer the most?
>>
>> GNU Style for me.
>
> OP didn't properly characterize GNU style.
>
> GNU style is actually something like this:
>
> if (flag)
> {
> switch (state)
> {
> case 42:
> {
> state = 73;
> break;
> }
> }
> }
> else
> {
> statement;
> }
This puts me in mind of trying to find the meat in a thin soup!
15 lines here, but in my personal syntax, it would be 8, and in Python
style, it might be only 6.
If I wrote it as C, I think it would be 10 lines (for example, it needs
'break').
There are actually only two lines here that do anything.
[toc] | [prev] | [next] | [standalone]
| From | Ar Rakin <rakinar2@onesoftnet.eu.org> |
|---|---|
| Date | 2025-02-26 17:51 +0600 |
| Message-ID | <878qps2abs.fsf@onesoftnet.eu.org> |
| In reply to | #390427 |
Kaz Kylheku <643-408-1753@kylheku.com> writes:
> On 2025-02-25, John McCue <jmccue@reddwf.jmcunx.com> wrote:
>> Ar Rakin <rakinar2@onesoftnet.eu.org> wrote:
>>> Hello there,
>>>
>>> I've been writing C code for a long time, in different styles, but
>>> always wanted to know which code style most people prefer. This is all
>>> about that question. Which one of the following do you prefer the most?
>>
>> GNU Style for me.
>
> OP didn't properly characterize GNU style.
>
> GNU style is actually something like this:
>
> if (flag)
> {
> switch (state)
> {
> case 42:
> {
> state = 73;
> break;
> }
> }
> }
> else
> {
> statement;
> }
>
> Four space indentation, but braces half-indent by two spaces.
Sorry, I should have showed this difference in my original post. I like
the GNU style except the weird indentation before the braces of control
statements. Not sure why they choose to indent that way.
The GNU style without indent before braces looks nice to me.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <643-408-1753@kylheku.com> |
|---|---|
| Date | 2025-02-26 17:59 +0000 |
| Message-ID | <20250226095615.829@kylheku.com> |
| In reply to | #390452 |
On 2025-02-26, Ar Rakin <rakinar2@onesoftnet.eu.org> wrote:
> Sorry, I should have showed this difference in my original post. I like
> the GNU style except the weird indentation before the braces of control
> statements. Not sure why they choose to indent that way.
>
> The GNU style without indent before braces looks nice to me.
Without the weird brace indent, it has nothing to do with GNU any more; it's
just two-space indentation, where opening braces are on their own line instead
of being "cuddled" into the previous line, which is very common:
if (flag)
{
switch (state)
{
case 42:
{
state = 73;
break;
}
}
}
else
{
statement;
}
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
Page 8 of 15 — ← Prev page 1 … 6 7 [8] 9 10 … 15 Next page →
Back to top | Article view | comp.lang.c
csiph-web