Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #70446 > unrolled thread
| Started by | woodbrian77@gmail.com |
|---|---|
| First post | 2019-12-13 21:28 -0800 |
| Last post | 2019-12-15 09:49 +0000 |
| Articles | 20 on this page of 309 — 26 participants |
Back to article view | Back to comp.lang.c++
Don't be fooled by cpp.sh woodbrian77@gmail.com - 2019-12-13 21:28 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-14 09:23 +0000
Re: Don't be fooled by cpp.sh Vir Campestris <vir.campestris@invalid.invalid> - 2019-12-14 17:19 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-14 09:54 -0800
Re: Don't be fooled by cpp.sh woodbrian77@gmail.com - 2019-12-14 12:00 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-14 13:51 -0800
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-14 22:19 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-14 16:13 -0800
Re: Don't be fooled by cpp.sh Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-12-15 15:35 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-14 22:17 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-14 16:03 -0800
Re: Don't be fooled by cpp.sh Ian Collins <ian-news@hotmail.com> - 2019-12-15 15:41 +1300
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-14 22:55 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-15 09:53 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-15 11:18 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-15 16:44 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-15 20:49 +0000
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-15 15:11 -0800
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-15 23:28 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-15 15:41 -0800
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-16 05:18 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-16 10:46 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-16 09:57 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-16 10:21 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-17 09:37 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-17 15:13 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-17 14:12 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-17 19:35 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-18 16:14 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-17 08:32 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-18 16:26 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-12-18 19:11 +0000
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-18 11:23 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-18 11:31 -0800
Re: Don't be fooled by cpp.sh Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-12-18 19:56 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-19 08:42 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-12-19 20:26 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-20 09:25 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-20 04:35 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-20 16:28 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-20 10:36 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-21 16:33 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-21 09:11 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-21 17:22 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-21 10:18 -0800
Re: Don't be fooled by cpp.sh Vir Campestris <vir.campestris@invalid.invalid> - 2019-12-21 21:21 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-21 14:30 -0800
Re: Don't be fooled by cpp.sh Vir Campestris <vir.campestris@invalid.invalid> - 2019-12-22 21:36 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-22 15:05 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-22 17:03 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibble@i42.removethisbit.co.uk> - 2019-12-22 17:46 +0000
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-22 18:07 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-23 16:23 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibble@i42.removethisbit.co.uk> - 2019-12-23 16:33 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-23 16:46 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-23 18:51 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-23 17:02 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-23 19:17 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-24 09:49 +0000
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-24 02:16 -0800
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-25 00:30 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-26 09:46 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-26 16:38 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-26 17:33 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-26 19:52 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-27 17:14 +0000
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-27 09:41 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-28 12:05 +0000
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-28 21:01 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-29 09:00 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-29 12:21 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-29 18:30 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-29 21:45 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-30 10:10 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-30 14:03 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-30 12:17 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-30 04:39 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-30 13:01 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-30 15:17 +0200
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-30 14:22 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-30 16:49 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-30 17:18 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-30 18:12 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-30 18:16 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-30 18:38 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-30 19:17 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-30 20:55 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 03:13 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 13:01 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 13:13 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 14:09 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 14:12 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 15:39 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 15:45 +0100
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-31 15:22 +0000
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 17:16 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 17:51 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 17:59 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 18:21 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 18:35 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 18:51 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 18:59 +0100
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-31 12:23 -0800
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-31 16:14 -0800
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-31 16:52 -0800
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-31 18:58 +0200
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 18:00 +0100
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-31 19:21 +0200
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 18:22 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 18:46 +0100
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-31 20:30 +0200
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 19:44 +0100
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 08:10 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-11 13:03 +0100
Re: Don't be fooled by cpp.sh Ian Collins <ian-news@hotmail.com> - 2020-01-12 07:50 +1300
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2020-01-11 11:55 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-11 23:59 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-01 23:04 +0100
Re: Don't be fooled by cpp.sh Richard Damon <Richard@Damon-Family.org> - 2020-01-04 20:04 -0500
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2020-01-05 13:36 +0100
Re: Don't be fooled by cpp.sh Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-01-06 18:39 +0000
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-31 16:16 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-31 17:01 -0800
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-01 17:34 +0200
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-01 23:09 +0100
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 03:29 +0100
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-30 19:37 -0800
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-31 11:19 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 13:14 +0100
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-31 16:06 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-30 05:39 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-30 16:39 +0100
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-31 09:25 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-31 12:00 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-31 16:10 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-31 16:42 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-01 09:07 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-01 15:48 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-02 09:24 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-02 12:02 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-02 10:52 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2020-01-02 13:27 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-02 16:45 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2020-01-02 16:55 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-02 17:24 +0000
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2020-01-02 18:30 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-03 09:40 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-02 22:58 +0100
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-02 22:28 -0500
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-02 22:56 -0500
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-02 22:20 -0500
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-03 14:53 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-03 17:22 +0100
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-04 12:45 +0000
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-03 09:01 -0800
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-01-03 10:29 -0800
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-03 21:05 -0500
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 08:46 -0800
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-01-10 09:51 -0800
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 14:59 -0800
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-31 19:06 +0200
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-31 14:06 +0200
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 13:38 +0100
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-31 16:13 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibble@i42.removethisbit.co.uk> - 2019-12-31 17:06 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-01 09:09 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-31 18:11 +0100
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-01 09:13 +0000
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2020-01-01 09:09 -0600
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-02 09:25 +0000
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2020-01-03 10:09 -0600
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-04 12:43 +0000
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2020-01-04 18:02 -0600
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-05 10:41 +0000
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2020-01-05 12:31 -0600
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-05 20:11 +0100
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2020-01-05 11:22 -0800
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2020-01-05 21:07 -0600
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-01-05 20:40 -0800
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2020-01-06 18:08 -0600
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-01-06 23:17 -0500
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-07 08:37 +0100
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 14:51 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-07 08:28 +0100
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 14:19 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-01 23:15 +0100
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-02 09:33 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2020-01-02 12:16 +0100
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-31 18:14 +0000
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-31 19:16 +0100
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-31 18:48 +0000
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-31 12:29 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-01 09:17 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-30 16:32 +0100
Re: Don't be fooled by cpp.sh Bo Persson <bo@bo-persson.se> - 2019-12-30 14:57 +0100
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-31 09:23 +0000
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-12-30 22:16 -0500
Re: Don't be fooled by cpp.sh Siri Cruise <chine.bleu@yahoo.com> - 2019-12-30 20:30 -0800
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 21:12 -0800
Re: Don't be fooled by cpp.sh Siri Cruise <chine.bleu@yahoo.com> - 2019-12-30 20:07 -0800
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-30 13:50 +0100
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2020-01-01 08:11 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2020-01-02 09:28 +0000
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 21:26 -0800
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-29 11:31 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-29 18:35 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibble@i42.removethisbit.co.uk> - 2019-12-29 18:40 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-30 10:12 +0000
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-30 14:10 +0100
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-29 12:11 -0800
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-29 22:20 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-30 01:23 -0800
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-30 15:54 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibble@i42.removethisbit.co.uk> - 2019-12-30 17:07 +0000
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-30 19:58 +0000
Re: Don't be fooled by cpp.sh Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-12-30 23:59 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-30 21:23 +0000
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-28 18:09 -0800
Re: Don't be fooled by cpp.sh Mr Flibble <flibble@i42.removethisbit.co.uk> - 2019-12-26 18:30 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-27 17:17 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-27 09:58 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-28 12:06 +0000
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-28 08:39 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.org - 2019-12-28 16:57 +0000
Re: Don't be fooled by cpp.sh Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2020-01-02 23:18 -0500
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2019-12-26 10:54 -0800
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-26 22:50 +0200
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-26 10:38 -0800
Re: Don't be fooled by cpp.sh woodbrian77@gmail.com - 2019-12-24 17:52 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-24 23:53 -0800
Re: Don't be fooled by cpp.sh woodbrian77@gmail.com - 2019-12-25 08:51 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-25 10:54 -0800
Re: Don't be fooled by cpp.sh woodbrian77@gmail.com - 2019-12-21 08:42 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-21 09:25 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-18 11:28 -0800
Re: Don't be fooled by cpp.sh Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-12-18 20:00 +0000
Re: Don't be fooled by cpp.sh Paavo Helde <myfirstname@osa.pri.ee> - 2019-12-18 22:12 +0200
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-19 08:47 +0000
Re: Don't be fooled by cpp.sh Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-30 14:03 +0100
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-18 09:47 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-18 11:49 -0800
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-18 12:05 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-18 12:19 -0800
Re: Don't be fooled by cpp.sh Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-12-16 21:13 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-17 09:38 +0000
Re: Don't be fooled by cpp.sh Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-12-17 09:14 +0000
Re: Don't be fooled by cpp.sh Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-12-17 17:50 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 09:35 +0100
Re: Don't be fooled by cpp.sh Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-12-15 20:48 +0000
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-16 09:55 +0000
Re: Don't be fooled by cpp.sh Melzzzzz <Melzzzzz@zzzzz.com> - 2019-12-15 11:12 +0000
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-15 06:53 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-15 16:48 +0000
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-15 09:10 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-15 18:33 +0000
Re: Don't be fooled by cpp.sh Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-12-15 19:29 +0000
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-12-15 23:38 -0500
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-15 21:23 -0800
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-15 21:36 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-15 21:43 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 09:44 +0100
Re: Don't be fooled by cpp.sh Bart <bc@freeuk.com> - 2019-12-16 12:10 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 16:21 +0100
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2019-12-16 10:54 -0600
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2019-12-16 10:47 -0800
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-16 11:19 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 21:15 +0100
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2019-12-16 22:23 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-17 09:31 +0100
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2019-12-16 23:23 -0600
Re: Don't be fooled by cpp.sh Vir Campestris <vir.campestris@invalid.invalid> - 2019-12-16 21:45 +0000
Re: Don't be fooled by cpp.sh Robert Wessel <robertwessel2@yahoo.com> - 2019-12-16 23:20 -0600
Re: Don't be fooled by cpp.sh Vir Campestris <vir.campestris@invalid.invalid> - 2019-12-17 21:56 +0000
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-16 22:06 -0800
Re: Don't be fooled by cpp.sh "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2019-12-16 19:42 -0800
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-16 11:56 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 21:18 +0100
Re: Don't be fooled by cpp.sh Bart <bc@freeuk.com> - 2019-12-16 21:03 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-17 00:04 +0100
Re: Don't be fooled by cpp.sh Bart <bc@freeuk.com> - 2019-12-17 01:06 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-17 14:51 +0100
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-12-16 07:25 -0500
Re: Don't be fooled by cpp.sh Bo Persson <bo@bo-persson.se> - 2019-12-16 14:13 +0100
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 16:32 +0100
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2019-12-16 10:52 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 21:24 +0100
Re: Don't be fooled by cpp.sh Öö Tiib <ootiib@hot.ee> - 2019-12-16 10:56 -0800
Re: Don't be fooled by cpp.sh Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-12-16 20:45 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-16 22:00 +0100
Re: Don't be fooled by cpp.sh Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-12-17 04:07 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-17 15:00 +0100
Re: Don't be fooled by cpp.sh Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-12-17 14:44 +0000
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-17 15:54 +0100
Re: Don't be fooled by cpp.sh Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-12-17 15:52 +0000
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2019-12-17 11:51 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-17 22:10 +0100
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2019-12-17 22:08 -0800
Re: Don't be fooled by cpp.sh David Brown <david.brown@hesbynett.no> - 2019-12-18 08:56 +0100
Re: Don't be fooled by cpp.sh Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-01-10 08:29 -0800
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-12-17 23:55 -0500
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-18 09:36 -0800
Re: Don't be fooled by cpp.sh Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2019-12-16 22:29 -0800
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-12-16 22:40 -0500
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-12-16 07:17 -0500
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-15 21:24 -0800
Re: Don't be fooled by cpp.sh Bo Persson <bo@bo-persson.se> - 2019-12-16 12:13 +0100
Re: Don't be fooled by cpp.sh James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-12-16 07:44 -0500
Re: Don't be fooled by cpp.sh Daniel <danielaparker@gmail.com> - 2019-12-16 18:53 -0800
Re: Don't be fooled by cpp.sh boltar@nowhere.co.uk - 2019-12-15 09:49 +0000
Page 13 of 16 — ← Prev page 1 … 11 12 [13] 14 15 16 Next page →
| From | Öö Tiib <ootiib@hot.ee> |
|---|---|
| Date | 2019-12-18 11:49 -0800 |
| Message-ID | <58bf0944-d907-4c4b-a5d6-b77bba98a9b5@googlegroups.com> |
| In reply to | #70559 |
On Wednesday, 18 December 2019 19:47:14 UTC+2, Daniel wrote: > On Monday, December 16, 2019 at 1:21:40 PM UTC-5, Öö Tiib wrote: > > > Union is > > rather good performance optimization in decent hands, variant is a easy > > to use reliable union, and optional is a variant between value and > > nothing. So "purist" who can wield such trivial tools typically > > wins such a sorry "latitudinarians" who can't. > > optional has a pleasing interface, variant (in my opinion :)) less so. > > I experimented with providing a non-throwing alternative interface with > optional, but value and nothing aren't usually the states that you want, > rather value and error condition. Variant of Value,Failure1,Failure2 etc. is better to use as "Fallible".
[toc] | [prev] | [next] | [standalone]
| From | Daniel <danielaparker@gmail.com> |
|---|---|
| Date | 2019-12-18 12:05 -0800 |
| Message-ID | <00f41501-e839-4367-b5f6-2f894c497060@googlegroups.com> |
| In reply to | #70565 |
On Wednesday, December 18, 2019 at 2:49:37 PM UTC-5, Öö Tiib wrote: > On Wednesday, 18 December 2019 19:47:14 UTC+2, Daniel wrote: > > > > I experimented with providing a non-throwing alternative interface with > > optional, but value and nothing aren't usually the states that you want, > > rather value and error condition. > > Variant of Value,Failure1,Failure2 etc. is better to use as "Fallible". I thought you'd want to wrap that, as returning a variant would be an excruciatingly unfriendly interface, I think you'd want success() and value() and value_or(), as well as error_code or whatever. Daniel
[toc] | [prev] | [next] | [standalone]
| From | Öö Tiib <ootiib@hot.ee> |
|---|---|
| Date | 2019-12-18 12:19 -0800 |
| Message-ID | <6620258a-1f37-4c74-b546-29cadc000ac7@googlegroups.com> |
| In reply to | #70568 |
On Wednesday, 18 December 2019 22:05:18 UTC+2, Daniel wrote: > On Wednesday, December 18, 2019 at 2:49:37 PM UTC-5, Öö Tiib wrote: > > On Wednesday, 18 December 2019 19:47:14 UTC+2, Daniel wrote: > > > > > > I experimented with providing a non-throwing alternative interface with > > > optional, but value and nothing aren't usually the states that you want, > > > rather value and error condition. > > > > Variant of Value,Failure1,Failure2 etc. is better to use as "Fallible". > > I thought you'd want to wrap that, as returning a variant would be an > excruciatingly unfriendly interface, I think you'd want success() and value() > and value_or(), as well as error_code or whatever. Sure. That is great thing about C++. Convenience wrappers do not cause any performance losses and there are templates to automate making such convenience wrappers.
[toc] | [prev] | [next] | [standalone]
| From | Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> |
|---|---|
| Date | 2019-12-16 21:13 +0000 |
| Message-ID | <LrSJF.237$Rl7.190@fx06.dcg> |
| In reply to | #70498 |
On 16/12/2019 09:57, boltar@nowhere.co.uk wrote: > On Sun, 15 Dec 2019 15:41:18 -0800 (PST) > =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote: >> On Monday, 16 December 2019 01:28:14 UTC+2, Melzzzzz wrote: >>> On 2019-12-15, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote: >>>> On 12/15/2019 12:49 PM, Melzzzzz wrote: >>>>> On 2019-12-15, boltar@nowhere.co.uk <boltar@nowhere.co.uk> wrote: >>>>>> On Sun, 15 Dec 2019 11:18:43 GMT >>>>>> Melzzzzz <Melzzzzz@zzzzz.com> wrote: >>>>>>> On 2019-12-15, boltar@nowhere.co.uk <boltar@nowhere.co.uk> wrote: >>>> [...] >>>>>>> I use C only when necessary. When I have to. syntactic sugar of C++ is >>>>>>> what makes me use it. And I hate macros. >>>>>> >>>>>> If you do cross platform systems or network programming you have no >> choice but >>>>>> to use macros even in C++17. >>>>> >>>>> I can use macros but I don't write them... >>>> >>>> Have you ever experienced the Boost preprocessor macros? Iirc, it was >>>> the Chaos lib way back. Some hardcore shi%. >>>> >>>> ;^) >>> >>> Heh, I never used boost as well :P >> >> Last 15 years it has been almost inevitable to use something from boost >> in bigger project. Other way is to write precisely same thing yourself. >> Did you have myFilesystem, myOptional and myVariant before C++17? > > Optional and variant are both solutions looking for a problem. Just more noise > added to the language to keep a tiny number of purists happy. Wrong! You really are an ignorant twit. /Flibble -- "Snakes didn't evolve, instead talking snakes with legs changed into snakes." - Rick C. Hodgin “You won’t burn in hell. But be nice anyway.” – Ricky Gervais “I see Atheists are fighting and killing each other again, over who doesn’t believe in any God the most. Oh, no..wait.. that never happens.” – Ricky Gervais "Suppose it's all true, and you walk up to the pearly gates, and are confronted by God," Byrne asked on his show The Meaning of Life. "What will Stephen Fry say to him, her, or it?" "I'd say, bone cancer in children? What's that about?" Fry replied. "How dare you? How dare you create a world to which there is such misery that is not our fault. It's not right, it's utterly, utterly evil." "Why should I respect a capricious, mean-minded, stupid God who creates a world that is so full of injustice and pain. That's what I would say."
[toc] | [prev] | [next] | [standalone]
| From | boltar@nowhere.co.uk |
|---|---|
| Date | 2019-12-17 09:38 +0000 |
| Message-ID | <qta7n9$87r$1@gioia.aioe.org> |
| In reply to | #70522 |
On Mon, 16 Dec 2019 21:13:18 +0000 Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> wrote: >On 16/12/2019 09:57, boltar@nowhere.co.uk wrote: >> On Sun, 15 Dec 2019 15:41:18 -0800 (PST) >> =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote: >>> On Monday, 16 December 2019 01:28:14 UTC+2, Melzzzzz wrote: >>>> On 2019-12-15, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote: >>>>> On 12/15/2019 12:49 PM, Melzzzzz wrote: >>>>>> On 2019-12-15, boltar@nowhere.co.uk <boltar@nowhere.co.uk> wrote: >>>>>>> On Sun, 15 Dec 2019 11:18:43 GMT >>>>>>> Melzzzzz <Melzzzzz@zzzzz.com> wrote: >>>>>>>> On 2019-12-15, boltar@nowhere.co.uk <boltar@nowhere.co.uk> wrote: >>>>> [...] >>>>>>>> I use C only when necessary. When I have to. syntactic sugar of C++ is >>>>>>>> what makes me use it. And I hate macros. >>>>>>> >>>>>>> If you do cross platform systems or network programming you have no >>> choice but >>>>>>> to use macros even in C++17. >>>>>> >>>>>> I can use macros but I don't write them... >>>>> >>>>> Have you ever experienced the Boost preprocessor macros? Iirc, it was >>>>> the Chaos lib way back. Some hardcore shi%. >>>>> >>>>> ;^) >>>> >>>> Heh, I never used boost as well :P >>> >>> Last 15 years it has been almost inevitable to use something from boost >>> in bigger project. Other way is to write precisely same thing yourself. >>> Did you have myFilesystem, myOptional and myVariant before C++17? >> >> Optional and variant are both solutions looking for a problem. Just more >noise >> added to the language to keep a tiny number of purists happy. > >Wrong! You really are an ignorant twit. Oh hello. Is playtime over already?
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2019-12-17 09:14 +0000 |
| Message-ID | <slrnqvh72r.2ntj.grahn+nntp@frailea.sa.invalid> |
| In reply to | #70498 |
On Mon, 2019-12-16, boltar@nowhere.co.uk wrote: > On Sun, 15 Dec 2019 15:41:18 -0800 (PST) > =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote: >>On Monday, 16 December 2019 01:28:14 UTC+2, Melzzzzz wrote: ... >>> Heh, I never used boost as well :P >> >>Last 15 years it has been almost inevitable to use something from boost >>in bigger project. Other way is to write precisely same thing yourself. >>Did you have myFilesystem, myOptional and myVariant before C++17? > > Optional and variant are both solutions looking for a problem. Just > more noise added to the language to keep a tiny number of purists > happy. As far as I can tell, they're useful for solving some kinds of problems in a specific way -- but not all programs need them. To have a concrete example, optional<T> is good for representing "zero or one" and is an alternative to conventions like - "zero means absent" - "-1 means absent" - "default-constructed means absent" - "T::invalid() means absent" - keeping T by pointer, just to get "nullptr means absent" This way you don't have to complicate T itself; it doesn't have to be aware of its own possible absense. /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> |
|---|---|
| Date | 2019-12-17 17:50 +0000 |
| Message-ID | <oz8KF.8551$Qb5.1910@fx17.dcg> |
| In reply to | #70536 |
On 17/12/2019 09:14, Jorgen Grahn wrote: > On Mon, 2019-12-16, boltar@nowhere.co.uk wrote: >> On Sun, 15 Dec 2019 15:41:18 -0800 (PST) >> =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote: >>> On Monday, 16 December 2019 01:28:14 UTC+2, Melzzzzz wrote: > ... >>>> Heh, I never used boost as well :P >>> >>> Last 15 years it has been almost inevitable to use something from boost >>> in bigger project. Other way is to write precisely same thing yourself. >>> Did you have myFilesystem, myOptional and myVariant before C++17? >> >> Optional and variant are both solutions looking for a problem. Just >> more noise added to the language to keep a tiny number of purists >> happy. > > As far as I can tell, they're useful for solving some kinds of > problems in a specific way -- but not all programs need them. > > To have a concrete example, optional<T> is good for representing "zero > or one" and is an alternative to conventions like > > - "zero means absent" > - "-1 means absent" > - "default-constructed means absent" > - "T::invalid() means absent" > - keeping T by pointer, just to get "nullptr means absent" > > This way you don't have to complicate T itself; it doesn't have to > be aware of its own possible absense. Why are you trying to teach a brick wall something? He is an obtuse fucktarded troll, nothing more. /Flibble -- "Snakes didn't evolve, instead talking snakes with legs changed into snakes." - Rick C. Hodgin “You won’t burn in hell. But be nice anyway.” – Ricky Gervais “I see Atheists are fighting and killing each other again, over who doesn’t believe in any God the most. Oh, no..wait.. that never happens.” – Ricky Gervais "Suppose it's all true, and you walk up to the pearly gates, and are confronted by God," Byrne asked on his show The Meaning of Life. "What will Stephen Fry say to him, her, or it?" "I'd say, bone cancer in children? What's that about?" Fry replied. "How dare you? How dare you create a world to which there is such misery that is not our fault. It's not right, it's utterly, utterly evil." "Why should I respect a capricious, mean-minded, stupid God who creates a world that is so full of injustice and pain. That's what I would say."
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2019-12-16 09:35 +0100 |
| Message-ID | <qt7fjv$vqu$1@dont-email.me> |
| In reply to | #70485 |
On 16/12/2019 00:11, Chris M. Thomasson wrote: > On 12/15/2019 12:49 PM, Melzzzzz wrote: >> On 2019-12-15, boltar@nowhere.co.uk <boltar@nowhere.co.uk> wrote: >>> On Sun, 15 Dec 2019 11:18:43 GMT >>> Melzzzzz <Melzzzzz@zzzzz.com> wrote: >>>> On 2019-12-15, boltar@nowhere.co.uk <boltar@nowhere.co.uk> wrote: > [...] >>>> I use C only when necessary. When I have to. syntactic sugar of C++ is >>>> what makes me use it. And I hate macros. >>> >>> If you do cross platform systems or network programming you have no >>> choice but >>> to use macros even in C++17. >> >> I can use macros but I don't write them... > > Have you ever experienced the Boost preprocessor macros? Iirc, it was > the Chaos lib way back. Some hardcore shi%. > Boost has always pushed the limits of what can be done with C++. And when it seems they have pushed it to something useful, but the user-experience or the implementation is unpleasant (such as needed "hardcore macros"), the C++ powers-that-be look at what they need to do to the language to give users roughly the same results, but less unpleasantness. This is one of the driving forces behind the evolution of C++.
[toc] | [prev] | [next] | [standalone]
| From | Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> |
|---|---|
| Date | 2019-12-15 20:48 +0000 |
| Message-ID | <c_wJF.31209$m4a.2255@fx03.dcg> |
| In reply to | #70470 |
On 15/12/2019 09:53, boltar@nowhere.co.uk wrote: > On Sat, 14 Dec 2019 16:03:10 -0800 (PST) > =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote: >> On Sunday, 15 December 2019 00:17:11 UTC+2, Melzzzzz wrote: >>> C++ can be quite clean language, written. >> >> Sure, and with cleanly written code the tools tend to be content as=20 >> well. >> But we have to be capable of reading code of others anyway if >> for nothing else then for constructively explaining why it is bad >> to use it like that. The C++98 was already huge in that sense. >> Then C++11 came and changed everything by quadrupling the language >> with move semantics, lambdas and constexpr. In February C++2020 will >> quadruple it again. I feel like too old for learning it all >> once again. :( > > You're not the only one. However no doubt I and many others will have to learn > all the extra pointless BS in c++20 simply in order to get our CVs through the > door for future job interviews. I doubt I will ever use any of it - I hardly > use anything from C++14 and so far nothing from 17 in my own projects. In > fact my last 2 projects work and personal were in plain C. You don't learn C++17 and C++20 for your fucking CV, you learn it because the improvements they bring to C++ are worth using and, thankfully, you will be forced to use them and if you don't like that you can simply fuck off elsewhere: I'm sure you will love Java instead. /Flibble -- "Snakes didn't evolve, instead talking snakes with legs changed into snakes." - Rick C. Hodgin “You won’t burn in hell. But be nice anyway.” – Ricky Gervais “I see Atheists are fighting and killing each other again, over who doesn’t believe in any God the most. Oh, no..wait.. that never happens.” – Ricky Gervais "Suppose it's all true, and you walk up to the pearly gates, and are confronted by God," Byrne asked on his show The Meaning of Life. "What will Stephen Fry say to him, her, or it?" "I'd say, bone cancer in children? What's that about?" Fry replied. "How dare you? How dare you create a world to which there is such misery that is not our fault. It's not right, it's utterly, utterly evil." "Why should I respect a capricious, mean-minded, stupid God who creates a world that is so full of injustice and pain. That's what I would say."
[toc] | [prev] | [next] | [standalone]
| From | boltar@nowhere.co.uk |
|---|---|
| Date | 2019-12-16 09:55 +0000 |
| Message-ID | <qt7ka2$1q9$1@gioia.aioe.org> |
| In reply to | #70483 |
On Sun, 15 Dec 2019 20:48:08 +0000 Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> wrote: >On 15/12/2019 09:53, boltar@nowhere.co.uk wrote: >> On Sat, 14 Dec 2019 16:03:10 -0800 (PST) >> =?UTF-8?B?w5bDtiBUaWli?= <ootiib@hot.ee> wrote: >>> On Sunday, 15 December 2019 00:17:11 UTC+2, Melzzzzz wrote: >>>> C++ can be quite clean language, written. >>> >>> Sure, and with cleanly written code the tools tend to be content as=20 >>> well. >>> But we have to be capable of reading code of others anyway if >>> for nothing else then for constructively explaining why it is bad >>> to use it like that. The C++98 was already huge in that sense. >>> Then C++11 came and changed everything by quadrupling the language >>> with move semantics, lambdas and constexpr. In February C++2020 will >>> quadruple it again. I feel like too old for learning it all >>> once again. :( >> >> You're not the only one. However no doubt I and many others will have to >learn >> all the extra pointless BS in c++20 simply in order to get our CVs through >the >> door for future job interviews. I doubt I will ever use any of it - I hardly >> use anything from C++14 and so far nothing from 17 in my own projects. In >> fact my last 2 projects work and personal were in plain C. > >You don't learn C++17 and C++20 for your fucking CV, you learn it because the >improvements they bring to C++ are worth using and, thankfully, you will be >forced to use them and if you don't like that you can simply fuck off >elsewhere: I'm sure you will love Java instead. Do try growing up at some point.
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <Melzzzzz@zzzzz.com> |
|---|---|
| Date | 2019-12-15 11:12 +0000 |
| Message-ID | <fyoJF.1694$Ol2.372@fx22.am4> |
| In reply to | #70465 |
On 2019-12-15, Öö Tiib <ootiib@hot.ee> wrote: > On Sunday, 15 December 2019 00:17:11 UTC+2, Melzzzzz wrote: >> On 2019-12-14, Öö Tiib <ootiib@hot.ee> wrote: >> > On Saturday, 14 December 2019 19:19:35 UTC+2, Vir Campestris wrote: >> >> On 14/12/2019 09:23, boltar@nowhere.co.uk wrote: >> >> > Who the hell cares about online C++ compilers? Anyone who uses C++ will >> >> > already have a far superior compiler on their own machine so what purpose >> >> > do they serve other than stroking the egos of the people writing them? >> >> >> >> I care. Just the other day I was testing some code across different >> >> compilers. The online compilers let me try half a dozen different >> >> compilers on my code fragment. I only have GCC installed on my machine. >> > >> > With so complex and quickly evolving language like C++ it is good idea >> > to have couple of different compilers installed plus some static >> > analysis tools as well. When any of such clever tools (written by quite >> > good programmers) become confused about your code then it is almost >> > guaraneed that other person (or even you yourself few months later) >> > will be even more confused about it. >> >> C++ can be quite clean language, written. > > Sure, and with cleanly written code the tools tend to be content as > well. > But we have to be capable of reading code of others anyway if > for nothing else then for constructively explaining why it is bad > to use it like that. The C++98 was already huge in that sense. > Then C++11 came and changed everything by quadrupling the language > with move semantics, lambdas and constexpr. In February C++2020 will > quadruple it again. I feel like too old for learning it all > once again. :( You just use what is convenient. In practice when write new code. That is how I learned new features. But still don't use constexpr ;) > -- press any key to continue or any other to quit... U ničemu ja ne uživam kao u svom statusu INVALIDA -- Zli Zec Svi smo svedoci - oko 3 godine intenzivne propagande je dovoljno da jedan narod poludi -- Zli Zec Na divljem zapadu i nije bilo tako puno nasilja, upravo zato jer su svi bili naoruzani. -- Mladen Gogala
[toc] | [prev] | [next] | [standalone]
| From | Daniel <danielaparker@gmail.com> |
|---|---|
| Date | 2019-12-15 06:53 -0800 |
| Message-ID | <7f5255fa-f634-4dc7-9f33-409acc47356c@googlegroups.com> |
| In reply to | #70465 |
On Saturday, December 14, 2019 at 7:03:20 PM UTC-5, Öö Tiib wrote: > The C++98 was already huge in that sense. > Then C++11 came and changed everything by quadrupling the language > with move semantics, lambdas and constexpr. In February C++2020 will > quadruple it again. And yet, it still doesn't have big decimal, big float, big integer, std::int128, a good story for unicode, a streams library that doesn't follow the "massive overhead principle", and much else. There is no common language package manager, which practically all modern languages have. In consequence, the C++ open source offerings frequently look pale in comparison to their counterparts in other languages that have these things, for example, there doesn't seem to be anything in the C++ arsenal that fully compares to Rust's serde, nor, it seems, can there be, given the lack of basic things. Daniel
[toc] | [prev] | [next] | [standalone]
| From | boltar@nowhere.co.uk |
|---|---|
| Date | 2019-12-15 16:48 +0000 |
| Message-ID | <qt5o5b$19h1$1@gioia.aioe.org> |
| In reply to | #70475 |
On Sun, 15 Dec 2019 06:53:07 -0800 (PST) Daniel <danielaparker@gmail.com> wrote: >the "massive overhead principle", and much else. There is no common languag= >e=20 >package manager, which practically all modern languages have. In Why does it need one? You have a directory tree for include files and most of the libraries are closely tied in with the OS itself so can't be managed by the language system. Its easy to offer a nice package manager in a high level language like Python that hides all the nasty low level details where it interfaces with the OS libraries but C/C++ use the OS libraries direct. If the package manager screws up the whole system is fucked, not just the compiler.
[toc] | [prev] | [next] | [standalone]
| From | Daniel <danielaparker@gmail.com> |
|---|---|
| Date | 2019-12-15 09:10 -0800 |
| Message-ID | <bbe561e6-7555-42f9-85bb-1a8e6163fd5f@googlegroups.com> |
| In reply to | #70479 |
On Sunday, December 15, 2019 at 11:48:56 AM UTC-5, bol...@nowhere.co.uk wrote: > On Sun, 15 Dec 2019 06:53:07 -0800 (PST) > Daniel wrote: > >the "massive overhead principle", and much else. There is no common languag= > >e=20 > >package manager, which practically all modern languages have. In > > Why does it need one? There appears to be a demand for one, witness the fact that we have HomeBrew, Conan, vcpkg, Hunter, Buckaroo, Spack, and many others. The problem in C++ is not that we don't have a package manager, but that we have too many, and no one commonly accepted one. Daniel
[toc] | [prev] | [next] | [standalone]
| From | boltar@nowhere.co.uk |
|---|---|
| Date | 2019-12-15 18:33 +0000 |
| Message-ID | <qt5uaj$7et$1@gioia.aioe.org> |
| In reply to | #70480 |
On Sun, 15 Dec 2019 09:10:23 -0800 (PST) Daniel <danielaparker@gmail.com> wrote: >On Sunday, December 15, 2019 at 11:48:56 AM UTC-5, bol...@nowhere.co.uk wrote: >> On Sun, 15 Dec 2019 06:53:07 -0800 (PST) >> Daniel wrote: >> >the "massive overhead principle", and much else. There is no common languag= > >> >e=20 >> >package manager, which practically all modern languages have. In >> >> Why does it need one? > >There appears to be a demand for one, witness the fact that we have HomeBrew, >Conan, vcpkg, Hunter, Buckaroo, Spack, and many others. The problem in C++ is I don't know about the others but Homebrew is a generic 3rd party package manager for macos. >not that we don't have a package manager, but that we have too many, and no >one commonly accepted one. That doesn't answer the question - why does C++ need one? Perhaps on a junk OS like windows where files are scattered to the 4 winds it might help but on *nix things are pretty clean and ordered already and you don't need a package manager to unzip some header and library files into /usr/local
[toc] | [prev] | [next] | [standalone]
| From | Jorgen Grahn <grahn+nntp@snipabacken.se> |
|---|---|
| Date | 2019-12-15 19:29 +0000 |
| Message-ID | <slrnqvd2ci.2ntj.grahn+nntp@frailea.sa.invalid> |
| In reply to | #70481 |
On Sun, 2019-12-15, boltar@nowhere.co.uk wrote: > On Sun, 15 Dec 2019 09:10:23 -0800 (PST) > Daniel <danielaparker@gmail.com> wrote: >>On Sunday, December 15, 2019 at 11:48:56 AM UTC-5, bol...@nowhere.co.uk wrote: >>> On Sun, 15 Dec 2019 06:53:07 -0800 (PST) >>> Daniel wrote: >>> >the "massive overhead principle", and much else. There is no >>> >common language package manager, which practically all modern >>> >languages have. In >>> >>> Why does it need one? >> >>There appears to be a demand for one, witness the fact that we have >>HomeBrew, Conan, vcpkg, Hunter, Buckaroo, Spack, and many >>others. The problem in C++ is ... >>not that we don't have a package manager, but that we have too many, and no >>one commonly accepted one. > > That doesn't answer the question - why does C++ need one? Perhaps on a junk > OS like windows where files are scattered to the 4 winds it might help but > on *nix things are pretty clean and ordered already and you don't need a > package manager to unzip some header and library files into /usr/local Actually you /do/ want a package manager, but I run Debian Stable and don't want parallel package managers for Perl, Python, Ruby, Java etc all providing software according to quality, stability and security principles which are unclear to me. I'm happy with C++ and C not picking sides in this regard. /Jorgen -- // Jorgen Grahn <grahn@ Oo o. . . \X/ snipabacken.se> O o .
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Date | 2019-12-15 23:38 -0500 |
| Message-ID | <qt71ni$128$1@dont-email.me> |
| In reply to | #70475 |
On 12/15/19 9:53 AM, Daniel wrote: ... > And yet, it still doesn't have ... > std::int128, I'm curious: how would std::int128 differ from std::int128_t, which has been standardized? It is optional, just like all the other fixed-sized typedefs. Like those other typedefs, if not supported, that identifier, and the corresponding macros such at INT128_MAX, may not be used for any conflicting purpose if the type is not supported. What more would you want of std::int128? Making it mandatory? That won't work any better than making std:int16_t mandatory - C++'s mandate is to be implementable almost everywhere, including platforms on which std::int16_t (much less std::int128_t) would not be implementable.
[toc] | [prev] | [next] | [standalone]
| From | Öö Tiib <ootiib@hot.ee> |
|---|---|
| Date | 2019-12-15 21:23 -0800 |
| Message-ID | <a5d2c6e9-f755-4a1c-90c1-60b3d5f41649@googlegroups.com> |
| In reply to | #70489 |
On Monday, 16 December 2019 06:38:20 UTC+2, James Kuyper wrote: > On 12/15/19 9:53 AM, Daniel wrote: > ... > > And yet, it still doesn't have ... > > std::int128, > > I'm curious: how would std::int128 differ from std::int128_t, which has > been standardized? It is optional, just like all the other fixed-sized > typedefs. Like those other typedefs, if not supported, that identifier, > and the corresponding macros such at INT128_MAX, may not be used for any > conflicting purpose if the type is not supported. > What more would you want of std::int128? Making it mandatory? That won't > work any better than making std:int16_t mandatory - C++'s mandate is to > be implementable almost everywhere, including platforms on which > std::int16_t (much less std::int128_t) would not be implementable. May be it is not about standard but about compiler makers who provide 128 bit integers that are not conformant with std::int128_t.
[toc] | [prev] | [next] | [standalone]
| From | Daniel <danielaparker@gmail.com> |
|---|---|
| Date | 2019-12-15 21:36 -0800 |
| Message-ID | <a6a63628-8c28-4500-a6bb-ac028a854b10@googlegroups.com> |
| In reply to | #70491 |
On Monday, December 16, 2019 at 12:23:39 AM UTC-5, Öö Tiib wrote: > > May be it is not about standard but about compiler makers who provide > 128 bit integers that are not conformant with std::int128_t. I don't know any compilers that have std::128_t. gcc and clang have __int128, but std::numeric_limits<__int128> is only defined if compiled with e.g. -std=gnu++11 and not -std=c++11. Daniel
[toc] | [prev] | [next] | [standalone]
| From | Öö Tiib <ootiib@hot.ee> |
|---|---|
| Date | 2019-12-15 21:43 -0800 |
| Message-ID | <2a6b4b2d-283f-4b5f-9f4c-025efaa087a8@googlegroups.com> |
| In reply to | #70493 |
On Monday, 16 December 2019 07:36:32 UTC+2, Daniel wrote: > On Monday, December 16, 2019 at 12:23:39 AM UTC-5, Öö Tiib wrote: > > > > May be it is not about standard but about compiler makers who provide > > 128 bit integers that are not conformant with std::int128_t. > > I don't know any compilers that have std::128_t. gcc and clang have __int128, > but std::numeric_limits<__int128> is only defined if compiled with e.g. > -std=gnu++11 and not -std=c++11. So don't I know of any. All compilers implement 128 bit integers as non-standard extensions.
[toc] | [prev] | [next] | [standalone]
Page 13 of 16 — ← Prev page 1 … 11 12 [13] 14 15 16 Next page →
Back to top | Article view | comp.lang.c++
csiph-web