Groups | Search | Server Info | Login | Register


Groups > comp.lang.c

comp.lang.c

394306 articles, 303 threads (numbers 1824 – 399011) — flat view

| Advanced

Subject Author Date
Safety of casting from 'long' to 'int' (691 replies, showing first 100 — browse in flat view) kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-04-30 00:39 +0000
   → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-04-30 09:11 +0800
   → Re: Safety of casting from 'long' to 'int' James Kuyper <jameskuyper@alumni.caltech.edu> 2026-04-29 21:12 -0400
   → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-04-29 19:56 -0700
     → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-04-30 11:30 +0800
   → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-04-30 00:56 -0700
   → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-04-30 10:47 +0200
     → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-04-30 19:35 +0800
       → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-04-30 14:04 +0200
         → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-05-02 12:32 +0800
           → Re: Safety of casting from 'long' to 'int' Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-02 08:57 +0200
           → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-02 11:58 +0200
             → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-05-02 19:59 +0800
               → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-02 15:13 +0200
                 → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-05-02 22:32 +0800
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-02 17:17 +0200
                 → Re: Safety of casting from 'long' to 'int' James Kuyper <jameskuyper@alumni.caltech.edu> 2026-05-02 16:56 -0400
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-03 20:11 -0700
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-02 14:35 -0700
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-02 22:45 +0100
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-02 15:02 -0700
                 → Re: Safety of casting from 'long' to 'int' Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-02 17:24 +0200
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-02 10:54 -0700
                 → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-05-03 05:19 +0800
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-02 16:50 -0700
                 → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-05-03 07:56 +0800
               → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-02 14:18 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-02 15:52 +0200
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-02 16:39 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-02 21:16 +0200
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 01:38 +0100
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-02 17:52 -0700
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 12:39 +0200
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-03 14:19 -0700
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-04 08:41 +0200
                 → Re: Safety of casting from 'long' to 'int' Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-04 11:22 +0200
                 → Re: Safety of casting from 'long' to 'int' "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> 2026-05-04 13:47 -0700
                 → Re: Safety of casting from 'long' to 'int' Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-05 02:12 +0200
                 → Re: Safety of casting from 'long' to 'int' scott@slp53.sl.home (Scott Lurndal) 2026-05-05 15:02 +0000
                 → Re: Safety of casting from 'long' to 'int' Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-06 04:06 +0200
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-05 08:47 +0200
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-05 00:11 -0700
                 → Re: Safety of casting from 'long' to 'int' "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> 2026-05-05 00:15 -0700
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-02 16:52 -0700
                 → Re: Safety of casting from 'long' to 'int' Michael S <already5chosen@yahoo.com> 2026-05-03 08:26 +0300
                 → Re: Safety of casting from 'long' to 'int' antispam@fricas.org (Waldek Hebisch) 2026-05-03 14:24 +0000
                 → Re: Safety of casting from 'long' to 'int' Michael S <already5chosen@yahoo.com> 2026-05-03 18:53 +0300
                 → Re: Safety of casting from 'long' to 'int' antispam@fricas.org (Waldek Hebisch) 2026-05-03 19:46 +0000
                 → Re: Safety of casting from 'long' to 'int' Michael S <already5chosen@yahoo.com> 2026-05-03 23:07 +0300
                 → Re: Safety of casting from 'long' to 'int' antispam@fricas.org (Waldek Hebisch) 2026-05-03 21:19 +0000
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-03 16:02 -0700
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-06 19:43 -0700
                 → Re: Safety of casting from 'long' to 'int' antispam@fricas.org (Waldek Hebisch) 2026-05-08 18:47 +0000
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-08 15:10 -0700
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-09 12:40 +0200
                 → Re: Safety of casting from 'long' to 'int' cross@spitfire.i.gajendra.net (Dan Cross) 2026-05-08 20:30 +0000
                 → Re: Safety of casting from 'long' to 'int' scott@slp53.sl.home (Scott Lurndal) 2026-05-08 21:39 +0000
                 → Re: Safety of casting from 'long' to 'int' cross@spitfire.i.gajendra.net (Dan Cross) 2026-05-09 01:09 +0000
                 → Re: Safety of casting from 'long' to 'int' Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-09 06:25 +0200
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-10 09:14 -0700
                 → Re: Safety of casting from 'long' to 'int' kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-10 16:44 +0000
                 → Re: Safety of casting from 'long' to 'int' cross@spitfire.i.gajendra.net (Dan Cross) 2026-05-10 17:27 +0000
                 → Re: Safety of casting from 'long' to 'int' antispam@fricas.org (Waldek Hebisch) 2026-05-03 00:18 +0000
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 11:18 +0100
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-02 17:39 -0700
                 → Re: Safety of casting from 'long' to 'int' Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-04 00:55 +0200
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-03 16:50 -0700
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-02 18:53 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-02 21:20 +0200
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-02 14:46 -0700
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 01:14 +0200
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-02 17:02 -0700
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 12:46 +0200
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-02 23:51 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 01:20 +0200
                 → Re: Safety of casting from 'long' to 'int' wij <wyniijj5@gmail.com> 2026-05-03 07:43 +0800
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 12:50 +0200
                 → Re: Safety of casting from 'long' to 'int' James Kuyper <jameskuyper@alumni.caltech.edu> 2026-05-03 14:27 -0400
                 → Re: Safety of casting from 'long' to 'int' Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-03 20:27 -0700
                 → Re: Safety of casting from 'long' to 'int' antispam@fricas.org (Waldek Hebisch) 2026-05-03 00:30 +0000
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 01:55 +0100
                 → Re: Safety of casting from 'long' to 'int' antispam@fricas.org (Waldek Hebisch) 2026-05-03 02:21 +0000
                 → Re: Safety of casting from 'long' to 'int' Michael S <already5chosen@yahoo.com> 2026-05-03 08:53 +0300
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 11:59 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 13:27 +0200
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 13:46 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 15:06 +0200
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 17:39 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 20:54 +0200
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 21:29 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-03 23:11 +0200
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-03 15:47 -0700
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-03 23:59 +0100
                 → Re: Safety of casting from 'long' to 'int' David Brown <david.brown@hesbynett.no> 2026-05-04 09:28 +0200
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-04 13:22 +0100
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-03 15:17 -0700
                 → Re: Safety of casting from 'long' to 'int' "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> 2026-05-04 14:14 -0700
                 → Re: Safety of casting from 'long' to 'int' "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> 2026-05-04 14:21 -0700
                 → Re: Safety of casting from 'long' to 'int' Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-04 16:05 -0700
                 → Re: Safety of casting from 'long' to 'int' Bart <bc@freeuk.com> 2026-05-04 22:24 +0100
 
