Groups > comp.lang.c > #168874 > unrolled thread

Why is there not a single good JSON library for C?

Started by	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
First post	2023-01-22 14:28 -0500
Last post	2023-01-26 12:48 -0600
Articles	20 on this page of 163 — 28 participants

Back to article view | Back to comp.lang.c

  Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-22 14:28 -0500
    Re: Why is there not a single good JSON library for C? Bonita Montero <Bonita.Montero@gmail.com> - 2023-01-22 20:56 +0100
      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-22 15:17 -0500
        Re: Why is there not a single good JSON library for C? Bonita Montero <Bonita.Montero@gmail.com> - 2023-01-23 05:25 +0100
          Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 09:06 -0500
            Re: Why is there not a single good JSON library for C? Bonita Montero <Bonita.Montero@gmail.com> - 2023-01-23 17:14 +0100
              Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-23 08:42 -0800
                Re: Why is there not a single good JSON library for C? Bonita Montero <Bonita.Montero@gmail.com> - 2023-01-23 21:27 +0100
                  Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-23 13:03 -0800
                    Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-23 13:24 -0800
                  Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-23 14:03 -0800
                  Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 17:52 -0500
                    Re: Why is there not a single good JSON library for C? Bonita Montero <Bonita.Montero@gmail.com> - 2023-01-24 13:59 +0100
            Re: Why is there not a single good JSON library for C? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-01-23 17:57 +0000
              Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 12:08 -0800
              Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 17:49 -0500
                Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 14:59 -0800
                  Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 18:20 -0500
                    Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 15:39 -0800
                      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 19:18 -0500
                Re: Why is there not a single good JSON library for C? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-23 20:10 -0500
        Re: Why is there not a single good JSON library for C? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-01-26 09:04 -0700
    Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-22 19:56 +0000
      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-22 15:26 -0500
        Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-22 22:06 +0000
    Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-22 11:59 -0800
      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-22 15:27 -0500
        Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-22 12:31 -0800
          Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-22 12:33 -0800
          Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-22 15:34 -0500
            Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-22 12:45 -0800
            Re: Why is there not a single good JSON library for C? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-01-22 13:18 -0800
              Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-22 13:38 -0800
            Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-22 13:30 -0800
              Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-23 13:17 -0600
                Re: Why is there not a single good JSON library for C? scott@slp53.sl.home (Scott Lurndal) - 2023-01-23 20:31 +0000
                  Re: Why is there not a single good JSON library for C? Bart <bc@freeuk.com> - 2023-01-24 00:31 +0000
                    Re: Why is there not a single good JSON library for C? scott@slp53.sl.home (Scott Lurndal) - 2023-01-24 00:44 +0000
                    Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 19:48 -0500
                      Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-24 07:23 -0800
      Re: Why is there not a single good JSON library for C? Vir Campestris <vir.campestris@invalid.invalid> - 2023-02-03 20:41 +0000
        Re: Why is there not a single good JSON library for C? bart c <bart4858@gmail.com> - 2023-02-04 17:32 -0800
          Re: Why is there not a single good JSON library for C? Öö Tiib <ootiib@hot.ee> - 2023-02-05 06:35 -0800
          Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-02-05 08:32 -0800
            Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-02-05 08:41 -0800
              Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-02-05 08:49 -0800
                Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-02-05 08:54 -0800
        Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-02-05 08:28 -0800
    Re: Why is there not a single good JSON library for C? Öö Tiib <ootiib@hot.ee> - 2023-01-22 14:17 -0800
    Re: Why is there not a single good JSON library for C? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-01-22 23:35 +0000
      Re: Why is there not a single good JSON library for C? Simon.Says.Yes@gfdedsed.hgtgfrfd - 2023-01-23 00:50 +0000
        Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-22 19:58 -0500
          Re: Why is there not a single good JSON library for C? Simon.Says.Yes@gfdedsed.hgtgfrfd - 2023-01-23 01:33 +0000
          Re: Why is there not a single good JSON library for C? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-01-23 02:39 +0000
        Re: Why is there not a single good JSON library for C? Öö Tiib <ootiib@hot.ee> - 2023-01-22 17:03 -0800
          Re: Why is there not a single good JSON library for C? Simon.Says.Yes@gfdedsed.hgtgfrfd - 2023-01-23 01:30 +0000
            Re: Why is there not a single good JSON library for C? Richard Damon <Richard@Damon-Family.org> - 2023-01-22 21:05 -0500
            Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-23 02:44 +0000
            Re: Why is there not a single good JSON library for C? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-23 03:21 -0500
            Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-23 11:15 +0100
              PGP signatures and BASE64 posts (Was : Why is there not a single good JSON library for C?) Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 12:47 +0000
                Re: PGP signatures and BASE64 posts (Was : Why is there not a single good JSON library for C?) David Brown <david.brown@hesbynett.no> - 2023-01-23 14:48 +0100
                  Re: PGP signatures and BASE64 posts (Was : Why is there not a single good JSON library for C?) Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-01-23 16:52 +0300
              Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 09:19 -0500
                Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-23 17:45 +0100
                  Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 18:09 -0500
                    Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-23 23:44 +0000
                      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 19:24 -0500
                        Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 16:49 -0800
                        Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-24 13:04 +0000
                          Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-24 17:19 -0500
                            Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-24 14:33 -0800
                              Re: Why is there not a single good JSON library for C? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-01-26 18:28 +0000
                                Re: Why is there not a single good JSON library for C? Manu Raju <MR@invalid.invalid> - 2023-01-26 18:44 +0000
                                  Re: Why is there not a single good JSON library for C? Anton Shepelev <anton.txt@gmail.com> - 2023-01-28 23:42 +0300
                                Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-26 11:56 -0800
                                Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-26 20:37 +0000
                                  Re: Why is there not a single good JSON library for C? Anton Shepelev <anton.txt@gmail.com> - 2023-01-28 23:37 +0300
                                    Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-28 22:27 +0000
                                Re: Why is there not a single good JSON library for C? Richard Damon <Richard@Damon-Family.org> - 2023-01-26 18:52 -0500
                            Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-25 00:33 +0000
                              Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-24 17:51 -0800
                                Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-25 11:03 +0100
                    Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-24 15:02 +0100
                      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-24 17:24 -0500
                        Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-24 14:36 -0800
                          Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-25 00:21 +0100
                            Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-24 15:28 -0800
                            Re: Why is there not a single good JSON library for C? bart c <bart4858@gmail.com> - 2023-01-25 06:43 -0800
                              Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-25 15:56 +0100
                              Re: Why is there not a single good JSON library for C? scott@slp53.sl.home (Scott Lurndal) - 2023-01-25 15:08 +0000
                                Re: Why is there not a single good JSON library for C? Öö Tiib <ootiib@hot.ee> - 2023-01-25 07:56 -0800
                                  Re: Why is there not a single good JSON library for C? Phil Carmody <pc+usenet@asdf.org> - 2023-01-25 22:48 +0200
                                    Re: Why is there not a single good JSON library for C? bart c <bart4858@gmail.com> - 2023-01-25 13:50 -0800
                                      Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-27 11:46 -0600
                                        Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-28 13:39 +0100
                                          Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-28 11:42 -0600
                                            Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-28 12:15 -0800
                                              Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-28 23:24 -0600
                              Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-25 12:10 -0800
                                Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-25 12:12 -0800
                Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 12:05 -0800
                  Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 13:46 -0800
                    Re: Why is there not a single good JSON library for C? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-23 20:06 -0500
                      Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-23 17:11 -0800
                      Re: Why is there not a single good JSON library for C? Phil Carmody <pc+usenet@asdf.org> - 2023-01-25 09:57 +0200
                        Re: Why is there not a single good JSON library for C? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 14:08 -0500
                  Re: Why is there not a single good JSON library for C? Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 22:05 +0000
                  Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 18:15 -0500
                    Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 15:36 -0800
                      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 19:43 -0500
                        Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-23 16:56 -0800
                          Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 20:12 -0500
                            Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-23 17:45 -0800
                        Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 16:58 -0800
                          Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-23 17:02 -0800
                            Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-24 15:15 +0100
                              Re: Why is there not a single good JSON library for C? Richard Harnden <richard.nospam@gmail.com> - 2023-01-24 14:35 +0000
                                Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-24 18:32 +0100
                          Re: Why is there not a single good JSON library for C Jim Jackson <jj@franjam.org.uk> - 2023-01-25 22:56 +0000
                            Re: Why is there not a single good JSON library for C Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-25 20:09 -0500
                  Re: Why is there not a single good JSON library for C? Phil Carmody <pc+usenet@asdf.org> - 2023-01-25 09:53 +0200
                    Re: Why is there not a single good JSON library for C? Öö Tiib <ootiib@hot.ee> - 2023-01-25 00:13 -0800
                      Re: Why is there not a single good JSON library for C? Phil Carmody <pc+usenet@asdf.org> - 2023-01-25 20:41 +0200
                        Re: Why is there not a single good JSON library for C? James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 14:08 -0500
                          Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-25 11:35 -0800
                            Re: Why is there not a single good JSON library for C? David Brown <david.brown@hesbynett.no> - 2023-01-26 00:18 +0100
                              Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-25 15:33 -0800
                              Re: Why is there not a single good JSON library for C? Phil Carmody <pc+usenet@asdf.org> - 2023-01-29 01:08 +0200
                                Re: Why is there not a single good JSON library for C? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-01-29 13:53 -0800
                            Apology to Öö Tiib (was Re: Why is there not a single good JSON library for C?) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-25 15:31 -0800
                              Re: Apology to Öö Tiib (was Re: Why is there not a single good JSON library for C?) Öö Tiib <ootiib@hot.ee> - 2023-01-25 23:17 -0800
                              A comment about dogwhistles Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-01-29 13:47 -0800
                                Re: A comment about dogwhistles Phil Carmody <pc+usenet@asdf.org> - 2023-03-03 15:05 +0200
                            Re: Why is there not a single good JSON library for C? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-01-26 15:16 +0300
                    Re: Why is there not a single good JSON library for C? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-25 10:37 -0800
                    Re: Why is there not a single good JSON library for C? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2023-01-29 20:57 -0700
                      Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-29 23:04 -0600
          Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-22 21:09 -0800
        Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-23 02:41 +0000
    Re: Why is there not a single good JSON library for C? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-01-23 11:35 +0300
    Re: Why is there not a single good JSON library for C? Opus <ifonly@youknew.org> - 2023-01-23 19:22 +0100
      Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-23 18:18 -0500
        Re: Why is there not a single good JSON library for C? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-01-23 16:57 -0800
          Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-24 18:23 -0600
            Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-24 20:35 -0500
              Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-24 21:37 -0600
                Re: Why is there not a single good JSON library for C? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-01-25 11:49 +0300
                  Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-25 12:32 -0600
                  Re: Why is there not a single good JSON library for C? Manu Raju <MR@invalid.invalid> - 2023-01-25 18:56 +0000
                Re: Why is there not a single good JSON library for C? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-25 18:45 +0000
                  Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-25 13:39 -0600
                Re: Why is there not a single good JSON library for C? Blue-Maned_Hawk <bluemanedhawk@gmail.com> - 2023-01-25 17:07 -0500
                  Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-25 17:54 -0600
                    Re: Why is there not a single good JSON library for C? scott@slp53.sl.home (Scott Lurndal) - 2023-01-26 00:04 +0000
                      Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-25 19:27 -0600
                  Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-26 02:50 -0800
                    Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-26 03:07 -0800
                      Re: Why is there not a single good JSON library for C? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-01-26 04:34 -0800
                        Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-26 04:56 -0800
                          Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-26 05:18 -0800
                            Re: Why is there not a single good JSON library for C? fir <profesor.fir@gmail.com> - 2023-01-26 05:23 -0800
                        Re: Why is there not a single good JSON library for C? BGB <cr88192@gmail.com> - 2023-01-26 12:48 -0600

