Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #170696 > unrolled thread
| Started by | fir <profesor.fir@gmail.com> |
|---|---|
| First post | 2023-07-12 07:18 -0700 |
| Last post | 2023-07-23 03:32 -0700 |
| Articles | 20 on this page of 968 — 32 participants |
Back to article view | Back to comp.lang.c
you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-12 07:18 -0700
Re: you think rust may outthrone c? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-07-13 01:37 -0400
Re: you think rust may outthrone c? jak <nospam@please.ty> - 2023-07-13 10:16 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-13 04:27 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-13 05:01 -0700
Re: you think rust may outthrone c? rek2 hispagatos <rek2@hispagatos.org.invalid> - 2023-07-13 14:10 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-13 17:51 +0000
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-13 18:56 +0000
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-13 19:39 +0000
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-13 20:30 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-13 22:29 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-14 00:19 +0100
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 06:43 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-14 11:47 +0100
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 11:04 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-14 21:01 +0000
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 21:21 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-14 13:52 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 12:08 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-14 17:10 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-14 21:32 +0000
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 22:04 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-14 21:02 +0000
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 21:35 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-15 14:30 +0200
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-15 16:36 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-15 15:49 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-15 16:02 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-16 01:18 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-15 16:25 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-16 11:07 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-16 05:42 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-16 16:17 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-16 07:44 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-16 09:57 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-16 10:34 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-16 10:41 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-16 20:55 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-17 01:54 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-17 02:43 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-17 03:16 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-17 14:54 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-17 07:08 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-17 16:43 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-17 17:19 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-21 00:05 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-21 16:52 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-17 17:21 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-17 09:44 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-17 21:24 +0200
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-17 15:10 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-17 18:46 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-17 21:27 +0200
Re: you think rust may outthrone c? jak <nospam@please.ty> - 2023-07-20 20:40 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-20 19:27 +0000
Re: you think rust may outthrone c? jak <nospam@please.ty> - 2023-07-20 22:16 +0200
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-20 19:17 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-17 16:15 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-17 09:17 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-17 21:41 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-17 23:02 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-17 08:22 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-17 15:01 -0700
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-17 15:01 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-18 09:26 +0200
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-18 00:33 -0700
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-18 00:35 -0700
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-18 00:37 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-18 13:05 +0100
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-19 17:56 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-18 09:13 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 12:18 +0100
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-18 01:24 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-17 15:06 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-17 23:11 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-17 15:30 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 00:07 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-18 01:28 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 02:20 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-18 02:12 +0000
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-18 03:25 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-18 09:55 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 12:29 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 02:29 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 09:16 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 12:38 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 14:24 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 14:12 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 16:33 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 16:37 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-19 16:55 +0000
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 19:44 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 12:06 +0100
Re: you think rust may outthrone c? Ike Naar <ike@sdf.org> - 2023-07-18 12:16 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 14:09 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-18 16:36 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 17:59 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 09:45 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 03:31 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-19 06:01 +0000
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-19 01:19 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-19 03:02 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-19 04:30 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 15:28 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-19 15:12 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-19 15:23 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 10:44 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-20 15:37 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-19 23:01 +0000
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-19 16:43 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 10:41 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 00:24 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-20 16:58 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-20 17:30 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-20 17:50 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-20 22:46 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 09:57 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 02:24 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 13:33 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 02:01 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-20 18:28 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 11:21 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-21 03:44 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 12:17 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 15:05 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 14:42 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 16:22 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 16:40 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 18:56 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 20:26 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-21 21:06 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-22 18:34 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-22 20:09 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 14:34 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 23:03 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 15:30 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-21 21:49 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-22 11:41 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-22 04:15 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-22 15:51 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-22 19:05 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 00:22 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-22 16:38 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 01:15 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-23 13:45 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 15:06 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-23 17:54 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 17:56 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-23 11:03 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-23 20:15 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 20:18 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-24 09:50 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-24 10:58 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-24 06:02 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-24 14:08 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-24 18:42 +0000
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-05 10:22 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-05 18:02 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-05 18:32 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-05 20:00 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-06 01:42 +0000
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-14 04:54 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 18:22 +0000
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-25 19:44 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-25 21:09 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-26 00:21 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-26 11:17 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-26 03:31 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-26 16:52 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-27 00:47 +0000
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-26 21:19 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-26 20:21 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-26 21:49 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-27 02:04 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-27 02:42 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-27 17:36 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-27 05:50 +0000
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-27 20:03 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-26 11:04 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-26 03:34 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-12 10:57 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-12 16:37 -0700
Re: you think rust may outthrone c? Spiros Bousbouras <spibou@gmail.com> - 2023-08-13 08:16 +0000
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 15:48 +0000
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-15 13:05 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-15 14:20 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-25 20:08 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-24 20:19 +0200
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 14:52 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-21 16:14 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 12:52 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-22 18:29 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-22 21:56 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-22 16:11 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-23 00:45 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-23 17:24 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 17:28 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-23 16:45 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-24 10:04 +0200
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-24 07:43 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-23 22:10 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-23 14:51 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 23:12 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-23 15:19 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-24 20:25 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-24 17:22 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-24 09:52 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-25 02:52 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-24 17:37 +0200
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-24 16:19 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-24 20:34 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-25 02:42 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-25 10:36 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-25 16:41 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-25 16:22 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-25 17:40 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-26 02:40 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-26 11:30 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-26 06:41 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-27 01:06 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-27 01:55 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-26 18:03 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-27 03:17 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-27 11:50 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-27 02:50 +0000
Overflow and undefined behaviour (WAS: you think rust may outthrone c?) Spiros Bousbouras <spibou@gmail.com> - 2023-07-25 16:43 +0000
Re: Overflow and undefined behaviour (WAS: you think rust may outthrone c?) Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-25 19:15 +0200
Re: Overflow and undefined behaviour (WAS: you think rust may outthrone c?) Bart <bc@freeuk.com> - 2023-07-25 18:43 +0100
Re: Overflow and undefined behaviour Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-25 15:03 -0700
Re: Overflow and undefined behaviour Spiros Bousbouras <spibou@gmail.com> - 2023-07-26 04:10 +0000
Re: Overflow and undefined behaviour Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-25 21:51 -0700
Re: Overflow and undefined behaviour Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-26 22:07 +0100
Re: Overflow and undefined behaviour Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-26 21:55 +0100
Re: Overflow and undefined behaviour Bart <bc@freeuk.com> - 2023-07-26 22:26 +0100
Re: Overflow and undefined behaviour Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-26 17:26 -0700
Re: Overflow and undefined behaviour Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-27 01:38 +0100
Re: Overflow and undefined behaviour Phil Carmody <pc+usenet@asdf.org> - 2023-08-13 14:53 +0300
Re: Overflow and undefined behaviour Bart <bc@freeuk.com> - 2023-08-13 13:07 +0100
What's wrong? The phrasing, that's what! (Was: Overflow and undefined behaviour) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-13 13:16 +0000
Re: Overflow and undefined behaviour Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-13 16:25 +0100
Re: Overflow and undefined behaviour Phil Carmody <pc+usenet@asdf.org> - 2023-08-14 12:10 +0300
Re: Overflow and undefined behaviour Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-14 04:33 -0700
Re: Overflow and undefined behaviour Phil Carmody <pc+usenet@asdf.org> - 2023-08-14 14:56 +0300
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-25 17:34 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-25 20:55 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-28 02:46 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-25 15:53 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-24 22:33 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-24 09:45 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-24 14:29 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-26 07:03 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-26 07:41 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-26 16:01 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-26 15:21 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-26 19:13 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-26 18:41 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-26 22:07 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-27 13:34 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-27 05:15 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-27 15:14 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-27 06:31 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-27 16:17 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-27 07:53 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-27 20:45 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-04 00:21 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-04 18:29 +0000
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 11:35 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-05 06:09 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-27 14:30 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-27 16:48 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-27 17:18 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-27 09:45 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-27 19:18 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-01 18:10 +0200
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-01 15:00 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-01 15:41 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-01 16:16 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-01 17:50 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-01 17:04 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-01 18:25 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-01 18:26 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-01 19:18 +0200
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-01 17:41 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-01 21:01 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-02 03:41 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-02 12:09 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-02 05:01 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-02 17:04 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-02 09:10 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-02 23:48 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-02 15:25 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-03 11:42 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 02:15 -0700
Re: you think rust may outthrone c? Spiros Bousbouras <spibou@gmail.com> - 2023-08-04 14:20 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-04 17:12 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 08:20 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-04 18:04 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 09:17 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-05 13:39 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-05 05:08 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 17:18 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 16:35 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 09:04 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-08 16:41 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 18:46 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 10:04 -0700
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 17:53 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-09 10:41 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-08 18:55 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-09 00:26 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 16:51 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 20:23 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-09 13:42 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-09 05:32 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-15 13:00 +0200
Re: you think rust may outthrone c? Michael S <already5chosen@yahoo.com> - 2023-08-09 05:35 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-09 05:48 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 14:17 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-15 13:06 +0200
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-09 13:44 +0000
Re: you think rust may outthrone c? doctor@doctor.nl2k.ab.ca (The Doctor) - 2023-08-09 14:00 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 15:09 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-09 07:15 -0700
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-09 15:48 +0000
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-09 08:54 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-09 15:18 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 16:01 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-09 15:50 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 17:51 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-09 21:51 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-15 13:16 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-09 09:18 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 00:05 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 19:10 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 16:24 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-09 14:24 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-09 17:18 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-09 17:38 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-15 13:35 +0200
Re: you think rust may outthrone c? Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 17:51 +0300
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-15 17:18 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 16:01 +0000
Re: you think rust may outthrone c? Phil Carmody <pc+usenet@asdf.org> - 2023-08-15 23:11 +0300
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 15:48 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-02 23:40 +0200
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-02 17:58 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-02 19:07 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-02 22:13 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-03 02:07 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-03 02:34 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-03 11:39 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-03 15:10 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-03 17:37 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-03 18:56 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-05 23:11 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-06 00:21 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-06 00:54 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-06 11:18 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-06 17:06 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-06 17:22 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-06 14:40 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-06 23:04 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-06 15:19 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-06 23:33 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-06 17:20 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-07 01:52 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-06 18:12 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-07 10:35 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-07 07:41 -0400
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-07 04:53 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-07 14:15 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-07 16:13 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-07 08:40 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-07 17:05 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-07 09:43 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-08 00:51 +0100
Making accountants cross (wa Re: you think rust may outthrone c?) Vir Campestris <vir.campestris@invalid.invalid> - 2023-08-10 15:38 +0100
Re: Making accountants cross (wa Re: you think rust may outthrone c?) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 16:26 +0100
Re: Making accountants cross (wa Re: you think rust may outthrone c?) Bart <bc@freeuk.com> - 2023-08-10 16:35 +0100
Re: Making accountants cross (wa Re: you think rust may outthrone c?) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 16:31 +0000
Re: Making accountants cross (wa Re: you think rust may outthrone c?) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-10 16:59 +0000
Re: Making accountants cross (wa Re: you think rust may outthrone c?) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-10 11:13 -0700
Re: Making accountants cross (wa Re: you think rust may outthrone c?) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 18:26 +0000
Re: Making accountants cross (wa Re: you think rust may outthrone c?) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-10 11:30 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 17:39 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-07 18:35 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-07 21:51 +0000
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-07 23:53 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 01:28 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-07 22:21 -0400
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 12:05 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 04:13 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 15:04 -0700
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-08 08:22 -0400
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 15:16 +0100
Re: you think rust may outthrone c? Michael S <already5chosen@yahoo.com> - 2023-08-08 09:15 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 18:33 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-08 21:58 -0400
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 11:05 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 11:53 +0100
Re: you think rust may outthrone c? Michael S <already5chosen@yahoo.com> - 2023-08-09 05:10 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 13:57 +0000
Re: you think rust may outthrone c? Michael S <already5chosen@yahoo.com> - 2023-08-08 08:55 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 18:23 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 15:28 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-07 15:17 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 01:08 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-07 18:31 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-08 00:43 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-08 06:20 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-08 15:56 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-08 08:35 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-09 02:44 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-09 05:53 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-07 16:20 +0000
Re: you think rust may outthrone c? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-08-07 13:10 -0400
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-07 10:24 -0700
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-07 22:46 -0400
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-07 14:52 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 01:01 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-07 17:59 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 11:34 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-08 08:34 -0400
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 14:51 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 23:19 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-08 22:58 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 00:33 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-08 23:50 +0000
Re: you think rust may outthrone c? Michael S <already5chosen@yahoo.com> - 2023-08-09 04:07 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-03 14:08 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-03 17:09 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-02 18:39 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-03 02:12 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-02 20:08 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-03 23:42 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-03 15:44 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-04 07:44 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-04 07:14 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-04 17:14 +0200
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-04 13:56 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-04 15:25 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-04 17:05 -0400
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-04 22:32 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-04 17:46 -0400
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-04 21:47 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-05 00:43 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-05 00:15 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-05 01:33 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-05 02:11 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-05 11:00 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-06 16:50 +0200
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-06 18:40 -0400
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-07 00:31 +0000
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-04 22:44 -0400
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-05 10:46 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-06 07:53 -0400
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-07 11:53 +0200
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-06 16:43 +0200
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-04 19:50 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-05 02:58 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-05 14:17 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-05 17:38 +0000
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-06 07:56 -0400
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-06 13:38 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-07 14:12 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-07 16:03 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-07 16:24 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-07 17:54 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-07 14:16 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-07 05:45 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-07 22:17 +0100
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-07 22:19 +0000
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-07 22:40 -0400
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 18:07 +0200
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-08 05:53 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 15:31 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 18:17 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 09:31 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-09 22:27 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-09 18:49 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-08 16:39 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-04 00:37 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-04 18:07 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 10:32 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-04 19:36 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 11:53 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 12:57 +0200
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 12:32 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 03:59 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 12:19 +0100
Re: you think rust may outthrone c? Richard Damon <Richard@Damon-Family.org> - 2023-08-08 08:40 -0400
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 12:17 +0200
Re: you think rust may outthrone c? Vir Campestris <vir.campestris@invalid.invalid> - 2023-08-04 18:00 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-04 19:25 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 13:11 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 04:22 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 14:45 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 06:02 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-08 15:39 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 08:36 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-09 02:15 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 12:36 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 14:05 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-08 15:31 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 14:34 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-08 16:11 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 15:49 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-08 21:05 +0100
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-08 09:02 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 16:27 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 16:09 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 16:42 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-08 18:38 +0200
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 09:47 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 19:14 +0100
Re: you think rust may outthrone c? Michael S <already5chosen@yahoo.com> - 2023-08-08 10:04 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 17:32 +0000
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 10:47 -0700
Re: you think rust may *DE*throne c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-09 03:04 +0100
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-08 19:44 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-09 11:22 +0100
Re: you think rust may *DE*throne c? Richard Harnden <richard.nospam@gmail.com> - 2023-08-09 11:36 +0100
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-09 11:58 +0100
Re: you think rust may *DE*throne c? Richard Harnden <richard.nospam@gmail.com> - 2023-08-09 14:29 +0100
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-09 16:02 +0000
Re: you think rust may *DE*throne c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-09 14:17 -0700
Re: you think rust may *DE*throne c? Dan Purgert <dan@djph.net> - 2023-08-09 11:05 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-09 13:32 +0100
Re: you think rust may *DE*throne c? Richard Harnden <richard.nospam@gmail.com> - 2023-08-09 14:32 +0100
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-09 15:07 +0100
Re: you think rust may *DE*throne c? Richard Harnden <richard.nospam@gmail.com> - 2023-08-09 15:48 +0100
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-09 16:08 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-09 15:52 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-09 18:09 +0100
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-09 16:34 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-12 10:36 +0200
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-12 02:58 -0700
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-13 08:18 +0200
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-13 07:07 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-13 07:34 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-13 08:24 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 14:10 +0200
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 00:18 -0700
Re: you think rust may *DE*throne c? Spiros Bousbouras <spibou@gmail.com> - 2023-08-13 08:08 +0000
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-13 03:44 -0700
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 06:16 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 15:53 +0000
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-13 08:58 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-13 17:36 +0100
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-13 03:38 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-12 12:12 +0100
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-13 09:30 +0200
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 16:02 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-13 17:48 +0100
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-13 18:53 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 20:41 +0000
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 20:40 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 04:28 +0000
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-14 15:52 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-14 16:06 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 14:19 +0200
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 14:33 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 17:24 +0200
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 15:58 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 15:58 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-15 15:27 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-11 08:43 +0200
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 11:17 +0100
Re: you think rust may *DE*throne c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-11 10:50 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 13:09 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-11 13:32 +0000
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-11 07:33 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-11 15:38 +0000
Re: you think rust may *DE*throne c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-11 16:45 +0000
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 10:20 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 18:35 +0100
Re: you think rust may *DE*throne c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-11 20:33 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 22:09 +0100
Re: you think rust may *DE*throne c? Richard Harnden <richard.nospam@gmail.com> - 2023-08-11 22:59 +0100
Re: you think rust may *DE*throne c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-08-11 23:25 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-12 00:26 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 14:24 +0200
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-11 21:30 +0000
Re: you think rust may *DE*throne c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-11 13:44 -0700
Re: you think rust may *DE*throne c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-11 14:55 -0700
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-11 21:38 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 22:46 +0100
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 14:32 +0200
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-12 12:07 +0100
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 15:34 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-11 15:39 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 17:26 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-11 16:53 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 18:15 +0100
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 18:46 +0100
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 14:35 +0200
Re: you think rust may *DE*throne c? Richard Harnden <richard.nospam@gmail.com> - 2023-08-11 19:43 +0100
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-13 09:34 +0200
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-13 16:02 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-13 17:38 +0100
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 14:37 +0200
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 14:34 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-15 16:17 +0100
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 17:25 +0200
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 16:00 +0000
Re: you think rust may *DE*throne c? Ike Naar <ike@sdf.org> - 2023-08-11 10:05 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 11:48 +0100
Re: you think rust may *DE*throne c? Dan Purgert <dan@djph.net> - 2023-08-09 15:06 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-09 16:16 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-10 09:38 +0200
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 10:51 +0100
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-09 15:57 +0000
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-10 00:15 +0200
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 00:22 +0100
Re: you think rust may *DE*throne c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-09 17:02 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 14:27 +0000
Re: you think rust may *DE*throne c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 00:01 +0100
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 00:39 +0100
Re: you think rust may *DE*throne c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-09 17:08 -0700
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 00:21 +0000
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 02:18 +0100
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 02:28 +0000
Re: you think rust may *DE*throne c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-09 22:42 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 14:23 +0000
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-09 19:10 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 14:24 +0000
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 14:21 +0000
Re: you think rust may *DE*throne c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 03:16 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 14:25 +0000
Re: you think rust may *DE*throne c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 16:18 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 15:53 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 16:15 +0000
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 16:59 +0000
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-10 10:12 -0700
Re: you think rust may *DE*throne c? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-08-10 17:16 +0000
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-10 10:27 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 17:54 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 18:18 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 18:16 +0000
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 14:44 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 14:56 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 23:17 +0100
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 16:06 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 16:20 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 16:38 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 16:58 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 18:43 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 01:30 +0100
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 17:58 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 07:03 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 07:28 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 07:47 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 08:06 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-11 16:13 +0100
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 08:28 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 08:37 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 08:46 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 08:58 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-11 09:52 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-10 18:21 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 23:09 +0100
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-11 01:14 +0000
Re: you think rust may *DE*throne c? Spiros Bousbouras <spibou@gmail.com> - 2023-08-11 05:42 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-11 06:07 +0000
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-11 13:30 +0000
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-11 19:41 +0000
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-12 08:21 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-12 11:14 -0700
Re: you think rust may *DE*throne c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 17:39 +0100
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-10 09:40 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 17:48 +0100
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 14:45 +0200
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-15 13:52 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-15 14:40 +0000
Re: you think rust may *DE*throne c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-15 06:26 -0700
Re: you think rust may *DE*throne c? David Brown <david.brown@hesbynett.no> - 2023-08-15 15:43 +0200
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-16 10:09 -0700
Re: you think rust may *DE*throne c? fir <profesor.fir@gmail.com> - 2023-08-18 07:36 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 16:33 +0100
Re: you think rust may *DE*throne c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-10 16:57 +0000
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-10 01:10 -0700
Re: you think rust may *DE*throne c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 16:08 +0100
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-10 09:49 -0700
Re: you think rust may *DE*throne c? Bart <bc@freeuk.com> - 2023-08-10 18:08 +0100
Re: you think rust may *DE*throne c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-10 21:04 +0100
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 20:56 +0000
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-10 14:20 +0000
Re: you think rust may *DE*throne c? Michael S <already5chosen@yahoo.com> - 2023-08-08 10:53 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 18:30 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-09 23:14 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-08 19:07 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 15:46 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 00:15 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 23:54 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 17:52 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-09 02:22 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 19:01 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-08 16:57 -0700
Re: you think rust may *DE*throne c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-08 14:03 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-27 13:13 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-28 23:35 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-28 19:21 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-29 21:15 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-29 14:45 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-29 00:05 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-29 11:19 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-29 13:47 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-29 15:10 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-29 16:00 +0000
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-29 15:30 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-29 14:22 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-29 14:49 -0700
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-27 14:07 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-27 16:03 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-01 19:43 +0200
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-01 18:37 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-01 22:16 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-01 21:53 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-01 23:28 +0100
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-08-02 01:54 +0000
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-02 11:14 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-02 18:23 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-02 19:02 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-03 11:28 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-03 11:53 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-08-03 11:54 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-08-02 18:12 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-01 14:45 -0700
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-26 15:02 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-26 17:08 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 12:38 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 12:29 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 09:46 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 02:29 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-22 21:04 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 14:38 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-19 07:00 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 17:31 +0100
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-19 14:54 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 10:55 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-21 03:07 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-19 12:07 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 15:15 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 17:08 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-19 17:30 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 19:22 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 20:28 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 16:27 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 17:06 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 20:39 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 20:21 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-19 15:42 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-19 23:31 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-19 18:53 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-20 01:46 -0700
Re: you think rust may outthrone c? Spiros Bousbouras <spibou@gmail.com> - 2023-07-20 09:51 +0000
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-20 03:36 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-20 12:13 +0100
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-20 13:06 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 11:28 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-20 16:44 +0000
Re: you think rust may outthrone c? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-21 01:22 -0400
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 02:03 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-22 15:37 -0700
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-20 02:08 +0100
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-22 15:43 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 11:07 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-21 02:49 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 10:17 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-21 16:30 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-21 12:54 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-22 15:56 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-19 17:22 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-19 21:01 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-19 20:46 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-19 20:47 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-19 21:49 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 11:42 +0200
Re: you think rust may outthrone c? "minf...@arcor.de" <minforth@arcor.de> - 2023-07-20 05:39 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 14:55 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-20 15:03 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 18:22 +0200
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-20 15:54 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 10:18 +0200
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-20 13:04 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 10:20 +0200
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-20 20:51 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-20 11:38 +0200
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-20 13:03 -0700
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-21 10:24 +0200
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-21 13:03 -0700
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-23 16:17 -0700
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-21 14:35 +0000
Re: you think rust may outthrone c? scott@slp53.sl.home (Scott Lurndal) - 2023-07-18 14:34 +0000
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-18 08:04 -0700
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-17 21:27 -0700
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 12:10 +0100
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-18 16:43 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-18 14:59 +0100
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-17 17:44 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-18 00:14 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-18 10:13 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-17 16:10 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-17 16:13 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-17 16:16 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-17 16:29 -0700
Yeah, C is harder than many programming languages. Your point? (Was: you think rust may outthrone c?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-14 11:24 +0000
Re: Yeah, C is harder than many programming languages. Your point? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 11:30 +0000
Re: Yeah, C is harder than many programming languages. Your point? fir <profesor.fir@gmail.com> - 2023-07-14 05:20 -0700
Re: Yeah, C is harder than many programming languages. Your point? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 12:29 +0000
Re: Yeah, C is harder than many programming languages. Your point? fir <profesor.fir@gmail.com> - 2023-07-14 05:46 -0700
Re: Yeah, C is harder than many programming languages. Your point? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 13:01 +0000
Re: Yeah, C is harder than many programming languages. Your point? fir <profesor.fir@gmail.com> - 2023-07-14 06:07 -0700
Re: Yeah, C is harder than many programming languages. Your point? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 13:26 +0000
Why not? (Was: Yeah, C is harder than many programming languages. Your point?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-14 13:32 +0000
Re: Why not? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 13:43 +0000
Re: Why not? (killfiles) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-14 14:10 +0000
Re: Why not? (killfiles) kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 14:28 +0000
Re: Why not? (killfiles) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-14 18:46 +0000
Re: Yeah, C is harder than many programming languages. Your point? fir <profesor.fir@gmail.com> - 2023-07-14 06:52 -0700
Re: Yeah, C is harder than many programming languages. Your point? fir <profesor.fir@gmail.com> - 2023-07-15 02:21 -0700
Re: Yeah, C is harder than many programming languages. Your point? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-14 09:14 -0400
Posting for our own amusement (Was: Yeah, C is harder than many programming languages. Your point?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-14 13:29 +0000
Re: Posting for our own amusement (Was: Yeah, C is harder than many programming languages. Your point?) "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-07-14 07:26 -0700
Re: Posting for our own amusement (Was: Yeah, C is harder than many programming languages. Your point?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-14 14:39 +0000
Re: Posting for our own amusement (Was: Yeah, C is harder than many programming languages. Your point?) David Brown <david.brown@hesbynett.no> - 2023-07-14 17:30 +0200
Re: Posting for our own amusement (Was: Yeah, C is harder than many programming languages. Your point?) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-14 20:53 +0000
Re: Yeah, C is harder than many programming languages. Your point? fir <profesor.fir@gmail.com> - 2023-07-14 06:30 -0700
Re: Yeah, C is harder than many programming languages. Your point? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 13:30 +0000
Re: Yeah, C is harder than many programming languages. Your point? gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-14 12:29 +0000
Re: Yeah, C is harder than many programming languages. Your point? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 12:46 +0000
Re: Yeah, C is harder than many programming languages. Your point? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-14 20:46 +0000
Re: Yeah, C is harder than many programming languages. Your point? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 21:49 +0000
Re: you think rust may outthrone c? Po Lu <luangruo@yahoo.com> - 2023-07-14 20:52 +0800
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 13:16 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-14 17:34 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 16:20 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-14 19:11 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 17:26 +0000
Re: you think rust may outthrone c? Paul N <gw7rib@aol.com> - 2023-07-15 04:42 -0700
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-15 12:29 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-15 18:40 +0200
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-20 19:05 -0700
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-14 21:25 +0000
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 22:30 +0000
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-14 15:48 -0700
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 22:56 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-15 14:41 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-15 12:55 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-15 18:46 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-15 17:28 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-15 20:20 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-15 18:42 +0000
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-22 06:46 -0700
Re: you think rust may outthrone c? Po Lu <luangruo@yahoo.com> - 2023-07-15 14:12 +0800
Re: you think rust may outthrone c? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-15 01:05 -0700
Re: you think rust may outthrone c? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-07-20 18:54 -0700
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-15 08:59 +0000
Re: you think rust may outthrone c? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-17 02:26 -0400
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-14 20:43 +0000
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 21:58 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-14 09:32 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-14 07:58 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-14 12:56 +0200
OT Re: you think rust may outthrone c? jak <nospam@please.ty> - 2023-07-14 10:20 +0200
Re: you think rust may outthrone c? Po Lu <luangruo@yahoo.com> - 2023-07-14 20:48 +0800
Re: you think rust may outthrone c? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-07-17 18:33 +0300
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-17 20:47 +0100
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-17 21:14 +0100
Re: you think rust may outthrone c? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-07-17 21:47 +0100
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-17 18:26 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-17 17:00 +0000
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-17 20:03 +0200
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-17 20:28 +0000
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-19 18:06 +0200
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-17 11:42 -0700
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-17 19:18 +0000
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-17 12:20 -0700
Re: you think rust may outthrone c? kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-17 20:26 +0000
Re: you think rust may outthrone c? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-18 01:06 -0700
Re: you think rust may outthrone c? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-07-18 06:37 -0400
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-19 18:07 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-19 09:17 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-20 11:06 +0200
Re: you think rust may outthrone c? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-07-19 19:16 -0400
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-20 11:07 +0200
Re: you think rust may outthrone c? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-07-20 08:49 -0400
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-20 16:25 +0200
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-20 19:48 +0200
Re: you think rust may outthrone c? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-07-21 02:06 -0400
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-21 09:32 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-21 06:06 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-21 06:13 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 14:57 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 07:10 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 16:29 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 07:33 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 16:35 +0200
Re: you think rust may outthrone c? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-07-22 01:30 -0400
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 15:00 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-22 14:53 +0100
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 07:22 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 16:32 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 07:42 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 17:01 +0200
Re: you think rust may outthrone c? jak <nospam@please.ty> - 2023-07-22 17:45 +0200
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 18:22 +0200
Re: you think rust may outthrone c? jak <nospam@please.ty> - 2023-07-22 19:00 +0200
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 19:06 +0200
Re: you think rust may outthrone c? jak <nospam@please.ty> - 2023-07-22 19:34 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 14:15 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 14:20 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 14:25 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 14:33 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 03:23 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 03:28 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-22 16:48 +0100
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 18:24 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-22 19:02 +0100
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 20:06 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 14:07 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 03:29 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 00:52 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 02:03 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 02:18 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 13:44 +0200
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 13:43 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 05:03 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 05:07 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 05:14 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 05:54 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 05:31 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 05:42 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 15:16 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 06:39 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 15:49 +0200
Re: you think rust may outthrone c? Bart <bc@freeuk.com> - 2023-07-23 14:56 +0100
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 16:11 +0200
Re: you think rust may outthrone c? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-07-23 14:34 +0000
Re: you think rust may outthrone c? David Brown <david.brown@hesbynett.no> - 2023-07-23 18:43 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 07:19 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 16:34 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 07:48 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 07:58 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 08:00 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 17:01 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 08:09 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 16:59 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 08:02 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 17:07 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 08:18 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 17:42 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 08:51 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 18:26 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 08:42 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 09:20 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 18:27 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 14:06 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 03:30 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 00:58 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 01:06 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 15:16 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 06:40 -0700
Re: you think rust may outthrone c? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-22 08:49 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 08:57 -0700
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-22 09:01 -0700
Re: you think rust may outthrone c? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-22 18:30 +0200
Re: you think rust may outthrone c? fir <profesor.fir@gmail.com> - 2023-07-23 03:32 -0700
Page 33 of 49 — ← Prev page 1 … 31 32 [33] 34 35 … 49 Next page →
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 14:56 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <5a314af7-84f3-40dc-b04a-e5a8b4166aben@googlegroups.com> |
| In reply to | #172048 |
czwartek, 10 sierpnia 2023 o 23:44:31 UTC+2 fir napisał(a):
> czwartek, 10 sierpnia 2023 o 20:16:49 UTC+2 Kaz Kylheku napisał(a):
> >
> > DLLs are lacking in some technology like symbol versioning, linking
> > in any direction (DLL cannot attach to symbols exported by executable)
> > and such. Plus the use of clunky .lib files taht SO's don't require,
> > and __decl(dllexport) and other cruft. (That pragma mechanism by
> > which a source file indicates a needed DLL doesn't need a .lib file
> > though, IIRC).
> >
> i dont remember as to this exe, though i remember i was testing it and
> those relative usage - when i was writing more than one dll was making
> some problems to me.. i dont remember hovever if you cant call functions in exe
> though - problem was rather that when you want to compile dll using other dll you need to have the other build (becouse compilaton readed binary dll to check if symbols exist even if
> linking is rruntime - this is in fact stupid but this is a consequence of fact that when
> you link to a symbol compilers dont know in which of dlls you want to0 link it is,
> and it need to put not only symbols but their parent module names in output) ..
> it is mighty stupid bcouse you cant compile code that uses the dll that you dont really get
> (unles there is some way providing this info on symbold what is the name of the
> parent module of them, __declspec(dllimport) are not a problem though
>
> it should be some other extension too like
>
> __something "green fire.dll" //import module name for given symbols
> {
> __declspec(dllimport) int foo(int a);
> __declspec(dllimport) float xx;
> }
>
ofc "normal c" also has this error becouse when you put symbol names in
normal c header you would in fact also needed to enclose it in module name
and some { } better too
they didnt do this probably as some may say, the obj modules cant have duplicates becouse
in c code you couldnt call a symbol that has duplicates at all..but on assembly/binary level
you totally can as those symbold evenif 10 of them have identycal name are there
just 32 bit adresses each of other value so on binary level there is no problem
with duplicated names of imports
more better adding those enclosing module names just gives something like compile time
or link time checking - you dont mistake where somethig should be, also get better
compile/link errors and also simply could use thet extended headers info to link
without providing this info in commandline
> but i dont know if there is something like that
>
>
> but besides in practice there are no problems with dlls at least when i use it
> is a breat with butter
>
> dlls are very likeable and i tell not a first time that if someone coded in c on windows he must
> learn dlls becouse dlls are sorta part of practical c..and its real nice part (ofc it lacks types
> encoded and call conventions which would allow to just get rid of headers - check my thread/post on it)
>
> probably it would allow even normal c to get rid of headers as pif everything would just work without headers people just could not include them and tha wouldnt break codes
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-10 23:17 +0100 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <ub3nm7$haft$2@dont-email.me> |
| In reply to | #172048 |
On 10/08/2023 22:44, fir wrote:
> czwartek, 10 sierpnia 2023 o 20:16:49 UTC+2 Kaz Kylheku napisał(a):
>>
>> DLLs are lacking in some technology like symbol versioning, linking
>> in any direction (DLL cannot attach to symbols exported by executable)
>> and such. Plus the use of clunky .lib files taht SO's don't require,
>> and __decl(dllexport) and other cruft. (That pragma mechanism by
>> which a source file indicates a needed DLL doesn't need a .lib file
>> though, IIRC).
>>
>
> i dont remember as to this exe, though i remember i was testing it and
> those relative usage - when i was writing more than one dll was making
> some problems to me.. i dont remember hovever if you cant call functions in exe
> though - problem was rather that when you want to compile dll using other dll you need to have the other build (becouse compilaton readed binary dll to check if symbols exist even if
> linking is rruntime - this is in fact stupid but this is a consequence of fact that when
> you link to a symbol compilers dont know in which of dlls you want to0 link it is,
> and it need to put not only symbols but their parent module names in output) ..
> it is mighty stupid bcouse you cant compile code that uses the dll that you dont really get
> (unles there is some way providing this info on symbold what is the name of the
> parent module of them, __declspec(dllimport) are not a problem though
>
> it should be some other extension too like
>
> __something "green fire.dll" //import module name for given symbols
> {
> __declspec(dllimport) int foo(int a);
> __declspec(dllimport) float xx;
> }
>
> but i dont know if there is something like that
>
>
> but besides in practice there are no problems with dlls at least when i use it
> is a breat with butter
>
> dlls are very likeable and i tell not a first time that if someone coded in c on windows he must
> learn dlls becouse dlls are sorta part of practical c..and its real nice part (ofc it lacks types
> encoded and call conventions which would allow to just get rid of headers - check my thread/post on it)
>
> probably it would allow even normal c to get rid of headers as pif everything would just work without headers people just could not include them and tha wouldnt break codes
How would that work? To use a function exported from a DLL, you will
need a function signature, perhaps a set of usertypes, enums and #defines.
All the stuff that normally is provided by a header.
Where would that information come from?
(My own idea was for an interface info to be embedded inside the DLL,
and accessed by calling a special exported function. For C, that could
just return a string containing the normal header code.
But it would need cooperation from the people creating the DLL (who
could be writing in any language, not C).
And from C compilers to delve inside DLL files (and at an early stage
long before linking). Since C compilers can't even shake off
anachronisms like -lm and a.out, I can't see that happening.)
My idea was for my own private use
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 16:06 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <08e28be9-2867-46be-872c-86bc3418b908n@googlegroups.com> |
| In reply to | #172051 |
piątek, 11 sierpnia 2023 o 00:17:57 UTC+2 Bart napisał(a):
> On 10/08/2023 22:44, fir wrote:
> > czwartek, 10 sierpnia 2023 o 20:16:49 UTC+2 Kaz Kylheku napisał(a):
> >>
> >> DLLs are lacking in some technology like symbol versioning, linking
> >> in any direction (DLL cannot attach to symbols exported by executable)
> >> and such. Plus the use of clunky .lib files taht SO's don't require,
> >> and __decl(dllexport) and other cruft. (That pragma mechanism by
> >> which a source file indicates a needed DLL doesn't need a .lib file
> >> though, IIRC).
> >>
> >
> > i dont remember as to this exe, though i remember i was testing it and
> > those relative usage - when i was writing more than one dll was making
> > some problems to me.. i dont remember hovever if you cant call functions in exe
> > though - problem was rather that when you want to compile dll using other dll you need to have the other build (becouse compilaton readed binary dll to check if symbols exist even if
> > linking is rruntime - this is in fact stupid but this is a consequence of fact that when
> > you link to a symbol compilers dont know in which of dlls you want to0 link it is,
> > and it need to put not only symbols but their parent module names in output) ..
> > it is mighty stupid bcouse you cant compile code that uses the dll that you dont really get
> > (unles there is some way providing this info on symbold what is the name of the
> > parent module of them, __declspec(dllimport) are not a problem though
> >
> > it should be some other extension too like
> >
> > __something "green fire.dll" //import module name for given symbols
> > {
> > __declspec(dllimport) int foo(int a);
> > __declspec(dllimport) float xx;
> > }
> >
> > but i dont know if there is something like that
> >
> >
> > but besides in practice there are no problems with dlls at least when i use it
> > is a breat with butter
> >
> > dlls are very likeable and i tell not a first time that if someone coded in c on windows he must
> > learn dlls becouse dlls are sorta part of practical c..and its real nice part (ofc it lacks types
> > encoded and call conventions which would allow to just get rid of headers - check my thread/post on it)
> >
> > probably it would allow even normal c to get rid of headers as pif everything would just work without headers people just could not include them and tha wouldnt break codes
> How would that work? To use a function exported from a DLL, you will
> need a function signature, perhaps a set of usertypes, enums and #defines.
>
> All the stuff that normally is provided by a header.
>
> Where would that information come from?
>
> (My own idea was for an interface info to be embedded inside the DLL,
> and accessed by calling a special exported function. For C, that could
> just return a string containing the normal header code.
>
> But it would need cooperation from the people creating the DLL (who
> could be writing in any language, not C).
>
> And from C compilers to delve inside DLL files (and at an early stage
> long before linking). Since C compilers can't even shake off
> anachronisms like -lm and a.out, I can't see that happening.)
>
>
>
> My idea was for my own private use
doi
lern how PE format works coz it is really important - not mucnh pleasant to read but important as hell
as how to encode this see a thread named
"new abi proposition (for modules/dynamic libraries)" from a month ago (13 VII)
doing this is not a problem PE (exe/dll) format is open to a section, in fact .iidata import section is just mainly a list of strings with dll names and its symbol names to import - it also has this array of pointers but empty (afair, or other junk) - those names are important as windows links by names - and just fill the pointers with proper values
i mean when i gor my program.exe that uses my green.fire.dll then it works like that::
windows load green.fire.dll into ram, the code for function "SetupWindow5" is placed in some ram area (in program.exe space) dll has export table where "SetupWindow5" exist and offset in dll where asm code for it is stored in that dll ...program.exe also is loaded in ram its import section is then loaded in ram it also has "SetupWindow5" string and correspondant junk pointer which is then fulfilled with real adres, so when i write
call ("green.fire.dll"->SetupWindow5)
then it really is something like call (0x00401034) which pointer is in import section of loaded exe
(whuch was loaded under say 0x00400000) and its value points to sax 0x0050cccc where code oof SetpuWindow5 of dll was loaded
that was digression but imo its important to understend it well
import section is just section in PE/dll file - but it contais literally only module names and symbol names with nothing more (except that junk pointers) - you need just add another section
in dfil file containing calling convention for each function symbol, and possibly also list of argument types and names, and even type definitions
roughly how it should look like i described in that post month ago
i could do it myself as i got my own assembler - and maybe i should becouse if someone else would do that before there is a chance it will do it more bad than i (im not in hurry hovever and it can take me 10 years becouse i got some other obligations and not code to much recent years)
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 16:20 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <948cea01-ef27-44a3-a18b-82d3cf0538c8n@googlegroups.com> |
| In reply to | #172052 |
piątek, 11 sierpnia 2023 o 01:06:37 UTC+2 fir napisał(a):
> piątek, 11 sierpnia 2023 o 00:17:57 UTC+2 Bart napisał(a):
> > On 10/08/2023 22:44, fir wrote:
> > > czwartek, 10 sierpnia 2023 o 20:16:49 UTC+2 Kaz Kylheku napisał(a):
> > >>
> > >> DLLs are lacking in some technology like symbol versioning, linking
> > >> in any direction (DLL cannot attach to symbols exported by executable)
> > >> and such. Plus the use of clunky .lib files taht SO's don't require,
> > >> and __decl(dllexport) and other cruft. (That pragma mechanism by
> > >> which a source file indicates a needed DLL doesn't need a .lib file
> > >> though, IIRC).
> > >>
> > >
> > > i dont remember as to this exe, though i remember i was testing it and
> > > those relative usage - when i was writing more than one dll was making
> > > some problems to me.. i dont remember hovever if you cant call functions in exe
> > > though - problem was rather that when you want to compile dll using other dll you need to have the other build (becouse compilaton readed binary dll to check if symbols exist even if
> > > linking is rruntime - this is in fact stupid but this is a consequence of fact that when
> > > you link to a symbol compilers dont know in which of dlls you want to0 link it is,
> > > and it need to put not only symbols but their parent module names in output) ..
> > > it is mighty stupid bcouse you cant compile code that uses the dll that you dont really get
> > > (unles there is some way providing this info on symbold what is the name of the
> > > parent module of them, __declspec(dllimport) are not a problem though
> > >
> > > it should be some other extension too like
> > >
> > > __something "green fire.dll" //import module name for given symbols
> > > {
> > > __declspec(dllimport) int foo(int a);
> > > __declspec(dllimport) float xx;
> > > }
> > >
> > > but i dont know if there is something like that
> > >
> > >
> > > but besides in practice there are no problems with dlls at least when i use it
> > > is a breat with butter
> > >
> > > dlls are very likeable and i tell not a first time that if someone coded in c on windows he must
> > > learn dlls becouse dlls are sorta part of practical c..and its real nice part (ofc it lacks types
> > > encoded and call conventions which would allow to just get rid of headers - check my thread/post on it)
> > >
> > > probably it would allow even normal c to get rid of headers as pif everything would just work without headers people just could not include them and tha wouldnt break codes
> > How would that work? To use a function exported from a DLL, you will
> > need a function signature, perhaps a set of usertypes, enums and #defines.
> >
> > All the stuff that normally is provided by a header.
> >
> > Where would that information come from?
> >
> > (My own idea was for an interface info to be embedded inside the DLL,
> > and accessed by calling a special exported function. For C, that could
> > just return a string containing the normal header code.
> >
> > But it would need cooperation from the people creating the DLL (who
> > could be writing in any language, not C).
> >
> > And from C compilers to delve inside DLL files (and at an early stage
> > long before linking). Since C compilers can't even shake off
> > anachronisms like -lm and a.out, I can't see that happening.)
> >
> >
> >
> > My idea was for my own private use
> doi
> lern how PE format works coz it is really important - not mucnh pleasant to read but important as hell
>
> as how to encode this see a thread named
> "new abi proposition (for modules/dynamic libraries)" from a month ago (13 VII)
>
> doing this is not a problem PE (exe/dll) format is open to a section, in fact .iidata import section is just mainly a list of strings with dll names and its symbol names to import - it also has this array of pointers but empty (afair, or other junk) - those names are important as windows links by names - and just fill the pointers with proper values
>
> i mean when i gor my program.exe that uses my green.fire.dll then it works like that::
>
> windows load green.fire.dll into ram, the code for function "SetupWindow5" is placed in some ram area (in program.exe space) dll has export table where "SetupWindow5" exist and offset in dll where asm code for it is stored in that dll ...program.exe also is loaded in ram its import section is then loaded in ram it also has "SetupWindow5" string and correspondant junk pointer which is then fulfilled with real adres, so when i write
>
> call ("green.fire.dll"->SetupWindow5)
>
> then it really is something like call (0x00401034) which pointer is in import section of loaded exe
> (whuch was loaded under say 0x00400000) and its value points to sax 0x0050cccc where code oof SetpuWindow5 of dll was loaded
>
> that was digression but imo its important to understend it well
>
> import section is just section in PE/dll file - but it contais literally only module names and symbol names with nothing more (except that junk pointers) - you need just add another section
> in dfil file containing calling convention for each function symbol, and possibly also list of argument types and names, and even type definitions
>
> roughly how it should look like i described in that post month ago
>
> i could do it myself as i got my own assembler - and maybe i should becouse if someone else would do that before there is a chance it will do it more bad than i (im not in hurry hovever and it can take me 10 years becouse i got some other obligations and not code to much recent years)
and how it would work, simply when compiling with -l"dllname" coimpiler would terat such dll section contents as tidays header... this has this disadvantage you need binary dll to compile into it buts its analog to just have a header, one also could wrote extern declarations by hand and compile without it
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 16:38 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <b9f17d28-f1ff-42fb-92e7-53b01782b7ffn@googlegroups.com> |
| In reply to | #172052 |
piątek, 11 sierpnia 2023 o 01:06:37 UTC+2 fir napisał(a):
>
> call ("green.fire.dll"->SetupWindow5)
>
> then it really is something like call (0x00401034) which pointer is in import section of loaded exe
> (whuch was loaded under say 0x00400000) and its value points to sax 0x0050cccc where code oof SetpuWindow5 of dll was loaded
>
more precisely values are for example
Building imports :
912 (0x0390) bytes stored in import section
green.fire.dll
frame_size_x (0x00402354)
frame_size_y (0x00402358)
ClearFrameData (0x0040235c)
frame_bitmap (0x00402360)
RegisterMouseMove (0x00402364)
RegisterLeftMouseButtonDown (0x00402368)
RegisterRightMouseButtonDown (0x0040236c)
RegisterKeyDown (0x00402370)
RegisterOnResize (0x00402374)
RegisterRunFrame (0x00402378)
SetSleepValue (0x0040237c)
SetupWindow3 (0x00402380)
msvcrt.dll
printf (0x00402388)
as as far as i knoe exe is loaded typically under 0x00400000
in my case code first than imports then data (static arrays) ..dll afait must be loaded
somewhere 0x004xxxxx - 0x7ffxxxxx, also heap is probably there
in fact it would be worth to print out thet pointers
exe code may use fixed adresses of jumps and data acces as its just loaded under known adress, dlls must provide fixups as dll must be loaded under varoius adress and need to apply fixups then
(old ollydbg debbugger for windows shows nice info with that data)
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 16:58 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <988dd185-cb9d-4d8e-b006-92a7cbf4c63en@googlegroups.com> |
| In reply to | #172054 |
piątek, 11 sierpnia 2023 o 01:39:12 UTC+2 fir napisał(a): > (old ollydbg debbugger for windows shows nice info with that data) olly for example shows that nice memory map (when attached to my game protorype codenamed tusk (turnbased space shooter) its nice coz it shows what dlls are loaded and where, it also shows which section occupies how many bytes - the biggest are .bbs it is zero inicialized static arrays..it shows for example i do not much optymalised my programs in this aspect (which is kinda bug as in many files i just declated sbig tatic arrays just to be handy, but its probbaly better to use realloc seeds and not to go with that static arrays to much (technically its still no harm as thetre unused and not even physical memory is mapped but logical areas are wasted) Memory map Address Size (Decimal) Owner Section Contains Type Access Initial Mapped as 00010000 00001000 (4096.) 00010000 (itself) Priv 00021004 RW RW 00020000 00001000 (4096.) 00020000 (itself) Priv 00021004 RW RW 0022C000 00001000 (4096.) 00030000 Priv 00021104 RW Guar RW 0022D000 00003000 (12288.) 00030000 stack of main thread Priv 00021104 RW Guar RW 00230000 00003000 (12288.) 00230000 (itself) Map 00041002 R R 00240000 00020000 (131072.) 00240000 (itself) Priv 00021004 RW RW 00340000 00006000 (24576.) 00340000 (itself) Priv 00021004 RW RW 00350000 00003000 (12288.) 00350000 (itself) Map 00041004 RW RW 00360000 00016000 (90112.) 00360000 (itself) Map 00041002 R R \Device\HarddiskVolume1\WINDOWS\system32\unicode.nls 00380000 00041000 (266240.) 00380000 (itself) Map 00041002 R R \Device\HarddiskVolume1\WINDOWS\system32\locale.nls 003D0000 00006000 (24576.) 003D0000 (itself) Map 00041002 R R \Device\HarddiskVolume1\WINDOWS\system32\sorttbls.nls 003E0000 00001000 (4096.) WS2_32 003E0000 (itself) PE header Imag 01001002 R RWE 003E1000 00013000 (77824.) WS2_32 003E0000 .text code,imports,exports Imag 01001002 R RWE 003F4000 00001000 (4096.) WS2_32 003E0000 .data data Imag 01001002 R RWE 003F5000 00001000 (4096.) WS2_32 003E0000 .rsrc resources Imag 01001002 R RWE 003F6000 00001000 (4096.) WS2_32 003E0000 .reloc relocations Imag 01001002 R RWE 00400000 00001000 (4096.) tusk 00400000 (itself) PE header Imag 01001002 R RWE 00401000 00030000 (196608.) tusk 00400000 .text code Imag 01001002 R RWE 00431000 00001000 (4096.) tusk 00400000 .data data Imag 01001002 R RWE 00432000 00004000 (16384.) tusk 00400000 .rdata Imag 01001002 R RWE 00436000 00001000 (4096.) tusk 00400000 .eh_fram Imag 01001002 R RWE 00437000 01966000 (26632192.) tusk 00400000 .bss Imag 01001002 R RWE 01D9D000 00001000 (4096.) tusk 00400000 .idata imports Imag 01001002 R RWE 01D9E000 00001000 (4096.) tusk 00400000 .CRT Imag 01001002 R RWE 01D9F000 00001000 (4096.) tusk 00400000 .tls Imag 01001002 R RWE 01DA0000 00004000 (16384.) tusk 00400000 .rsrc resources Imag 01001002 R RWE 01DB0000 00041000 (266240.) 01DB0000 (itself) Map 00041002 R R \Device\HarddiskVolume1\WINDOWS\system32\sortkey.nls 01E00000 00041000 (266240.) 01E00000 (itself) Map 00041002 R R 01E50000 00001000 (4096.) WS2HELP 01E50000 (itself) PE header Imag 01001002 R RWE 01E51000 00004000 (16384.) WS2HELP 01E50000 .text code,imports,exports Imag 01001002 R RWE 01E55000 00001000 (4096.) WS2HELP 01E50000 .data data Imag 01001002 R RWE 01E56000 00001000 (4096.) WS2HELP 01E50000 .rsrc resources Imag 01001002 R RWE 01E57000 00001000 (4096.) WS2HELP 01E50000 .reloc relocations Imag 01001002 R RWE 01E60000 00004000 (16384.) 01E60000 (itself) Map 00041020 R E R E 01F20000 00002000 (8192.) 01E60000 Map 00041020 R E R E 01F30000 00103000 (1060864.) 01F30000 (itself) Map 00041002 R R 02040000 00001000 (4096.) 02040000 (itself) Priv 00021004 RW RW 02050000 00073000 (471040.) 02050000 (itself) Map 00041020 R E R E 02350000 00001000 (4096.) 02350000 (itself) Priv 00021004 RW RW 02360000 00004000 (16384.) 02360000 (itself) Priv 00021004 RW RW 02370000 00003000 (12288.) 02370000 (itself) Map 00041002 R R \Device\HarddiskVolume1\WINDOWS\system32\ctype.nls 02380000 00001000 (4096.) 02380000 (itself) Priv 00021004 RW RW 02400000 00004000 (16384.) 02400000 (itself) Priv 00021004 RW RW 02410000 00002000 (8192.) 02410000 (itself) Map 00041002 R R 02420000 00001000 (4096.) 02420000 (itself) Map 00041004 RW RW 02430000 00002000 (8192.) 02430000 (itself) Map 00041002 R R 02440000 00003000 (12288.) 02440000 (itself) Priv 00021004 RW RW 02480000 00011000 (69632.) 02480000 (itself) Map 00041002 R R \Device\HarddiskVolume1\WINDOWS\system32\c_1252.nls 024AE000 00001000 (4096.) 024A0000 Priv 00021104 RW Guar RW 024AF000 00001000 (4096.) 024A0000 stack of thread 0000 Priv 00021104 RW Guar RW 024B0000 00002000 (8192.) 024B0000 (itself) Map 00041002 R R 024C0000 0022C000 (2277376.) 024C0000 (itself) Priv 00021004 RW RW 026F0000 00040000 (262144.) 026F0000 (itself) Map 00041002 R R 02730000 00100000 (1048576.) 02730000 (itself) Priv 00021004 RW RW 02A2E000 00001000 (4096.) 02830000 Priv 00021104 RW Guar RW 02A2F000 00001000 (4096.) 02830000 stack of thread 0000 Priv 00021104 RW Guar RW 02C2D000 00001000 (4096.) 02A30000 Priv 00021104 RW Guar RW 02C2E000 00002000 (8192.) 02A30000 stack of thread 0000 Priv 00021104 RW Guar RW 5D520000 00001000 (4096.) COMCTL32 5D520000 (itself) PE header Imag 01001002 R RWE 5D521000 00071000 (462848.) COMCTL32 5D520000 .text code,imports,exports Imag 01001002 R RWE 5D592000 00003000 (12288.) COMCTL32 5D520000 .data data Imag 01001002 R RWE 5D595000 00020000 (131072.) COMCTL32 5D520000 .rsrc resources Imag 01001002 R RWE 5D5B5000 00005000 (20480.) COMCTL32 5D520000 .reloc relocations Imag 01001002 R RWE 64840000 00001000 (4096.) green_fi 64840000 (itself) PE header Imag 01001002 R RWE 64841000 00044000 (278528.) green_fi 64840000 .text code Imag 01001002 R RWE 64885000 00026000 (155648.) green_fi 64840000 .data data Imag 01001002 R RWE 648AB000 00002000 (8192.) green_fi 64840000 .rdata Imag 01001002 R RWE 648AD000 00001000 (4096.) green_fi 64840000 .eh_fram Imag 01001002 R RWE 648AE000 0DDC4000 (232538112.) green_fi 64840000 .bss Imag 01001002 R RWE 72672000 00004000 (16384.) green_fi 64840000 .edata exports Imag 01001002 R RWE 72676000 00002000 (8192.) green_fi 64840000 .idata imports Imag 01001002 R RWE 72678000 00001000 (4096.) green_fi 64840000 .CRT Imag 01001002 R RWE 72679000 00001000 (4096.) green_fi 64840000 .tls Imag 01001002 R RWE 7267A000 00001000 (4096.) green_fi 64840000 .rsrc resources Imag 01001002 R RWE 7267B000 00004000 (16384.) green_fi 64840000 .reloc relocations Imag 01001002 R RWE 72CA0000 00001000 (4096.) msacm32 72CA0000 (itself) PE header Imag 01001002 R RWE 72CA1000 00003000 (12288.) msacm32 72CA0000 .text code,imports,exports Imag 01001002 R RWE 72CA4000 00001000 (4096.) msacm32 72CA0000 .data data Imag 01001002 R RWE 72CA5000 00002000 (8192.) msacm32 72CA0000 .rsrc resources Imag 01001002 R RWE 72CA7000 00001000 (4096.) msacm32 72CA0000 .reloc relocations Imag 01001002 R RWE 72CB0000 00001000 (4096.) wdmaud 72CB0000 (itself) PE header Imag 01001002 R RWE 72CB1000 00005000 (20480.) wdmaud 72CB0000 .text code,imports,exports Imag 01001002 R RWE 72CB6000 00001000 (4096.) wdmaud 72CB0000 .data data Imag 01001002 R RWE 72CB7000 00001000 (4096.) wdmaud 72CB0000 .rsrc resources Imag 01001002 R RWE 72CB8000 00001000 (4096.) wdmaud 72CB0000 .reloc relocations Imag 01001002 R RWE 76380000 00001000 (4096.) COMDLG32 76380000 (itself) PE header Imag 01001002 R RWE 76381000 00030000 (196608.) COMDLG32 76380000 .text code,imports,exports Imag 01001002 R RWE 763B1000 00004000 (16384.) COMDLG32 76380000 .data data Imag 01001002 R RWE 763B5000 00011000 (69632.) COMDLG32 76380000 .rsrc resources Imag 01001002 R RWE 763C6000 00003000 (12288.) COMDLG32 76380000 .reloc relocations Imag 01001002 R RWE 76B20000 00001000 (4096.) WINMM 76B20000 (itself) PE header Imag 01001002 R RWE 76B21000 0001F000 (126976.) WINMM 76B20000 .text code,imports,exports Imag 01001002 R RWE 76B40000 00002000 (8192.) WINMM 76B20000 .data data Imag 01001002 R RWE 76B42000 0000A000 (40960.) WINMM 76B20000 .rsrc resources Imag 01001002 R RWE 76B4C000 00002000 (8192.) WINMM 76B20000 .reloc relocations Imag 01001002 R RWE 76BE0000 00001000 (4096.) PSAPI 76BE0000 (itself) PE header Imag 01001002 R RWE 76BE1000 00004000 (16384.) PSAPI 76BE0000 .text code,imports,exports Imag 01001002 R RWE 76BE5000 00004000 (16384.) PSAPI 76BE0000 .data data Imag 01001002 R RWE 76BE9000 00001000 (4096.) PSAPI 76BE0000 .rsrc resources Imag 01001002 R RWE 76BEA000 00001000 (4096.) PSAPI 76BE0000 .reloc relocations Imag 01001002 R RWE 76C20000 00001000 (4096.) WINTRUST 76C20000 (itself) PE header Imag 01001002 R RWE 76C21000 00029000 (167936.) WINTRUST 76C20000 .text code,imports,exports Imag 01001002 R RWE 76C4A000 00001000 (4096.) WINTRUST 76C20000 .data data Imag 01001002 R RWE 76C4B000 00001000 (4096.) WINTRUST 76C20000 .rsrc resources Imag 01001002 R RWE 76C4C000 00002000 (8192.) WINTRUST 76C20000 .reloc relocations Imag 01001002 R RWE 76C80000 00001000 (4096.) IMAGEHLP 76C80000 (itself) PE header Imag 01001002 R RWE 76C81000 00022000 (139264.) IMAGEHLP 76C80000 .text code,imports,exports Imag 01001002 R RWE 76CA3000 00002000 (8192.) IMAGEHLP 76C80000 .data data Imag 01001002 R RWE 76CA5000 00001000 (4096.) IMAGEHLP 76C80000 .rsrc resources Imag 01001002 R RWE 76CA6000 00002000 (8192.) IMAGEHLP 76C80000 .reloc relocations Imag 01001002 R RWE 773C0000 00001000 (4096.) comctl_1 773C0000 (itself) PE header Imag 01001002 R RWE 773C1000 00091000 (593920.) comctl_1 773C0000 .text code,imports,exports Imag 01001002 R RWE 77452000 00001000 (4096.) comctl_1 773C0000 .data data Imag 01001002 R RWE 77453000 0006A000 (434176.) comctl_1 773C0000 .rsrc resources Imag 01001002 R RWE 774BD000 00006000 (24576.) comctl_1 773C0000 .reloc relocations Imag 01001002 R RWE 77A70000 00001000 (4096.) CRYPT32 77A70000 (itself) PE header Imag 01001002 R RWE 77A71000 00085000 (544768.) CRYPT32 77A70000 .text code,imports,exports Imag 01001002 R RWE 77AF6000 00003000 (12288.) CRYPT32 77A70000 .data data Imag 01001002 R RWE 77AF9000 00008000 (32768.) CRYPT32 77A70000 .rsrc resources Imag 01001002 R RWE 77B01000 00005000 (20480.) CRYPT32 77A70000 .reloc relocations Imag 01001002 R RWE 77B10000 00001000 (4096.) MSASN1 77B10000 (itself) PE header Imag 01001002 R RWE 77B11000 0000E000 (57344.) MSASN1 77B10000 .text code,imports,exports Imag 01001002 R RWE 77B1F000 00001000 (4096.) MSASN1 77B10000 .data data Imag 01001002 R RWE 77B20000 00001000 (4096.) MSASN1 77B10000 .rsrc resources Imag 01001002 R RWE 77B21000 00001000 (4096.) MSASN1 77B10000 .reloc relocations Imag 01001002 R RWE 77BC0000 00001000 (4096.) midimap 77BC0000 (itself) PE header Imag 01001002 R RWE 77BC1000 00003000 (12288.) midimap 77BC0000 .text code,imports,exports Imag 01001002 R RWE 77BC4000 00001000 (4096.) midimap 77BC0000 .data data Imag 01001002 R RWE 77BC5000 00001000 (4096.) midimap 77BC0000 .rsrc resources Imag 01001002 R RWE 77BC6000 00001000 (4096.) midimap 77BC0000 .reloc relocations Imag 01001002 R RWE 77BD0000 00001000 (4096.) MSACM3_1 77BD0000 (itself) PE header Imag 01001002 R RWE 77BD1000 00010000 (65536.) MSACM3_1 77BD0000 .text code,imports,exports Imag 01001002 R RWE 77BE1000 00001000 (4096.) MSACM3_1 77BD0000 .data data Imag 01001002 R RWE 77BE2000 00002000 (8192.) MSACM3_1 77BD0000 .rsrc resources Imag 01001002 R RWE 77BE4000 00001000 (4096.) MSACM3_1 77BD0000 .reloc relocations Imag 01001002 R RWE 77C00000 00001000 (4096.) msvcrt 77C00000 (itself) PE header Imag 01001002 R RWE 77C01000 0004C000 (311296.) msvcrt 77C00000 .text code,imports,exports Imag 01001002 R RWE 77C4D000 00007000 (28672.) msvcrt 77C00000 .data data Imag 01001002 R RWE 77C54000 00001000 (4096.) msvcrt 77C00000 .rsrc resources Imag 01001002 R RWE 77C55000 00003000 (12288.) msvcrt 77C00000 .reloc relocations Imag 01001002 R RWE 77DC0000 00001000 (4096.) ADVAPI32 77DC0000 (itself) PE header Imag 01001002 R RWE 77DC1000 00075000 (479232.) ADVAPI32 77DC0000 .text code,imports,exports Imag 01001002 R RWE 77E36000 00005000 (20480.) ADVAPI32 77DC0000 .data data Imag 01001002 R RWE 77E3B000 0002C000 (180224.) ADVAPI32 77DC0000 .rsrc resources Imag 01001002 R RWE 77E67000 00005000 (20480.) ADVAPI32 77DC0000 .reloc relocations Imag 01001002 R RWE 77E70000 00001000 (4096.) RPCRT4 77E70000 (itself) PE header Imag 01001002 R RWE 77E71000 00083000 (536576.) RPCRT4 77E70000 .text code,imports,exports Imag 01001002 R RWE 77EF4000 00007000 (28672.) RPCRT4 77E70000 .orpc code Imag 01001002 R RWE 77EFB000 00001000 (4096.) RPCRT4 77E70000 .data data Imag 01001002 R RWE 77EFC000 00001000 (4096.) RPCRT4 77E70000 .rsrc resources Imag 01001002 R RWE 77EFD000 00005000 (20480.) RPCRT4 77E70000 .reloc relocations Imag 01001002 R RWE 77F10000 00001000 (4096.) GDI32 77F10000 (itself) PE header Imag 01001002 R RWE 77F11000 00043000 (274432.) GDI32 77F10000 .text code,imports,exports Imag 01001002 R RWE 77F54000 00002000 (8192.) GDI32 77F10000 .data data Imag 01001002 R RWE 77F56000 00001000 (4096.) GDI32 77F10000 .rsrc resources Imag 01001002 R RWE 77F57000 00002000 (8192.) GDI32 77F10000 .reloc relocations Imag 01001002 R RWE 77F60000 00001000 (4096.) SHLWAPI 77F60000 (itself) PE header Imag 01001002 R RWE 77F61000 0006C000 (442368.) SHLWAPI 77F60000 .text code,imports,exports Imag 01001002 R RWE 77FCD000 00001000 (4096.) SHLWAPI 77F60000 .data data Imag 01001002 R RWE 77FCE000 00002000 (8192.) SHLWAPI 77F60000 .rsrc resources Imag 01001002 R RWE 77FD0000 00006000 (24576.) SHLWAPI 77F60000 .reloc relocations Imag 01001002 R RWE 77FE0000 00001000 (4096.) Secur32 77FE0000 (itself) PE header Imag 01001002 R RWE 77FE1000 0000D000 (53248.) Secur32 77FE0000 .text code,imports,exports Imag 01001002 R RWE 77FEE000 00001000 (4096.) Secur32 77FE0000 .data data Imag 01001002 R RWE 77FEF000 00001000 (4096.) Secur32 77FE0000 .rsrc resources Imag 01001002 R RWE 77FF0000 00001000 (4096.) Secur32 77FE0000 .reloc relocations Imag 01001002 R RWE 7C800000 00001000 (4096.) kernel32 7C800000 (itself) PE header Imag 01001002 R RWE 7C801000 00084000 (540672.) kernel32 7C800000 .text code,imports,exports Imag 01001002 R RWE 7C885000 00005000 (20480.) kernel32 7C800000 .data data Imag 01001002 R RWE 7C88A000 0006D000 (446464.) kernel32 7C800000 .rsrc resources Imag 01001002 R RWE 7C8F7000 00006000 (24576.) kernel32 7C800000 .reloc relocations Imag 01001002 R RWE 7C900000 00001000 (4096.) ntdll 7C900000 (itself) PE header Imag 01001002 R RWE 7C901000 0007A000 (499712.) ntdll 7C900000 .text code,exports Imag 01001002 R RWE 7C97B000 00005000 (20480.) ntdll 7C900000 .data data Imag 01001002 R RWE 7C980000 0002E000 (188416.) ntdll 7C900000 .rsrc resources Imag 01001002 R RWE 7C9AE000 00003000 (12288.) ntdll 7C900000 .reloc relocations Imag 01001002 R RWE 7C9C0000 00001000 (4096.) SHELL32 7C9C0000 (itself) PE header Imag 01001002 R RWE 7C9C1000 001FE000 (2088960.) SHELL32 7C9C0000 .text code,imports,exports Imag 01001002 R RWE 7CBBF000 0001D000 (118784.) SHELL32 7C9C0000 .data data Imag 01001002 R RWE 7CBDC000 005E7000 (6189056.) SHELL32 7C9C0000 .rsrc resources Imag 01001002 R RWE 7D1C3000 0001B000 (110592.) SHELL32 7C9C0000 .reloc relocations Imag 01001002 R RWE 7E360000 00001000 (4096.) USER32 7E360000 (itself) PE header Imag 01001002 R RWE 7E361000 00060000 (393216.) USER32 7E360000 .text code,imports,exports Imag 01001002 R RWE 7E3C1000 00002000 (8192.) USER32 7E360000 .data data Imag 01001002 R RWE 7E3C3000 0002B000 (176128.) USER32 7E360000 .rsrc resources Imag 01001002 R RWE 7E3EE000 00003000 (12288.) USER32 7E360000 .reloc relocations Imag 01001002 R RWE 7F6F0000 00007000 (28672.) 7F6F0000 (itself) Map 00041020 R E R E 7FFB0000 00024000 (147456.) 7FFB0000 (itself) Map 00041002 R R 7FFD9000 00001000 (4096.) 7FFD9000 (itself) Priv 00021004 RW RW 7FFDC000 00001000 (4096.) 7FFDC000 (itself) data block of thread Priv 00021004 RW RW 7FFDD000 00001000 (4096.) 7FFDD000 (itself) data block of thread Priv 00021004 RW RW 7FFDE000 00001000 (4096.) 7FFDE000 (itself) data block of thread Priv 00021004 RW RW 7FFDF000 00001000 (4096.) 7FFDF000 (itself) data block of main t Priv 00021004 RW RW 7FFE0000 00001000 (4096.) 7FFE0000 (itself) Priv 00021002 R R
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 18:43 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <fc180b44-6c59-4288-be42-d65ce34f5a51n@googlegroups.com> |
| In reply to | #172055 |
watching this map i dont know the details but roughly it seems - program begins at 4 MB below is 2 MB stack, dlls are putted down 2 GB and between program and dlls probably there is heap..some other regions are also mapped but i dont know what it is
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-11 01:30 +0100 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <ub3veb$icj5$1@dont-email.me> |
| In reply to | #172052 |
On 11/08/2023 00:06, fir wrote:
> piątek, 11 sierpnia 2023 o 00:17:57 UTC+2 Bart napisał(a):
>> On 10/08/2023 22:44, fir wrote:
>>> czwartek, 10 sierpnia 2023 o 20:16:49 UTC+2 Kaz Kylheku napisał(a):
>>>>
>>>> DLLs are lacking in some technology like symbol versioning, linking
>>>> in any direction (DLL cannot attach to symbols exported by executable)
>>>> and such. Plus the use of clunky .lib files taht SO's don't require,
>>>> and __decl(dllexport) and other cruft. (That pragma mechanism by
>>>> which a source file indicates a needed DLL doesn't need a .lib file
>>>> though, IIRC).
>>>>
>>>
>>> i dont remember as to this exe, though i remember i was testing it and
>>> those relative usage - when i was writing more than one dll was making
>>> some problems to me.. i dont remember hovever if you cant call
functions in exe
>>> though - problem was rather that when you want to compile dll using
other dll you need to have the other build (becouse compilaton readed
binary dll to check if symbols exist even if
>>> linking is rruntime - this is in fact stupid but this is a
consequence of fact that when
>>> you link to a symbol compilers dont know in which of dlls you want
to0 link it is,
>>> and it need to put not only symbols but their parent module names
in output) ..
>>> it is mighty stupid bcouse you cant compile code that uses the dll
that you dont really get
>>> (unles there is some way providing this info on symbold what is the
name of the
>>> parent module of them, __declspec(dllimport) are not a problem though
>>>
>>> it should be some other extension too like
>>>
>>> __something "green fire.dll" //import module name for given symbols
>>> {
>>> __declspec(dllimport) int foo(int a);
>>> __declspec(dllimport) float xx;
>>> }
>>>
>>> but i dont know if there is something like that
>>>
>>>
>>> but besides in practice there are no problems with dlls at least
when i use it
>>> is a breat with butter
>>>
>>> dlls are very likeable and i tell not a first time that if someone
coded in c on windows he must
>>> learn dlls becouse dlls are sorta part of practical c..and its real
nice part (ofc it lacks types
>>> encoded and call conventions which would allow to just get rid of
headers - check my thread/post on it)
>>>
>>> probably it would allow even normal c to get rid of headers as pif
everything would just work without headers people just could not include
them and tha wouldnt break codes
>> How would that work? To use a function exported from a DLL, you will
>> need a function signature, perhaps a set of usertypes, enums and
#defines.
>>
>> All the stuff that normally is provided by a header.
>>
>> Where would that information come from?
>>
>> (My own idea was for an interface info to be embedded inside the DLL,
>> and accessed by calling a special exported function. For C, that could
>> just return a string containing the normal header code.
>>
>> But it would need cooperation from the people creating the DLL (who
>> could be writing in any language, not C).
>>
>> And from C compilers to delve inside DLL files (and at an early stage
>> long before linking). Since C compilers can't even shake off
>> anachronisms like -lm and a.out, I can't see that happening.)
>>
>>
>>
>> My idea was for my own private use
> doi
> lern how PE format works coz it is really important - not mucnh
pleasant to read but important as hell
You really don't need to disect a DLL file to extract some data from it.
A regular interface will do.
For example, for a DLL that exports one function 'add()', add this extra
function:
char* header = "int add(int, int);\n";
char* getheader(void) { return header;}
and create a DLL like 'lib.dll'.
Now, in the compiler that wants to import functions from lib.dll, use
code like this:
#include <stdio.h>
#include <windows.h>
int main(void) {
void* handle;
char* (*fnptr)(void);
handle=LoadLibrary("lib.dll");
if (handle) {
fnptr=GetProcAddress(handle, "getheader");
if (fnptr)
printf("Header = %s\n", fnptr());
}
}
Calling getheader() returns the same string as including a header file
like 'lib.h'.
No need to be delving inside the PE format.
Actually, as written, that 'header' variable is exported also, so you
can directly access that, but I prefer to do it via a function.
And, PE is a terrible, terrible format. Only get into as last resort.
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 17:58 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <ac12cc42-c391-4628-9efa-91ac321e3852n@googlegroups.com> |
| In reply to | #172056 |
piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a):
> On 11/08/2023 00:06, fir wrote:
> > piątek, 11 sierpnia 2023 o 00:17:57 UTC+2 Bart napisał(a):
> >> On 10/08/2023 22:44, fir wrote:
> >>> czwartek, 10 sierpnia 2023 o 20:16:49 UTC+2 Kaz Kylheku napisał(a):
> >>>>
> >>>> DLLs are lacking in some technology like symbol versioning, linking
> >>>> in any direction (DLL cannot attach to symbols exported by executable)
> >>>> and such. Plus the use of clunky .lib files taht SO's don't require,
> >>>> and __decl(dllexport) and other cruft. (That pragma mechanism by
> >>>> which a source file indicates a needed DLL doesn't need a .lib file
> >>>> though, IIRC).
> >>>>
> >>>
> >>> i dont remember as to this exe, though i remember i was testing it and
> >>> those relative usage - when i was writing more than one dll was making
> >>> some problems to me.. i dont remember hovever if you cant call
> functions in exe
> >>> though - problem was rather that when you want to compile dll using
> other dll you need to have the other build (becouse compilaton readed
> binary dll to check if symbols exist even if
> >>> linking is rruntime - this is in fact stupid but this is a
> consequence of fact that when
> >>> you link to a symbol compilers dont know in which of dlls you want
> to0 link it is,
> >>> and it need to put not only symbols but their parent module names
> in output) ..
> >>> it is mighty stupid bcouse you cant compile code that uses the dll
> that you dont really get
> >>> (unles there is some way providing this info on symbold what is the
> name of the
> >>> parent module of them, __declspec(dllimport) are not a problem though
> >>>
> >>> it should be some other extension too like
> >>>
> >>> __something "green fire.dll" //import module name for given symbols
> >>> {
> >>> __declspec(dllimport) int foo(int a);
> >>> __declspec(dllimport) float xx;
> >>> }
> >>>
> >>> but i dont know if there is something like that
> >>>
> >>>
> >>> but besides in practice there are no problems with dlls at least
> when i use it
> >>> is a breat with butter
> >>>
> >>> dlls are very likeable and i tell not a first time that if someone
> coded in c on windows he must
> >>> learn dlls becouse dlls are sorta part of practical c..and its real
> nice part (ofc it lacks types
> >>> encoded and call conventions which would allow to just get rid of
> headers - check my thread/post on it)
> >>>
> >>> probably it would allow even normal c to get rid of headers as pif
> everything would just work without headers people just could not include
> them and tha wouldnt break codes
> >> How would that work? To use a function exported from a DLL, you will
> >> need a function signature, perhaps a set of usertypes, enums and
> #defines.
> >>
> >> All the stuff that normally is provided by a header.
> >>
> >> Where would that information come from?
> >>
> >> (My own idea was for an interface info to be embedded inside the DLL,
> >> and accessed by calling a special exported function. For C, that could
> >> just return a string containing the normal header code.
> >>
> >> But it would need cooperation from the people creating the DLL (who
> >> could be writing in any language, not C).
> >>
> >> And from C compilers to delve inside DLL files (and at an early stage
> >> long before linking). Since C compilers can't even shake off
> >> anachronisms like -lm and a.out, I can't see that happening.)
> >>
> >>
> >>
> >> My idea was for my own private use
> > doi
> > lern how PE format works coz it is really important - not mucnh
> pleasant to read but important as hell
> You really don't need to disect a DLL file to extract some data from it.
> A regular interface will do.
>
> For example, for a DLL that exports one function 'add()', add this extra
> function:
>
> char* header = "int add(int, int);\n";
> char* getheader(void) { return header;}
>
> and create a DLL like 'lib.dll'.
>
> Now, in the compiler that wants to import functions from lib.dll, use
> code like this:
>
> #include <stdio.h>
> #include <windows.h>
>
> int main(void) {
> void* handle;
> char* (*fnptr)(void);
>
> handle=LoadLibrary("lib.dll");
> if (handle) {
> fnptr=GetProcAddress(handle, "getheader");
> if (fnptr)
> printf("Header = %s\n", fnptr());
> }
> }
>
> Calling getheader() returns the same string as including a header file
> like 'lib.h'.
>
> No need to be delving inside the PE format.
>
> Actually, as written, that 'header' variable is exported also, so you
> can directly access that, but I prefer to do it via a function.
>
> And, PE is a terrible, terrible format. Only get into as last resort.
you cannot return c code as it must be binary level description language agnostic,
calling code is weird as it imo should be a normal format that you could open on other system then dll is run on
adding a section is normal way and is no specially hard, it is to do in few days (first functioning draft of it, but that would be most work)
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 07:03 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <246b0335-9eb8-492c-843a-62d280a27107n@googlegroups.com> |
| In reply to | #172057 |
piątek, 11 sierpnia 2023 o 02:58:49 UTC+2 fir napisał(a):
> piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a):
> > On 11/08/2023 00:06, fir wrote:
> > > piątek, 11 sierpnia 2023 o 00:17:57 UTC+2 Bart napisał(a):
> > >> On 10/08/2023 22:44, fir wrote:
> > >>> czwartek, 10 sierpnia 2023 o 20:16:49 UTC+2 Kaz Kylheku napisał(a):
> > >>>>
> > >>>> DLLs are lacking in some technology like symbol versioning, linking
> > >>>> in any direction (DLL cannot attach to symbols exported by executable)
> > >>>> and such. Plus the use of clunky .lib files taht SO's don't require,
> > >>>> and __decl(dllexport) and other cruft. (That pragma mechanism by
> > >>>> which a source file indicates a needed DLL doesn't need a .lib file
> > >>>> though, IIRC).
> > >>>>
> > >>>
> > >>> i dont remember as to this exe, though i remember i was testing it and
> > >>> those relative usage - when i was writing more than one dll was making
> > >>> some problems to me.. i dont remember hovever if you cant call
> > functions in exe
> > >>> though - problem was rather that when you want to compile dll using
> > other dll you need to have the other build (becouse compilaton readed
> > binary dll to check if symbols exist even if
> > >>> linking is rruntime - this is in fact stupid but this is a
> > consequence of fact that when
> > >>> you link to a symbol compilers dont know in which of dlls you want
> > to0 link it is,
> > >>> and it need to put not only symbols but their parent module names
> > in output) ..
> > >>> it is mighty stupid bcouse you cant compile code that uses the dll
> > that you dont really get
> > >>> (unles there is some way providing this info on symbold what is the
> > name of the
> > >>> parent module of them, __declspec(dllimport) are not a problem though
> > >>>
> > >>> it should be some other extension too like
> > >>>
> > >>> __something "green fire.dll" //import module name for given symbols
> > >>> {
> > >>> __declspec(dllimport) int foo(int a);
> > >>> __declspec(dllimport) float xx;
> > >>> }
> > >>>
> > >>> but i dont know if there is something like that
> > >>>
> > >>>
> > >>> but besides in practice there are no problems with dlls at least
> > when i use it
> > >>> is a breat with butter
> > >>>
> > >>> dlls are very likeable and i tell not a first time that if someone
> > coded in c on windows he must
> > >>> learn dlls becouse dlls are sorta part of practical c..and its real
> > nice part (ofc it lacks types
> > >>> encoded and call conventions which would allow to just get rid of
> > headers - check my thread/post on it)
> > >>>
> > >>> probably it would allow even normal c to get rid of headers as pif
> > everything would just work without headers people just could not include
> > them and tha wouldnt break codes
> > >> How would that work? To use a function exported from a DLL, you will
> > >> need a function signature, perhaps a set of usertypes, enums and
> > #defines.
> > >>
> > >> All the stuff that normally is provided by a header.
> > >>
> > >> Where would that information come from?
> > >>
> > >> (My own idea was for an interface info to be embedded inside the DLL,
> > >> and accessed by calling a special exported function. For C, that could
> > >> just return a string containing the normal header code.
> > >>
> > >> But it would need cooperation from the people creating the DLL (who
> > >> could be writing in any language, not C).
> > >>
> > >> And from C compilers to delve inside DLL files (and at an early stage
> > >> long before linking). Since C compilers can't even shake off
> > >> anachronisms like -lm and a.out, I can't see that happening.)
> > >>
> > >>
> > >>
> > >> My idea was for my own private use
> > > doi
> > > lern how PE format works coz it is really important - not mucnh
> > pleasant to read but important as hell
> > You really don't need to disect a DLL file to extract some data from it.
> > A regular interface will do.
> >
> > For example, for a DLL that exports one function 'add()', add this extra
> > function:
> >
> > char* header = "int add(int, int);\n";
> > char* getheader(void) { return header;}
> >
> > and create a DLL like 'lib.dll'.
> >
> > Now, in the compiler that wants to import functions from lib.dll, use
> > code like this:
> >
> > #include <stdio.h>
> > #include <windows.h>
> >
> > int main(void) {
> > void* handle;
> > char* (*fnptr)(void);
> >
> > handle=LoadLibrary("lib.dll");
> > if (handle) {
> > fnptr=GetProcAddress(handle, "getheader");
> > if (fnptr)
> > printf("Header = %s\n", fnptr());
> > }
> > }
> >
> > Calling getheader() returns the same string as including a header file
> > like 'lib.h'.
> >
> > No need to be delving inside the PE format.
> >
> > Actually, as written, that 'header' variable is exported also, so you
> > can directly access that, but I prefer to do it via a function.
> >
> > And, PE is a terrible, terrible format. Only get into as last resort.
> you cannot return c code as it must be binary level description language agnostic,
> calling code is weird as it imo should be a normal format that you could open on other system then dll is run on
> adding a section is normal way and is no specially hard, it is to do in few days (first functioning draft of it, but that would be most work)
in fact i must (should) slightly revrite the code in org-asm that builds import section, and i should add one that creates export section too, so maybe i will post detail on this how hard this is or rather is not, its a matter of one evening of easy code (except that little stress that youre not sure if you know enough well the windows demand and if it will run, as you must belive in 'gossips; on it)
i will be writing it soon so i may probably post on it though today i feel mighty sick (health problems)
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 07:28 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <abb8c99c-ebfb-4cd4-8e65-0e22667354d8n@googlegroups.com> |
| In reply to | #172057 |
piątek, 11 sierpnia 2023 o 02:58:49 UTC+2 fir napisał(a): > piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a): > > > > Calling getheader() returns the same string as including a header file > > like 'lib.h'. > > > > No need to be delving inside the PE format. > > > > Actually, as written, that 'header' variable is exported also, so you > > can directly access that, but I prefer to do it via a function. > > > > And, PE is a terrible, terrible format. Only get into as last resort. > you cannot return c code as it must be binary level description language agnostic, > calling code is weird as it imo should be a normal format that you could open on other system then dll is run on > adding a section is normal way and is no specially hard, it is to do in few days (first functioning draft of it, but that would be most work) besides if you would make compilers calling modules code to obtain headers you could make that compiler runy any of your code, playing songs for example - that would be funny maybe but... as i said it must be language agnostic type info do it canyt be header but some binary specification based on registered enumarations (conventions) accepted in binary abi world (see that post i wrote, it gives the description in more detail) https://groups.google.com/g/comp.lang.c/c/Qniawhtoc7s
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 07:47 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <d804a454-147d-470c-b1b5-6b23b1af0af5n@googlegroups.com> |
| In reply to | #172076 |
piątek, 11 sierpnia 2023 o 16:28:55 UTC+2 fir napisał(a): > > piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a): > > > > > > Actually, as written, that 'header' variable is exported also, so you > > > can directly access that, but I prefer to do it via a function. > > > the ide of kkeping this header as a string is not totally idiotic but its not optimal (its c specific and thus sorta weird, but theorethically might b used as some additions of what things look like now - but sort athis way you could add whoel source to dll as a string too) also to remember are efficincy things - i realized it maybe clearer writing on this swuare complexity that breakc computer down even for 1000 objects, and also those newline counts by fgets that took 300 ms: computers are still slow today.. reading 1 MB file or its part still takes about 1 ms (as to rank and saing not precisisely ofc depending on machine but say so) it is notable amount of time (as things stack) square algorithms breaks (begin to break) computers runtime in range 1k - 5k simple objects linear breaks (begin to break ) computer in range 1M simple objects... so when talking about runtime and fluid working the machines are still slow...and if you would add that headers, even if ram dont matter so much today the time is imo still bottleneck imo still hope the rems would be faster maybe as it would be really nice to have 10x as fast as today - say 100 GB/s or 1 TB/s) at home (this /s is misleading ofc coz important is what you got a t milisecond not on second..so 100 GB/s is 100 MB/ms which is nice but not so much cosmic amount as for today)
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 08:06 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <5c627e2a-f24e-4f06-9cc3-4b5cce223571n@googlegroups.com> |
| In reply to | #172079 |
piątek, 11 sierpnia 2023 o 16:47:48 UTC+2 fir napisał(a): > > square algorithms breaks (begin to break) computers runtime in range 1k - 5k simple objects linear breaks (begin to break ) computer in range 1M simple objects... it also dependants what one means simple - if simple means pixel it 'began to break' 1M or more but if soem means particles with more if logic etc or rasterized triangles (on CPU) it even began to break at 100k... (it then depends on machine as on old it may ba 100k on new it may be 600k) so i mean those talk is some kind of methafor/estimation but i would say linear things began to break a 1M (or seometimes even less) today (strictly on my old machine it began to break at 100-150k)
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-11 16:13 +0100 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <ub5j63$sqv6$1@dont-email.me> |
| In reply to | #172079 |
On 11/08/2023 15:47, fir wrote: > piątek, 11 sierpnia 2023 o 16:28:55 UTC+2 fir napisał(a): >>> piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a): >>>> >>>> Actually, as written, that 'header' variable is exported also, so you >>>> can directly access that, but I prefer to do it via a function. >>>> > the ide of kkeping this header as a string is not totally idiotic but its > not optimal (its c specific and thus sorta weird, but theorethically might b used as some additions of what things look like now - but sort athis way you could add whoel source to dll as a string too) > > also to remember are efficincy things - i realized it maybe clearer writing > on this swuare complexity that breakc computer down even for 1000 objects, and also those newline counts by fgets that took 300 ms: > > computers are still slow today.. reading 1 MB file or its part still takes about 1 ms > (as to rank and saing not precisisely ofc depending on machine but say so) > it is notable amount of time (as things stack) > > square algorithms breaks (begin to break) computers runtime in range 1k - 5k simple objects linear breaks (begin to break ) computer in range 1M simple objects... so when talking about runtime and fluid working the machines are still slow...and if you would add that headers, even if ram dont matter so much today > the time is imo still bottleneck imo > > still hope the rems would be faster maybe as it would be really nice to have 10x as fast as today - say 100 GB/s or 1 TB/s) at home (this /s is misleading ofc coz important is what you got a t milisecond not on second..so 100 GB/s is 100 MB/ms which is nice but not so much cosmic amount as for today) Your comment I first replied to was talking about DLLs, and getting rid of C headers. I assumed that was about headers needed to access libraries present in DLLs files. If talking about a new language however, and headers in general, then of course they can be eliminated. I haven't used headers (ie. separate declarations of shared functions etc) in my own languages for over a decade. But still, if I want to use a DLL that /someone else has written/, I need an interface to that library that I can then turn into bindings for my language. It is here, also, that binary, language-neutral, API information could be added to and accessed from a DLL file in the manner I suggested for C header info. Then an explicit file of API declarations, in whatever language, is not needed. Although something will be needed as docs so that you know how to use the library.
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 08:28 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <01d69c9e-2b53-4912-93dc-c6d098ef3d3fn@googlegroups.com> |
| In reply to | #172081 |
piątek, 11 sierpnia 2023 o 17:13:22 UTC+2 Bart napisał(a): > On 11/08/2023 15:47, fir wrote: > > piątek, 11 sierpnia 2023 o 16:28:55 UTC+2 fir napisał(a): > >>> piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a): > >>>> > >>>> Actually, as written, that 'header' variable is exported also, so you > >>>> can directly access that, but I prefer to do it via a function. > >>>> > > the ide of kkeping this header as a string is not totally idiotic but its > > not optimal (its c specific and thus sorta weird, but theorethically might b used as some additions of what things look like now - but sort athis way you could add whoel source to dll as a string too) > > > > also to remember are efficincy things - i realized it maybe clearer writing > > on this swuare complexity that breakc computer down even for 1000 objects, and also those newline counts by fgets that took 300 ms: > > > > computers are still slow today.. reading 1 MB file or its part still takes about 1 ms > > (as to rank and saing not precisisely ofc depending on machine but say so) > > it is notable amount of time (as things stack) > > > > square algorithms breaks (begin to break) computers runtime in range 1k - 5k simple objects linear breaks (begin to break ) computer in range 1M simple objects... so when talking about runtime and fluid working the machines are still slow...and if you would add that headers, even if ram dont matter so much today > > the time is imo still bottleneck imo > > > > still hope the rems would be faster maybe as it would be really nice to have 10x as fast as today - say 100 GB/s or 1 TB/s) at home (this /s is misleading ofc coz important is what you got a t milisecond not on second..so 100 GB/s is 100 MB/ms which is nice but not so much cosmic amount as for today) > Your comment I first replied to was talking about DLLs, and getting rid > of C headers. > > I assumed that was about headers needed to access libraries present in > DLLs files. > > If talking about a new language however, and headers in general, then of > course they can be eliminated. > > I haven't used headers (ie. separate declarations of shared functions > etc) in my own languages for over a decade. > > But still, if I want to use a DLL that /someone else has written/, I > need an interface to that library that I can then turn into bindings for > my language. > > It is here, also, that binary, language-neutral, API information could > be added to and accessed from a DLL file in the manner I suggested for C > header info. > > Then an explicit file of API declarations, in whatever language, is not > needed. Although something will be needed as docs so that you know how > to use the library. i wouldnt say i say on new languages i just say on dll's as they are - they just contain symbol names , and they at least should contain yet calling convention and at least input argument sizes or something but more better argument list and its types and prefereably even names, and yet preferably even new type definitions encoded , and even more info it cant be c declarations, it must be language agnostic - but is no problem tod efine this, you simoply need to define lists of namens and enums (liek list of enums with calling convention, list of enums for predefinde types, like int32 int64 float double (and things liek that) (if float is used in ABI at alla as i dont remember if it is not all doubles) etc better realize it cant be c source header strings couse it cant, it must be binary, enum based convention its hovever needed so its kinda obvious to say it will be defined and used, maybe i will define it myself when i will be shipping furia compiler more (i got only about half of it written and as i got other things to do it will take me yet at least few years assuming nothing much bad heppen at all)
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 08:37 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <905d2517-1fa9-4e0a-aaeb-2d35bd1cea9bn@googlegroups.com> |
| In reply to | #172082 |
piątek, 11 sierpnia 2023 o 17:28:41 UTC+2 fir napisał(a): > piątek, 11 sierpnia 2023 o 17:13:22 UTC+2 Bart napisał(a): > > On 11/08/2023 15:47, fir wrote: > > > piątek, 11 sierpnia 2023 o 16:28:55 UTC+2 fir napisał(a): > > >>> piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a): > > >>>> > > >>>> Actually, as written, that 'header' variable is exported also, so you > > >>>> can directly access that, but I prefer to do it via a function. > > >>>> > > > the ide of kkeping this header as a string is not totally idiotic but its > > > not optimal (its c specific and thus sorta weird, but theorethically might b used as some additions of what things look like now - but sort athis way you could add whoel source to dll as a string too) > > > > > > also to remember are efficincy things - i realized it maybe clearer writing > > > on this swuare complexity that breakc computer down even for 1000 objects, and also those newline counts by fgets that took 300 ms: > > > > > > computers are still slow today.. reading 1 MB file or its part still takes about 1 ms > > > (as to rank and saing not precisisely ofc depending on machine but say so) > > > it is notable amount of time (as things stack) > > > > > > square algorithms breaks (begin to break) computers runtime in range 1k - 5k simple objects linear breaks (begin to break ) computer in range 1M simple objects... so when talking about runtime and fluid working the machines are still slow...and if you would add that headers, even if ram dont matter so much today > > > the time is imo still bottleneck imo > > > > > > still hope the rems would be faster maybe as it would be really nice to have 10x as fast as today - say 100 GB/s or 1 TB/s) at home (this /s is misleading ofc coz important is what you got a t milisecond not on second..so 100 GB/s is 100 MB/ms which is nice but not so much cosmic amount as for today) > > Your comment I first replied to was talking about DLLs, and getting rid > > of C headers. > > > > I assumed that was about headers needed to access libraries present in > > DLLs files. > > > > If talking about a new language however, and headers in general, then of > > course they can be eliminated. > > > > I haven't used headers (ie. separate declarations of shared functions > > etc) in my own languages for over a decade. > > > > But still, if I want to use a DLL that /someone else has written/, I > > need an interface to that library that I can then turn into bindings for > > my language. > > > > It is here, also, that binary, language-neutral, API information could > > be added to and accessed from a DLL file in the manner I suggested for C > > header info. > > > > Then an explicit file of API declarations, in whatever language, is not > > needed. Although something will be needed as docs so that you know how > > to use the library. > i wouldnt say i say on new languages i just say on dll's as they are - > they just contain symbol names , and they at least should contain yet calling convention and at least input argument sizes or something but more better > argument list and its types and prefereably even names, and yet preferably even new type definitions encoded , and even more info > > it cant be c declarations, it must be language agnostic - but is no problem tod efine this, you simoply need to define lists of namens and enums (liek list of enums with calling convention, list of enums for predefinde types, like int32 int64 float double (and things liek that) (if float is used in ABI at alla as i dont remember if it is not all doubles) etc > i think it could be also named "binary header block" as it is kinde header buts its binary and dlls needs thet header block - so its seen as header is stupid thing it needs to be something liek that in dlls, but on binary level, it also need to take some bytes - skipping it is kinda hard optimisation, but its needed for convenience of programmers and general information also decreasing amount of of errors etc
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 08:46 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <688936d6-28c6-4d9e-a80f-fc8c620f68a3n@googlegroups.com> |
| In reply to | #172083 |
piątek, 11 sierpnia 2023 o 17:38:03 UTC+2 fir napisał(a): > > > i think it could be also named "binary header block" > > as it is kinde header buts its binary and dlls needs thet header block - > so its seen as header is stupid thing it needs to be something liek that in dlls, but on binary level, it also need to take some bytes - skipping it is kinda hard optimisation, but its needed for convenience of programmers and general information also decreasing amount of of errors etc as far as i remembet in dlls there is also an option to skip list of names in dll saving a space (say if dll kas few hunderds of symbols and each have on average 15 bytes it saves few kilobytes) and use calling by ordinals, i mean table index - but fortunatelly most dlls dont use it afaik... as this would also be optimisation and obfuscation thsi way i hope peopel would not skip binary header block too, having an option to delete header block and lefting only names or skiping both and lefting ordinals only
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 08:58 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <d2d71b93-8a5c-4d04-97aa-ed62c0f3a617n@googlegroups.com> |
| In reply to | #172086 |
piątek, 11 sierpnia 2023 o 17:46:41 UTC+2 fir napisał(a): > piątek, 11 sierpnia 2023 o 17:38:03 UTC+2 fir napisał(a): > > > > > i think it could be also named "binary header block" > > > > as it is kinde header buts its binary and dlls needs thet header block - > > so its seen as header is stupid thing it needs to be something liek that in dlls, but on binary level, it also need to take some bytes - skipping it is kinda hard optimisation, but its needed for convenience of programmers and general information also decreasing amount of of errors etc > as far as i remembet in dlls there is also an option to skip list of names in dll > saving a space (say if dll kas few hunderds of symbols and each have on average 15 bytes it saves few kilobytes) and use calling by ordinals, i mean table > index - but fortunatelly most dlls dont use it afaik... as this would also be optimisation and obfuscation > > > thsi way i hope peopel would not skip binary header block too, having an option to delete header block and lefting only names or skiping both and lefting ordinals only even winapi system dlls has its not skiped and for example list of export names in kernel32.dll on windows xp in that dll is from 0x3f8e to 0x8728 - about 16 kb if im not wrong
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-11 09:52 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <5a5cf9e2-d77e-4982-be19-027f10f99d8dn@googlegroups.com> |
| In reply to | #172079 |
piątek, 11 sierpnia 2023 o 16:47:48 UTC+2 fir napisał(a): > piątek, 11 sierpnia 2023 o 16:28:55 UTC+2 fir napisał(a): > > > piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a): > > > > > > > > Actually, as written, that 'header' variable is exported also, so you > > > > can directly access that, but I prefer to do it via a function. > > > > > the idea of keeping this header as a string is not totally idiotic but its > not optimal (its c specific and thus sorta weird, but theorethically might be used as some additions of what things look like now - but sort athis way you could add whole source to dll as a string too) > i could also heep not only a source as a string but a whoel compiler inside, in todays times when dlls like about 1.5MB typically the full compiler + assembler would be in natural form 0.5 MB dll (full) but i think the compiler+assembler can be optimised for size to not take more than 200 KB still being in quality
[toc] | [prev] | [next] | [standalone]
| From | fir <profesor.fir@gmail.com> |
|---|---|
| Date | 2023-08-10 18:21 -0700 |
| Subject | Re: you think rust may *DE*throne c? |
| Message-ID | <bb1608de-81e2-451e-a13d-622d0453f644n@googlegroups.com> |
| In reply to | #172056 |
piątek, 11 sierpnia 2023 o 02:30:18 UTC+2 Bart napisał(a): > And, PE is a terrible, terrible format. Only get into as last resort. its somewhat bad/slightly terrible imo..could be simpler but binary formats itself are not much pleasant imo besides its close to internals and many hackers like this kind of internals (by jackers i rather mean 'internalists') i think if some understand what it need to contauin it shows it contains what need to contain (like code dump(block), data dump, importd, exports, reallocks and header containing information like cpu/os type and xection properties.. mainly this header could be simplified coz those sections ere needed)
[toc] | [prev] | [next] | [standalone]
Page 33 of 49 — ← Prev page 1 … 31 32 [33] 34 35 … 49 Next page →
Back to top | Article view | comp.lang.c
csiph-web