Is reallocarray() planned to be standardized? (9 replies) kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-14 20:09 +0000
   → Re: Is reallocarray() planned to be standardized? kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-14 21:10 +0000
     → Re: Is reallocarray() planned to be standardized? cross@spitfire.i.gajendra.net (Dan Cross) 2026-05-14 23:35 +0000
       → Re: Is reallocarray() planned to be standardized? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-14 17:46 -0700
         → Re: Is reallocarray() planned to be standardized? cross@spitfire.i.gajendra.net (Dan Cross) 2026-05-15 02:00 +0000
           → Re: Is reallocarray() planned to be standardized? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-14 19:22 -0700
             → Re: Is reallocarray() planned to be standardized? cross@spitfire.i.gajendra.net (Dan Cross) 2026-05-15 11:02 +0000
     → Re: Is reallocarray() planned to be standardized? Lawrence D’Oliveiro <ldo@nz.invalid> 2026-05-15 07:07 +0000
   → Re: Is reallocarray() planned to be standardized? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-14 17:26 -0700
     → Re: Is reallocarray() planned to be standardized? cross@spitfire.i.gajendra.net (Dan Cross) 2026-05-15 02:08 +0000
 
Are designated initializer supposed to zero padding? (30 replies) highcrew <high.crew3868@fastmail.com> 2026-05-10 22:47 +0200
   → Re: Are designated initializer supposed to zero padding? James Kuyper <jameskuyper@alumni.caltech.edu> 2026-05-10 19:15 -0400
     → Re: Are designated initializer supposed to zero padding? highcrew <high.crew3868@fastmail.com> 2026-05-11 09:11 +0200
       → Re: Are designated initializer supposed to zero padding? James Kuyper <jameskuyper@alumni.caltech.edu> 2026-05-12 16:02 -0400
         → Re: Are designated initializer supposed to zero padding? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-12 21:10 -0700
           → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-13 15:51 -0700
             → Re: Are designated initializer supposed to zero padding? David Brown <david.brown@hesbynett.no> 2026-05-14 11:36 +0200
               → Re: Are designated initializer supposed to zero padding? Richard Harnden <richard.nospam@gmail.invalid> 2026-05-14 11:47 +0100
                 → Re: Are designated initializer supposed to zero padding? David Brown <david.brown@hesbynett.no> 2026-05-14 14:11 +0200
               → Re: Are designated initializer supposed to zero padding? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-14 15:55 -0700
                 → Re: Are designated initializer supposed to zero padding? David Brown <david.brown@hesbynett.no> 2026-05-15 10:20 +0200
   → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-10 20:01 -0700
     → Re: Are designated initializer supposed to zero padding? highcrew <high.crew3868@fastmail.com> 2026-05-11 09:10 +0200
       → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-12 09:36 -0700
     → Re: Are designated initializer supposed to zero padding? scott@slp53.sl.home (Scott Lurndal) 2026-05-11 15:34 +0000
       → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-11 18:23 -0700
     → Re: Are designated initializer supposed to zero padding? Michael S <already5chosen@yahoo.com> 2026-05-11 23:22 +0300
       → Re: Are designated initializer supposed to zero padding? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-11 14:34 -0700
         → Re: Are designated initializer supposed to zero padding? Michael S <already5chosen@yahoo.com> 2026-05-12 00:55 +0300
           → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-11 15:27 -0700
           → Re: Are designated initializer supposed to zero padding? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-11 16:07 -0700
       → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-11 15:19 -0700
         → Re: Are designated initializer supposed to zero padding? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-11 16:10 -0700
           → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-11 18:13 -0700
             → Re: Are designated initializer supposed to zero padding? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-11 18:28 -0700
               → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-11 21:59 -0700
                 → Re: Are designated initializer supposed to zero padding? David Brown <david.brown@hesbynett.no> 2026-05-12 09:15 +0200
                 → Re: Are designated initializer supposed to zero padding? Keith Thompson <Keith.S.Thompson+u@gmail.com> 2026-05-12 00:27 -0700
                 → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-12 06:44 -0700
       → Re: Are designated initializer supposed to zero padding? Tim Rentsch <tr.17687@z991.linuxsc.com> 2026-05-11 18:15 -0700
   → Re: Are designated initializer supposed to zero padding? Michael S <already5chosen@yahoo.com> 2026-05-12 01:00 +0300
 