Page 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →

#168874 — Why is there not a single good JSON library for C?

From	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Date	2023-01-22 14:28 -0500
Subject	Why is there not a single good JSON library for C?
Message-ID	<tqk2pa$37qfr$1@dont-email.me>

[Multipart message — attachments visible in raw view] — view raw

I need a JSON library that allows me to read directly from a JSON file. 
  I don't want to have to copy the file into a string or unpack it into 
a structure.  I don't need to be able to write into the JSON file.  I 
just want to be able to directly read from a JSON file.  None of the C 
JSON libraries that i could find work for me.

-- 
⚗︎ | /blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
bluemanedhawk.github.io
Apologies if this message got encoded into octoctal.  Blame Thunderbird 
for not behaving correctly with Unicode and PGP.

[toc] | [next] | [standalone]

#168875

From	Bonita Montero <Bonita.Montero@gmail.com>
Date	2023-01-22 20:56 +0100
Message-ID	<tqk4bb$382vi$1@dont-email.me>
In reply to	#168874

Am 22.01.2023 um 20:28 schrieb Blue-Maned_Hawk:

> I need a JSON library that allows me to read directly from a JSON file. 
> I don't want to have to copy the file into a string or unpack it into 
> a structure.  I don't need to be able to write into the JSON file.  I 
> just want to be able to directly read from a JSON file.  None of the C 
> JSON libraries that i could find work for me.

