Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.misc > #80763
| From | rbowman <bowman@montana.com> |
|---|---|
| Newsgroups | comp.os.linux.misc, alt.folklore.computers, alt.unix.geeks |
| Subject | Re: What is wrong with C? (and fond memories of VAX) |
| Date | 2026-01-08 20:34 +0000 |
| Message-ID | <msain4Fns51U2@mid.individual.net> (permalink) |
| References | (17 earlier) <4Wc7R.1392895$ACS3.688415@fx17.iad> <m7023mx6eh.ln2@Telcontar.valinor> <ms867vFblsjU2@mid.individual.net> <10jo43o$1e3l8$4@dont-email.me> <qoT7R.27032$hjM7.23661@fx07.iad> |
Cross-posted to 3 groups.
On Thu, 08 Jan 2026 19:16:38 GMT, Charlie Gibbs wrote: > On 2026-01-08, The Natural Philosopher <tnp@invalid.invalid> wrote: > >> On 07/01/2026 22:49, rbowman wrote: >> >>> On Wed, 7 Jan 2026 13:30:14 +0100, Carlos E.R. wrote: >>> >>>> It is possible that current C compilers signal many more problems >>>> that back then, but not runtime errors. >>> >>> gcc has become pickier. That isn't always a welcome thing when working >>> with legacy code and requires a search of the compiler options to get >>> it to shut up about such horrible heresies as assuming a function >>> returns an int. >>> >> Actually I welcome that. at leats 10% of the time the compiler finds a >> bug that way, and the other 90% i upgrade the source to be more >> explicit... > > +1 > > I re-worked my code over time so that -Wall yields no errors. > And then a new version of gcc comes out which picks even more nits, and > the process repeats. Not being a quick-and-dirty type, I consider it a > win overall. > > The one exception is its scrutiny of printf() calls. > That was a step too far, so I added -Wno-format-overflow. It was never a good idea but the legacy code often defined a variable in a .h file. The newer gcc implementations would throw multiple definition errors. Fixing it would have been painful. foo.h that defined int bar; might be included in several different programs so you would have to hunt down all the uses and then define bar someplace in a .c file. Great project for the new guy but at the time the newest guy had been there for 20 years. Adding the compiler flag to the relevant makefiles was easier. The missing int return type in function definitions wasn't as widespread and an easier fix. It was sort of pedantic since the return usually wasn't being checked anyway.
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 10:59 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 12:27 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 06:54 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 11:57 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 07:10 -0500
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 14:34 +0100
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 14:38 +0100
Re: naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-02 08:49 -0800
Re: C structure portability, naughty Python John Levine <johnl@taugh.com> - 2026-01-02 18:26 +0000
Re: C structure portability, naughty Python c186282 <c186282@nnada.net> - 2026-01-02 15:08 -0500
Re: C structure portability, naughty Python John Levine <johnl@taugh.com> - 2026-01-02 20:32 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-03 00:08 +0000
Re: C structure portability, naughty Python John Levine <johnl@taugh.com> - 2026-01-03 02:47 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-03 07:03 -0500
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-03 19:43 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-04 06:42 -0500
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-04 20:29 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-04 15:14 +0100
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-04 09:43 -0500
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-04 19:41 +0000
Re: Naughty C♯ Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-04 21:18 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-04 19:04 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 03:55 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-05 11:29 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 06:59 -0500
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 06:55 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 17:43 +0000
Re: Naughty C♯ Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-05 18:08 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 20:32 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 17:25 -0500
Re: Naughty C♯ Pancho <Pancho.Jones@protonmail.com> - 2026-01-06 07:55 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-06 06:19 -0500
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-05 08:26 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 18:09 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:16 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 05:57 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 17:48 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-05 18:09 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:20 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:24 +0000
Re: Naughty C♯ Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 21:44 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-05 19:31 -0500
Re: Naughty C♯ antispam@fricas.org (Waldek Hebisch) - 2026-01-06 12:16 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-06 11:12 -0500
Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 16:25 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 17:59 +0000
Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 19:59 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 21:57 +0000
Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-07 13:37 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-07 15:30 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 17:26 +0000
Re: Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 17:50 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-06 19:06 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-06 16:24 -0500
Re: Naughty C♯ antispam@fricas.org (Waldek Hebisch) - 2026-01-06 23:10 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-07 00:22 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-06 21:00 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-07 21:24 +0000
Re: Naughty C♯ antispam@fricas.org (Waldek Hebisch) - 2026-01-08 01:00 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-07 15:27 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-07 21:29 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 10:02 +0000
Re: Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-07 11:53 +0000
Re: Naughty C♯ Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 07:34 -0700
Re: Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-07 15:13 +0000
Re: Naughty C♯ Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 12:20 -0700
Re: Naughty C♯ John Ames <commodorejohn@gmail.com> - 2026-01-07 11:40 -0800
Re: Naughty C♯ Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 20:20 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-07 21:36 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 20:09 +0000
Re: Naughty C♯ "Carlos E.R." <robin_listas@es.invalid> - 2026-01-06 13:36 +0100
Re: Naughty C♯ Peter Flass <Peter@Iron-Spring.com> - 2026-01-06 07:55 -0700
Re: Naughty PL/I (was Re: Naughty C♯) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 20:04 +0000
What is wrong with C? (and fond memories of VAX) Lars Poulsen <lars@beagle-ears.com> - 2026-01-06 15:15 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-06 18:57 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-06 20:10 +0000
Re: What is wrong with C? (and fond memories of VAX) scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 21:59 +0000
Re: What is wrong with C? (and fond memories of VAX) Richard Kettlewell <invalid@invalid.invalid> - 2026-01-06 22:54 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-07 01:40 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: What is wrong with C? (and fond memories of VAX) "Carlos E.R." <robin_listas@es.invalid> - 2026-01-07 13:30 +0100
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-07 22:49 +0000
Re: What is wrong with C? (and fond memories of VAX) c186282 <c186282@nnada.net> - 2026-01-08 00:47 -0500
Re: What is wrong with C? (and fond memories of VAX) The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 11:23 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 19:16 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-08 20:34 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 22:45 +0000
Re: What is wrong with C? (and fond memories of VAX) sean@conman.org - 2026-01-09 00:23 +0000
Re: What is wrong with C? (and fond memories of VAX) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-09 04:54 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-09 07:08 +0000
Re: What is wrong with C? (and fond memories of VAX) scott@slp53.sl.home (Scott Lurndal) - 2026-01-09 16:18 +0000
Re: What is wrong with C? (and fond memories of VAX) "Carlos E.R." <robin_listas@es.invalid> - 2026-01-12 15:44 +0100
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-12 18:57 +0000
Re: What is wrong with C? (and fond memories of VAX) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-12 19:59 +0000
Re: What is wrong with C? (and fond memories of VAX) Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-13 06:13 -0500
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-13 18:22 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 17:17 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-06 18:59 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-05 11:26 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 03:34 +0000
Re: Naughty C♯ Richard Kettlewell <invalid@invalid.invalid> - 2026-01-05 08:24 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 19:06 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 06:50 -0500
Re: Naughty C♯ Pancho <Pancho.Jones@protonmail.com> - 2026-01-06 08:03 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-06 19:11 +0000
Re: Naughty C♯ Bob Vloon <usenet@bananacorp.nl.invalid> - 2026-01-07 12:01 +0000
Re: Naughty Java (was Re: Naughty C♯) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 20:18 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-05 03:09 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-05 13:31 +0100
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-04 20:04 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-05 13:25 +0100
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-05 15:47 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 21:45 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-05 09:20 -0800
Re: C structure portability, naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-05 18:10 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 21:45 +0000
Re: C structure portability, naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-05 23:28 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 00:14 +0000
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-06 00:23 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 00:57 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-06 06:24 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-06 08:14 -0800
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-06 18:57 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-06 11:03 -0800
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-07 09:00 -0800
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-07 12:23 -0500
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-08 14:01 +0100
Re: C structure portability, naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-07 20:55 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-06 20:58 +0000
Re: C structure portability, naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 09:48 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-07 20:17 +0000
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 04:57 +0000
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 15:29 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-06 06:21 -0500
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-05 18:13 +0000
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:16 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-04 19:48 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-05 13:37 +0100
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-04 21:17 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-05 04:01 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 07:07 -0500
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-05 11:05 -0800
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-03 18:32 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 19:38 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-02 21:33 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-02 15:00 -0700
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 00:52 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-02 19:51 -0700
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-03 06:09 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 20:38 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-03 16:58 -0500
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-04 08:01 -0700
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-04 16:25 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-05 04:12 +0000
Re: naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-04 07:14 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-04 20:25 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-04 07:59 -0700
Re: naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-04 16:31 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-04 19:41 +0000
Re: naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-04 20:05 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-05 04:17 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 05:57 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-05 19:20 +0000
Re: naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 17:35 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-06 06:36 +0000
Re: naughty Python Robert Riches <spamtrap42@jacob21819.net> - 2026-01-06 03:31 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 10:20 +0000
Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-06 18:48 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 22:02 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-07 00:27 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 02:09 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-07 14:18 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 20:40 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 22:23 +0000
Re: Case-dependent file systems Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-10 14:36 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-10 14:53 +0000
Re: Case-dependent file systems Richard Kettlewell <invalid@invalid.invalid> - 2026-01-10 15:08 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-11 02:00 +0000
Re: Case-dependent file systems Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-11 14:34 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-11 16:14 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-11 20:31 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-11 21:38 +0000
Re: Case-dependant file systems Richard Kettlewell <invalid@invalid.invalid> - 2026-01-06 23:09 +0000
Re: Case-dependant file systems "Carlos E.R." <robin_listas@es.invalid> - 2026-01-08 14:17 +0100
Re: Case-dependant file systems The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 13:36 +0000
Re: Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-08 14:05 +0000
Re: Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-08 14:15 +0000
Re: Case-dependant file systems Richard Kettlewell <invalid@invalid.invalid> - 2026-01-08 14:02 +0000
Re: Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-08 14:13 +0000
Re: Case-dependant file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-08 22:12 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-06 21:08 +0000
Re: C structures, was naughty Python John Levine <johnl@taugh.com> - 2026-01-02 22:41 +0000
Re: C structures, was naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-02 15:44 -0800
csiph-web