chat gpt is terribly great thing for c coding (16 replies) fir <profesor.fir@gmail.com> 2026-05-08 20:42 +0200
   → Re: chat gpt is terribly great thing for c coding kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-08 21:59 +0000
     → Re: chat gpt is terribly great thing for c coding fir <profesor.fir@gmail.com> 2026-05-09 00:17 +0200
       → Re: chat gpt is terribly great thing for c coding kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-08 22:31 +0000
         → Re: chat gpt is terribly great thing for c coding fir <profesor.fir@gmail.com> 2026-05-09 00:45 +0200
           → Re: chat gpt is terribly great thing for c coding David Odimegwu <hype@gmail.com> 2026-05-09 00:53 +0000
   → Re: chat gpt is terribly great thing for c coding Jim Jackson <jj@franjam.org.uk> 2026-05-12 18:01 +0000
     → Re: chat gpt is terribly great thing for c coding fir <profesor.fir@gmail.com> 2026-05-13 08:47 +0200
       → Re: chat gpt is terribly great thing for c coding kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-14 00:17 +0000
         → Re: chat gpt is terribly great thing for c coding Janis Papanagnou <janis_papanagnou+ng@hotmail.com> 2026-05-14 04:11 +0200
           → Re: chat gpt is terribly great thing for c coding kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-14 14:30 +0000
             → Re: chat gpt is terribly great thing for c coding "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> 2026-05-14 15:27 -0700
           → Re: chat gpt is terribly great thing for c coding fir <profesor.fir@gmail.com> 2026-05-14 19:04 +0200
         → Re: chat gpt is terribly great thing for c coding fir <profesor.fir@gmail.com> 2026-05-14 19:03 +0200
           → Re: chat gpt is terribly great thing for c coding kalevi@kolttonen.fi (Kalevi Kolttonen) 2026-05-14 18:30 +0000
             → Re: chat gpt is terribly great thing for c coding fir <profesor.fir@gmail.com> 2026-05-14 22:59 +0200
               → Re: chat gpt is terribly great thing for c coding fir <profesor.fir@gmail.com> 2026-05-14 23:08 +0200
 
thinking about the skinnest c (12 replies) fir <profesor.fir@gmail.com> 2026-05-12 15:08 +0200
   → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-12 15:25 +0200
     → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 10:51 +0200
       → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 12:12 +0200
     → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 11:06 +0200
     → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 13:55 +0200
       → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 14:15 +0200
         → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 14:48 +0200
           → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 15:04 +0200
             → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 15:16 +0200
   → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 15:30 +0200
     → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-13 15:50 +0200
       → Re: thinking about the skinnest c fir <profesor.fir@gmail.com> 2026-05-14 19:44 +0200
 
(fir's c theory) scopes are wrong (7 replies) fir <profesor.fir@gmail.com> 2026-05-12 12:22 +0200
   → Re: (fir's c theory) scopes are wrong?? Lawrence D’Oliveiro <ldo@nz.invalid> 2026-05-13 07:03 +0000
     → Re: (fir's c theory) scopes are wrong?? fir <profesor.fir@gmail.com> 2026-05-13 10:42 +0200
       → Re: (fir's c theory) scopes are wrong?? Lawrence D’Oliveiro <ldo@nz.invalid> 2026-05-13 08:59 +0000
         → Re: (fir's c theory) scopes are wrong?? fir <profesor.fir@gmail.com> 2026-05-13 11:57 +0200
           → Re: (fir's c theory) scopes are wrong?? fir <profesor.fir@gmail.com> 2026-05-13 12:00 +0200
             → Re: (fir's c theory) scopes are wrong?? fir <profesor.fir@gmail.com> 2026-05-13 12:08 +0200
           → Re: (fir's c theory) scopes are wrong?? Lawrence D’Oliveiro <ldo@nz.invalid> 2026-05-14 02:37 +0000

~Page 1 of ~597 (articles 398925–399011) Older →


csiph-web