Better use C++. It's a magnitudes more comfortable language anyway.

[toc] | [prev] | [next] | [standalone]

#168878

From	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Date	2023-01-22 15:17 -0500
Message-ID	<tqk5l1$382la$1@dont-email.me>
In reply to	#168875

[Multipart message — attachments visible in raw view] — view raw

On 1/22/23 14:56, Bonita Montero wrote:
> 
> Better use C++. It's a magnitudes more comfortable language anyway.
> 

I don't find it comfortable.  And i don't see how using C++ would help 
with finding a library.

-- 
⚗︎ | /blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
bluemanedhawk.github.io
Apologies if this message got encoded into octoctal.  Blame Thunderbird 
for not behaving correctly with Unicode and PGP.

[toc] | [prev] | [next] | [standalone]

#168916

From	Bonita Montero <Bonita.Montero@gmail.com>
Date	2023-01-23 05:25 +0100
Message-ID	<tql26t$3fnpm$1@dont-email.me>
In reply to	#168878

Am 22.01.2023 um 21:17 schrieb Blue-Maned_Hawk:

> On 1/22/23 14:56, Bonita Montero wrote:

>> Better use C++. It's a magnitudes more comfortable language anyway.

> I don't find it comfortable.
> And i don't see how using C++ would help with finding a library.

Its more comfortable because you weite less code.
And there are for sure more JSON libraries for C++ than for C.

[toc] | [prev] | [next] | [standalone]

#168927

From	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Date	2023-01-23 09:06 -0500
Message-ID	<tqm49h$3l01v$1@dont-email.me>
In reply to	#168916

[Multipart message — attachments visible in raw view] — view raw

On 1/22/23 23:25, Bonita Montero wrote:
> Am 22.01.2023 um 21:17 schrieb Blue-Maned_Hawk:
> 
>> On 1/22/23 14:56, Bonita Montero wrote:
> 
>>> Better use C++. It's a magnitudes more comfortable language anyway.
> 
>> I don't find it comfortable.
>> >> And i don't see how using C++ would help with finding a library.
> 
> Its more comfortable because you weite less code.

I don't find that comforting.

> And there are for sure more JSON libraries for C++ than for C.

Do you have examples?

-- 
⚗︎ | /blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
bluemanedhawk.github.io
Apologies if this message got encoded into octoctal.  Blame Thunderbird 
for not behaving correctly with Unicode and PGP.

[toc] | [prev] | [next] | [standalone]

#168929

From	Bonita Montero <Bonita.Montero@gmail.com>
Date	2023-01-23 17:14 +0100
Message-ID	<tqmbo9$3mckc$2@dont-email.me>
In reply to	#168927

Am 23.01.2023 um 15:06 schrieb Blue-Maned_Hawk:
> On 1/22/23 23:25, Bonita Montero wrote:
>> Am 22.01.2023 um 21:17 schrieb Blue-Maned_Hawk:
>>
>>> On 1/22/23 14:56, Bonita Montero wrote:
>>
>>>> Better use C++. It's a magnitudes more comfortable language anyway.
>>
>>> I don't find it comfortable.
>>> >> And i don't see how using C++ would help with finding a library.
>>
>> Its more comfortable because you weite less code.
> 
> I don't find that comforting.

I'll bet you don't have much experience with C++.

>> And there are for sure more JSON libraries for C++ than for C.

> Do you have examples?

I used lib_json for a coding contest from Trivago.
It has a convenience impossible with C.

[toc] | [prev] | [next] | [standalone]

#168930

From	fir <profesor.fir@gmail.com>
Date	2023-01-23 08:42 -0800
Message-ID	<2be67a72-cbd1-4cb3-95f9-5280a1d8af66n@googlegroups.com>
In reply to	#168929

poniedziałek, 23 stycznia 2023 o 17:14:15 UTC+1 Bonita Montero napisał(a):
> Am 23.01.2023 um 15:06 schrieb Blue-Maned_Hawk: 
> > On 1/22/23 23:25, Bonita Montero wrote: 
> >> Am 22.01.2023 um 21:17 schrieb Blue-Maned_Hawk: 
> >> 
> >>> On 1/22/23 14:56, Bonita Montero wrote: 
> >> 
> >>>> Better use C++. It's a magnitudes more comfortable language anyway. 
> >> 
> >>> I don't find it comfortable. 
> >>> >> And i don't see how using C++ would help with finding a library. 
> >> 
> >> Its more comfortable because you weite less code. 
> > 
> > I don't find that comforting.
> I'll bet you don't have much experience with C++.
> >> And there are for sure more JSON libraries for C++ than for C. 
> 
> > Do you have examples?
> I used lib_json for a coding contest from Trivago. 
> It has a convenience impossible with C.

kuc++ ( translated : pony++) has one convenience: ponys go into it

that is what also linus torwalds was sain ;c (ponys want something stupid, ponys dont stand reasoneble things so big stream of ponys know where to go: (and in fact kuc++ became kobold (cobol) of present times)

in our world the marked for stupidity is abiyt 10 times bigger than market for good things so this rule also work here

[toc] | [prev] | [next] | [standalone]

#168941

From	Bonita Montero <Bonita.Montero@gmail.com>
Date	2023-01-23 21:27 +0100
Message-ID	<tqmqhp$3ou4l$1@dont-email.me>
In reply to	#168930

Am 23.01.2023 um 17:42 schrieb fir:

> kuc++ ( translated : pony++) has one convenience: ponys go into it
> that is what also linus torwalds was sain ;c (ponys want something stupid, ponys dont stand reasoneble things so big stream of ponys know where to go: (and in fact kuc++ became kobold (cobol) of present times)
> in our world the marked for stupidity is abiyt 10 times bigger than market for good things so this rule also work here

It's stupid to program in C if C++ is a viable alternative.
You can easily write a tenth of the code with the same
performance and a much higher maintainability.

[toc] | [prev] | [next] | [standalone]

#168945

From	fir <profesor.fir@gmail.com>
Date	2023-01-23 13:03 -0800
Message-ID	<a07605c7-a911-448e-927c-05bfba792478n@googlegroups.com>
In reply to	#168941

poniedziałek, 23 stycznia 2023 o 21:26:46 UTC+1 Bonita Montero napisał(a):
> Am 23.01.2023 um 17:42 schrieb fir: 
> 
> > kuc++ ( translated : pony++) has one convenience: ponys go into it 
> > that is what also linus torwalds was sain ;c (ponys want something stupid, ponys dont stand reasoneble things so big stream of ponys know where to go: (and in fact kuc++ became kobold (cobol) of present times) 
> > in our world the marked for stupidity is abiyt 10 times bigger than market for good things so this rule also work here
> It's stupid to program in C if C++ is a viable alternative. 
> You can easily write a tenth of the code with the same 
> performance and a much higher maintainability.

ponys says so.. ponys are belivers..

[toc] | [prev] | [next] | [standalone]

#168947

From	fir <profesor.fir@gmail.com>
Date	2023-01-23 13:24 -0800
Message-ID	<3e7c24f4-d26b-452b-b49b-e5af5969b590n@googlegroups.com>
In reply to	#168945

poniedziałek, 23 stycznia 2023 o 22:03:53 UTC+1 fir napisał(a):
> poniedziałek, 23 stycznia 2023 o 21:26:46 UTC+1 Bonita Montero napisał(a): 
> > Am 23.01.2023 um 17:42 schrieb fir: 
> > 
> > > kuc++ ( translated : pony++) has one convenience: ponys go into it 
> > > that is what also linus torwalds was sain ;c (ponys want something stupid, ponys dont stand reasoneble things so big stream of ponys know where to go: (and in fact kuc++ became kobold (cobol) of present times) 
> > > in our world the marked for stupidity is abiyt 10 times bigger than market for good things so this rule also work here 

> > It's stupid to program in C if C++ is a viable alternative. 
> > You can easily write a tenth of the code with the same 
> > performance and a much higher maintainability.

> ponys says so.. ponys are belivers..

btw i recently was talking to emo on that in simple words,
say if that what you say would be true there is still a problem od STUPIDITY,
kuc++ is imenely stupid and this is a problem for people who dislike stupidity
(like me and few others, coz majority of people prefers stupidity ofc)

those words showing simply part of kuc++ stupidity:

in c when you got a piece of code you silmpl -l"some.dll" it and than you call
its functions and acces its variables ..when in kuc++ you must pack this
ina  form of class object , instantiate it in a form of new (usually) then 
set a pointer to it as some field (usually) hunt hundreds of possible
null pointers (when me programing in c hunt 1 null pointer once a 3 years,
emo who use kuc++ do it regularely, hundreds of them a year) and then 
manage one big knot of idiotism which all that idiotic packaging make

this show kuc++ is ONLY for idiots imo (what ponys belive that language
sedigned for isiots is better for them is also highly doubtfull for me.. though
strictly is not impossible imo coz stupid people may feel more attuned maybe 
but i also doubt that)

[toc] | [prev] | [next] | [standalone]

#168949

From	"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>
Date	2023-01-23 14:03 -0800
Message-ID	<tqn08c$3pa57$3@dont-email.me>
In reply to	#168941

On 1/23/2023 12:27 PM, Bonita Montero wrote:
> Am 23.01.2023 um 17:42 schrieb fir:
> 
>> kuc++ ( translated : pony++) has one convenience: ponys go into it
>> that is what also linus torwalds was sain ;c (ponys want something 
>> stupid, ponys dont stand reasoneble things so big stream of ponys know 
>> where to go: (and in fact kuc++ became kobold (cobol) of present times)
>> in our world the marked for stupidity is abiyt 10 times bigger than 
>> market for good things so this rule also work here
> 
> It's stupid to program in C if C++ is a viable alternative.

Yikes! Well, I have been programming in C++ for the past couple of 
months. Humm... ;^)



> You can easily write a tenth of the code with the same
> performance and a much higher maintainability.
>

[toc] | [prev] | [next] | [standalone]

#168952

From	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Date	2023-01-23 17:52 -0500
Message-ID	<tqn336$3q93v$1@dont-email.me>
In reply to	#168941

[Multipart message — attachments visible in raw view] — view raw

On 1/23/23 15:27, Bonita Montero wrote:
> <snip/>
> 
> It's stupid to program in C if C++ is a viable alternative.
> 
> <snip/>
> 

I think it's rare for it to be a viable alternative.  It is a _much_ 
more complicated language than C, making bloated software that is far 
more difficult for others to contribute to.

-- 
⚗︎ | /blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
bluemanedhawk.github.io
Apologies if this message got encoded into octoctal.  Blame Thunderbird 
for not behaving correctly with Unicode and PGP.

[toc] | [prev] | [next] | [standalone]

#168991

From	Bonita Montero <Bonita.Montero@gmail.com>
Date	2023-01-24 13:59 +0100
Message-ID	<tqokl9$5497$1@dont-email.me>
In reply to	#168952

Am 23.01.2023 um 23:52 schrieb Blue-Maned_Hawk:

> I think it's rare for it to be a viable alternative. ...

Usually it is and the decision is made upon the developer's
mindset and capabilities.

[toc] | [prev] | [next] | [standalone]

#168932

From	Kaz Kylheku <864-117-4973@kylheku.com>
Date	2023-01-23 17:57 +0000
Message-ID	<20230123095705.928@kylheku.com>
In reply to	#168927

On 2023-01-23, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)

*plonk*

[toc] | [prev] | [next] | [standalone]

#168938

From	Keith Thompson <Keith.S.Thompson+u@gmail.com>
Date	2023-01-23 12:08 -0800
Message-ID	<87cz75ggji.fsf@nosuchdomain.example.com>
In reply to	#168932

Kaz Kylheku <864-117-4973@kylheku.com> writes:
> On 2023-01-23, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
>
> *plonk*

FYI, my newsreader displayed that message correctly.  I didn't even
realize it was MIME-encoded until it was pointed out.

I understand that you're using slrn (according to your headers) which
apparently doesn't handle MIME.  (I see that slrn has recent releases;
I'm *mildly* surprised it doesn't handle MIME.)

I'm *not* suggesting you should change newsreaders to cater to the way
this person posts, just providing a bit of information about why it's
causing problems.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for XCOM Labs
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]

#168951

From	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Date	2023-01-23 17:49 -0500
Message-ID	<tqn2t8$3q93u$1@dont-email.me>
In reply to	#168932

[Multipart message — attachments visible in raw view] — view raw

On 1/23/23 12:57, Kaz Kylheku wrote:
> On 2023-01-23, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> 
> *plonk*

I have literally no idea how i am meant to interpret this.

-- 
⚗︎ | /blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
bluemanedhawk.github.io
Apologies if this message got encoded into octoctal.  Blame Thunderbird 
for not behaving correctly with Unicode and PGP.

[toc] | [prev] | [next] | [standalone]

#168953

From	Keith Thompson <Keith.S.Thompson+u@gmail.com>
Date	2023-01-23 14:59 -0800
Message-ID	<87mt68g8m9.fsf@nosuchdomain.example.com>
In reply to	#168951

Blue-Maned_Hawk <bluemanedhawk@gmail.com> writes:
> On 1/23/23 12:57, Kaz Kylheku wrote:
>> On 2023-01-23, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
>>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
>> *plonk*
>
> I have literally no idea how i am meant to interpret this.

Really?  It's been explained at some length.

Your PGP signatures are causing your messages here to be encoded as
multipart MIME messages, with the parts (the message body and the
signature) encoded in base64.

Some newsreaders can interpret this.  Kaz uses one that apparently does
not, so he cannot read your messages.

Many of us have suggested that PGP-signing your messaes has very little
benefit, and have suggested you stop doing it.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for XCOM Labs
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]

#168958

From	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Date	2023-01-23 18:20 -0500
Message-ID	<tqn4oa$3q93v$6@dont-email.me>
In reply to	#168953

[Multipart message — attachments visible in raw view] — view raw

On 1/23/23 17:59, Keith Thompson wrote:
> Blue-Maned_Hawk <bluemanedhawk@gmail.com> writes:
>> On 1/23/23 12:57, Kaz Kylheku wrote:
>>> On 2023-01-23, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
>>>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
>>> *plonk*
>>
>> I have literally no idea how i am meant to interpret this.
> 
> Really?  It's been explained at some length.
>
Sorry, what i was trying to say was that "*plonk*" is not a word that 
conveys very much information.  Apologies if that wasn't clear.

-- 
⚗︎ | /blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
bluemanedhawk.github.io
Apologies if this message got encoded into octoctal.  Blame Thunderbird 
for not behaving correctly with Unicode and PGP.

[toc] | [prev] | [next] | [standalone]

#168960

From	Keith Thompson <Keith.S.Thompson+u@gmail.com>
Date	2023-01-23 15:39 -0800
Message-ID	<87edrkg6rv.fsf@nosuchdomain.example.com>
In reply to	#168958

Blue-Maned_Hawk <bluemanedhawk@gmail.com> writes:
> On 1/23/23 17:59, Keith Thompson wrote:
>> Blue-Maned_Hawk <bluemanedhawk@gmail.com> writes:
>>> On 1/23/23 12:57, Kaz Kylheku wrote:
>>>> On 2023-01-23, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
>>>>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
>>>> *plonk*
>>>
>>> I have literally no idea how i am meant to interpret this.
>> Really?  It's been explained at some length.
>>
> Sorry, what i was trying to say was that "*plonk*" is not a word that
> conveys very much information.  Apologies if that wasn't clear.

Ah, I see.

"*plonk*" is Usenet jargon, meaning that Kaz has added you to his
killfile.  He has configured his newsreader so that it doesn't show him
any articles you've posted.  (It's been said that it's "sound a newbie
makes as he falls to the bottom of a kill file").

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for XCOM Labs
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]

#168964

From	Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Date	2023-01-23 19:18 -0500
Message-ID	<tqn83t$3r6pd$1@dont-email.me>
In reply to	#168960

[Multipart message — attachments visible in raw view] — view raw

On 1/23/23 18:39, Keith Thompson wrote:
> Blue-Maned_Hawk <bluemanedhawk@gmail.com> writes:
>> On 1/23/23 17:59, Keith Thompson wrote:
>>> Blue-Maned_Hawk <bluemanedhawk@gmail.com> writes:
>>>> On 1/23/23 12:57, Kaz Kylheku wrote:
>>>>> On 2023-01-23, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
>>>>>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
>>>>> *plonk*
>>>>
>>>> I have literally no idea how i am meant to interpret this.
>>> Really?  It's been explained at some length.
>>>
>> Sorry, what i was trying to say was that "*plonk*" is not a word that
>> conveys very much information.  Apologies if that wasn't clear.
> 
> Ah, I see.
> 
> "*plonk*" is Usenet jargon, meaning that Kaz has added you to his
> killfile.  He has configured his newsreader so that it doesn't show him
> any articles you've posted.  (It's been said that it's "sound a newbie
> makes as he falls to the bottom of a kill file").
> 

Ah, well then.  Thanks for letting me know.

-- 
⚗︎ | /blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
bluemanedhawk.github.io
Apologies if this message got encoded into octoctal.  Blame Thunderbird 
for not behaving correctly with Unicode and PGP.

[toc] | [prev] | [next] | [standalone]

Page 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →

csiph-web

Why is there not a single good JSON library for C?

Contents

#168874 — Why is there not a single good JSON library for C?

#168875

#168878

#168916

#168927

#168929

#168930

#168941

#168945

#168947

#168949

#168952

#168991

#168932

#168938

#168951

#168953

#168958

#168960

#168964